On-prem exchange, cloud mailboxes and MS license count

[rvilhelm]

Hi,

I have a case opened for this question, #07594888.

I have hybrid enviroment with exchange on-prem with ~1.000 users where we use Veeam VBR to do backup. Slowly are are moving some users to O365 mailboxes, but i am having a issue with how Veeam O365, and/or Microsoft, count mailbox users in Entra.
I have 150 licensed Office 365 users, but only 66 of them have a cloud mailbox, the rest of the have their mailbox on-prem. To do mailbox/onedrive dynamic, i have created a dynamic security group containing all users with a active Business Premium, E3, exchange plan 1+2 added to it. This part work and contains 150 users.

When Veeam O365 takes a backup of this group, i get a error saying "06-02-2025 23:59:04 :: Processing archive mailbox X completed with warning: Exchange account was not found (ID: daeeb2dd-5d0d-450c-a64e-988b37b1b41c)" on all users which have a on-prem mailbox. Users with a O365 mailbox works of cause.

Is it possible anyway to make a dynamic rule syntax to only find users which has a mailbox in O365 as seen in this Exchange portal?

/Robert

[Mildur]

Hi Robert

No, we don't have support for dynamic rules.
If there is such a capability, you have to find it in Entra ID as part of the dynamic group settings or script yourself adding the user accounts with PowerShell/Rest API.

Did you add your Organization as a hybrid configuration?

Best,
Fabian

[rvilhelm]

Hi Fabian

Thanks. To be clear the dynamic group i have configured is a Entra ID group. My issue here is the users, i am adding are based on the license type, they have, and most at these are users with on-prem mailboxes. That´s why i asked if its possible to dynamic rule containing only mailbox living in the cloud. I know this is not a issue related to Veeam.

Regarding the hybrid configuration, i looked into this and it´s currently setup for O365. But chosing hybrid then i have to select at least one on-prem exchange/sharepoint, but we do not want to buy Veeam O365 licenses for those on-prem servers as we already have VBR on-prem.

My end goal, if possible without to much manual work, are to do on-prem backyp with VBR og cloud with Veeam for 365.

What is the "normal" way to do this in hybrid enriroments when you already have en VBR license for all on-prem stuff?

Regards
Robert

[MuchachoNL]

I don't know how you've selected your Exchange users for that group, and if your on-prem mailbox users have an EOP1 or EOP2 activated.
If not, you can select them based off the fact if they have EOP1 or EOP2.
I used this rule syntax to ensure I only backup those with an actual Exchange account (=Mailbox Online)

Code: Select all

(user.assignedPlans -any (assignedPlan.servicePlanId -eq ‘efb87545-963c-4e0d-99df-69c6916d9eb0’ -and assignedPlan.capabilityStatus -eq ‘Enabled’)) -or (user.assignedPlans -any (assignedPlan.servicePlanId -eq ‘9aaf7827-d63c-4b61-89c3-182f06f82e5c’ -and assignedPlan.capabilityStatus -eq ‘Enabled’))

[rvilhelm]

Hi @MuchachoNL

All my online users have a 365 Business Premium or E3.

With the below syntax, i cant even save the group.

[MuchachoNL]

You have an Azure P1 license? I tried to implement this with all our clients, and at one tenant I wasn't able to make a dynamic group because they didn't have Azure P1 license

[rvilhelm]

No, we have a P2 license.

[MuchachoNL]

It's probably a copy paste thing where the apostrophes aren't copied correctly. It should be ' and not ‘ ’

This is the correct one, sorry for the trouble.

Code: Select all

(user.assignedPlans -any (assignedPlan.servicePlanId -eq 'efb87545-963c-4e0d-99df-69c6916d9eb0' -and assignedPlan.capabilityStatus -eq 'Enabled')) -or (user.assignedPlans -any (assignedPlan.servicePlanId -eq '9aaf7827-d63c-4b61-89c3-182f06f82e5c' -and assignedPlan.capabilityStatus -eq 'Enabled'))

[rvilhelm]

The dynamic rule is working now, ' has to be a ".

But anyway, it do not solve my main issue. I only need users with a valid mailbox located in Entra.
Currently we have many Business Premium licenses assigned, but most of them has the mailbox located on our on-prem exchange servers.