Feature Request - AD & AAD objects restoration from Veeam Enterprise Manager

[alav]

Hi everyone,

I impletemented Veeam Enterprise Manager several month ago, and today, in my organization, we are limited about capacity of restoration from VEM.
One of our Helpdesk team could restore some object on Active Directory, and other one on Entra. But they can't do it because I don't let access on our VBR server and we don't have option to allow these users to restore this kind of object.

We have another team that I let use VEM to restore only files on file server from VEM, it works pretty well, and I would like to do the same things with AD and AAD, as we have option to restore files or SQL or Exchange objects.

Something has been plan about that ?

And no, let this kind of user access to the VBR is not a solution, especially because to restore AD object, the user need to be local admin on the VBR server (what's the hell, seriously!)

[PetrM]

Hi Axel,

The described problem is crystal clear, and of course, we already have different ideas for how to solve it. I agree that adding such functionality to EM seems to be the most obvious approach at the moment. Nevertheless, I cannot share any details regarding specific plans or an ETA.

Just FYI: the requirement for a local admin exists due to the necessity of reading data from the local mount. The reason is that these databases have a specific ACL (access control lists), and the data structure is available only to the local admin.

Thanks!

[alav]

Hi Petr,

Thanks for the answer.

I understand the constraint, but it's a little bit frustrating when we try to improve security and separate activity between different team and responsability.

No details on specific plans or an ETA, I hope this isn't a way of telling us that this product won't evolve any further, is it ?

[PetrM]

Hi Axel,

I would say that it is 100% the opposite: it is a way to emphasize that the product continues to evolve. However, evolution always requires time, and it is not possible to comment on timelines. If a feature request made no sense, I would say that there was no value in it and that it was not part of our roadmap.

Thanks!