[Feature Request] Backup proxy servers in Workgroup

[jnana.dash]

Hello,

We have just evaluated VBO ver-2.0. We are planning to deploy it on Azure, but the requirement of Active Directory for proxy servers is quite disturbing. Initially this issue was not known and after few researches, we came to know workgroup is not supported for proxy servers. Extending our on-prem Active directory to Azure just for few servers is a quite risky and tedious job. Our InfoSec team will never allow this. Also, maintaining another active directory on Azure just for Veeam puts us on the same difficult page, as managing AD is another overhead just to run Veeam backup. The pre-sales team suggested us to raise a request in this forum for our issues.

I hope other customers are also facing the same issue. Please make the proxy servers to work in workgroup environment.

Regards,
Jnana Ranjan Dash

[Mike Resseler]

Jnana,

This FR is already on our list but I cannot make any promises when it will hit the product. I am a bit surprised that it wasn't known though, as it is written clearly in the release notes and user guide

Cheers
Mike

[JaySt]

yes +1 for this FR
i'm not happy with the requirement to have an AD just for the proxies. For the same reasons mentioned above.

[Sean S]

Yes + 1 for this FR
I understand the requirement but can understand the reasons mentioned in this request...

[Polina]

Noted

[lasseoe]

Big +1 for this.
None of the VBO365 components should require an AD.

[Polina]

Counted, thanks!

[Russ_SelectTech]

currently scaling the Office 365 backup solution to include multiple servers (proxies) requires a domain but from a security perspective this isn't always desirable and can add an overhead to smaller businesses and MSP services.

we'd like to see the Veeam Office 365 backup solution supported in a workgroup

[nielsengelen]

I've merged your request with the existing topic @Russ_SelectTech. Your request is noted.

[DE&C]

+1 from me for the feature request

[nielsengelen]

Your request is noted. This is still on the roadmap but no ETA for now.