EntraID, why not part of VB365

[DaStivi]

i still don't understand why this functionality hasn't been integrated in the VB365 Product where it should belong... and especially for Service Providers (and also for normal customers), the tenant is in backup there already and could simply have expanded to secure also the users and groups etc, even more some of the restore functionality of vb365 is directly depended to entraID Objects, like Mailboxes!!!!

[Mildur]

Hi Stephan

I split your question from the other topic. Please lets not mix different discussions in a single topic.

Regarding why Entra ID is not part of Veeam Backup for Microsoft 365, it's because Entra ID can be used independently from Microsoft 365 licenses.

Entra ID as an identity and access management provider is used across different Microsoft and non-Microsoft services.
Some examples include:
- Identity management for larger environments (SSO for your on-prem applications or other non-microsoft based web services)
- App developers who use application registrations to access resources on Azure
- People who use other Microsoft Services (Microsoft 365, Azure, Dynamics Online, …)

Entra ID is not solely a component used by Microsoft 365; instead, it functions as a identity and access management solution that extends beyond just Microsoft 365 services.

Best,
Fabian

[DanielJ]

The only ones who have asked me (for a long time) about backing up Azure AD/EntraID are our VB365 customers. It would have been convenient to just include it in their VB365 backups. Now I have to think about how to best implement this for customers who want it (luckily I'm being paid to think of such things).

[DaStivi]

Hi Stephan

Entra ID is not solely a component used by Microsoft 365; instead, it functions as a identity and access management solution that extends beyond just Microsoft 365 services.

Best,
Fabian

in my humble opinion it still would have fitted into the vb365 product better... even if you don't backup any of the M365 content, it would have belonged there... and not in a product that purpose was until now to backup infrastructure systems!
you could have made some licensing solely for entraID objects, or what ever... maybe still just count one vb365 license per user... but of course from a (veeam-)business perspective you would probably have given away this feature now for "free" at least don't earn extra like now with the instance based licensing... but that's just my 2 cents

[mkretzer]

Indeed. With the current functionality it is hard to argue purchasing 1/10 universal license for every user we have, even if that user is not actively in use. This is better with Veeam for Office365.

[sdv]

@Veeam - Are there plans moving Entra Id to O365 product in 2026?

Because right now we are forced using Veeam Data Cloud (no API, no detailed reports) or use VBR.
- The first is another cloud dependency with only basic features.
- The latter is, as others mentioned, becoming way too pricy (triple the costs of VBR if not more).

O365 onprem still feels the best fit to add EntraID

[AlexAverboukh]

No, there are no such plans, we still consider Entra ID to be a separate identity service.

[DaStivi]

Is there usage data available? How many veeam customers using entra Backup, that uses M365 Backup ?

And how many use entraID backup without VB365?

None of my veeam customers are using entraID Backup!

[AlexL]

All my customers with Entra ID also have MS365 backup, but not all my MS365 customers have Entra ID backup (yet)

[tm67]

Same here. It's difficult to explain why EntraID has to be licensed completely separately if using local installed vb365 / VBR.
We have a few requests to protect EntraID, but only from already vb365 customers.
I wonder how the future licensing will be if additional SaaS services from Microsoft can be protected with Veeam. If there are even more separate licenses required, it will be even more difficult to justify those.