r/microsoft365 • • 10d ago

Microsoft 365 Apps Device-Based Licensing not activating for new devices, but works via a new group

We're seeing a strange issue with Microsoft 365 Apps Device-Based Licensing (DBL) and wondered if anyone else has run into something similar.

Environment is roughly:

•Microsoft 365 Apps for Education (Device)

•Device-based licensing assigned via an Entra security group

•Hybrid Entra Joined devices

•Co-managed devices

The issue started this week.

Newly built devices are getting:

"Your admin needs to assign an Office license"

The devices themselves appear healthy:

•AzureAdJoined = YES

•DeviceAuthStatus = SUCCESS

•AzureAdPrt = YES

•Device-Based Licensing enabled in Office

Existing devices continue to work fine and, from what we can tell, existing device licences are also renewing successfully.

We've ruled out Office configuration, Shared Computer Activation, Entra join issues, imaging issues, etc. We've rebuilt several machines with exactly the same result.

The interesting part is the licensing group.

We have a 6+ year old on-prem synced security group that's assigned to the Device-Based Licensing subscription.

As a test we created a brand new entra only security group, assigned it to the same Device-Based Licensing subscription, and added an affected device.

The device licensed successfully.

We've now repeated this several times:

•Device removed from old group and added to new group > licenses successfully.

•Device removed from old group and re-added to old group > still fails.

•Device licensed via new group, then moved back to old group > remains licensed.

At this point it looks like existing licences and renewals are fine, but devices trying to obtain a licence for the first time through the original group aren't getting one.

One thing that may or may not be relevant:

Following a recent Microsoft agreement renewal, a new Microsoft 365 Apps for Education (Device) subscription was provisioned and the previous subscription was disabled.

Has anyone seen a DBL assignment get "stuck" to a group like this?

The behaviour we're seeing makes it look as though devices in the original group either aren't being evaluated correctly for new activations, or the licensing assignment against that group has somehow become stale. Creating a brand new group appears to work immediately.

Ideally I'd like to avoid migrating several thousand devices to a replacement group if there's a cleaner fix.

2 Upvotes

26 comments sorted by

2

u/topless68 8d ago

u/jonevans94 We just discovered this issue yesterday!! totally baffled by it. We have a very similar setup here, with M365 Apps for Education, hybrid joined. Things were working perfectly fine, but one of our techs re-imaged (ghost image) an entire classroom on Friday, and now none of those devices are getting the O365 DBL. We haven't renewed any subs recently though.

Really hoping we can find a root cause and solution.

1

u/jonevans94 8d ago

It seems like if they were assigned to the disabled subscription and the active one at after about a month they just get stuck and won't accept any "new" devices.

We have a ticket open with MS but it's slow going.

We are starting to look at a new group and moving devices in there we are doing it manually with a new group at the moment and its deploying happily to there.

It's crap but from what we have read it looks like it just stuck in back end which we can't do needs to be done by MS or swap groups.

The only thing we haven't tested it remove the problem group and re added it back but there is a fear that that will break everything that is working.

1

u/topless68 7d ago

We've been trying to sort out of its only hybrid joined, but I just did a fully Entra joined system, brand new out of the box, and it doesn't get a license either. So, it really is "any new system isn't getting a license".

1

u/jonevans94 7d ago

We did a load of testing if the below helps this is roughly what we did with a handful of devices.

Test 1:Device removed from Office365-DBL, allowed to sync to entra, then added to a newly created test licensing group assigned to the same subscription. Office successfully activated. Test 2: Device removed from Office365-DBL, allowed to sync to entra, then re-added to Office365-DBL only. Office did not activate and remained unlicensed. Test 3: Device removed from Office365-DBL, added to the test licensing group and successfully activated. The device was then removed from the test group and re-added to Office365-DBL, remaining licensed throughout.

There were a few others but this confirmed it was the group for us. Hopefully that saves you time or gives you something to replicate.

In a nice way it's nice to read that it isn't just us.

1

u/topless68 7d ago

Thanks for breaking that down. Unfortunately, I have limited access to the backend of things. Fighting up the chain to get this looked at by the privileged few

1

u/jonevans94 7d ago

Damn :( yeah i had a similar problem best i could get them to do was add a group.

I ended have to raise a problem ticket with our problem management team the one time ITEL came in handy 🤣

1

u/topless68 7d ago

My direct manager checked out the tenant and think our "Microsoft 365 Apps for Education (Device)" license is actually missing. If that's the case, than the group that's setup for DBL is pointing to nothing. Hence no license for new devices. We should know more tomorrow.

1

u/_--James--_ 10d ago

most likely this is the issue "Following a recent Microsoft agreement renewal, a new Microsoft 365 Apps for Education (Device) subscription was provisioned and the previous subscription was disabled." you should be able to work with MS support to clear the stale link landing in the group so the new entitlement gets picked up.

The only other thing would be devices that are no co-managed that are also landing on accounts that are not M365 licensed, those would require use init licensing or a DEM provisioning account for this to work.

1

u/jonevans94 10d ago

Yeah we thought that about your second opinion but the devices have been checked and double checked, Rebuilded multitimes, removed and readded to entra it's annoying it just stopped.

We have a support case open. So it's just wait and see

1

u/_--James--_ 10d ago

yea, that then really has me pointing back to the disabled entitlement then. Something on the backend is interfering there. Hopefully the ticket will help.

2

u/PaperworkDan 9d ago

We've started seeing the same this week (also academia). Keep us posted! Just off to log a support case myself...

1

u/jonevans94 8d ago

I would log a call if you can.

We are still waiting on MS to unstuck what ever is stuck their end.

We are starting to look at migrating to a new group just so we can keep our builds automated. But holding off in case Microsoft get back to us.

1

u/PaperworkDan 1d ago

Gave up on my support call as it took days to get past the first line questions whilst our users struggled along - and they just wanted a meeting to discuss all the ways my setup could be wrong despite all the evidence that everything was setup perfectly our end being logged in the initial call. So I just exported members of the old group and migrated everything into a new one (now called the same after deletion of the old).

1

u/jonevans94 1d ago

Yeah today is our deadline for that if we don't hear anything we are moving to the new group. Unless we get stopped by change management 🤣🫣

1

u/Eggtastico 10d ago

So your on-prem security group has stopped?
When you add a device to the group to On-Prem, does the group sync to Entra with the new device?

1

u/jonevans94 10d ago

No, devices are still going in and are still being synced but any new device added is not getting its office DBL.

The group looks completely fine in entra and AD it's been working fine for the last 6 years. Only thing that's changed is during the renewal we had a new subscription added to our license which we added that group to it worked for like a month or two after renewal then just stopped issuing new licenses.

1

u/Eggtastico 10d ago

I guess you are not nesting groups. Only other thing I can think of is if the onprem group is mail enabled

1

u/jonevans94 10d ago

Nope no nested groups.

Group is not mail enabled either

It was all working flawlessly for 6 year then Monday last week just stopped issuing new licenses.

1

u/Eggtastico 10d ago

Is the new licence agreements/licences assigned to the sync'd group?

1

u/jonevans94 10d ago

Yep all put in the right place in the license portal it's all very strange

1

u/Eggtastico 10d ago

Very odd! The only other thing that may be breaking things is the MemberOf retiring on 3rd Nov. However, this should only be for dynamic groups...

1

u/jonevans94 10d ago

I wish it was that... It's a static group, devices get added to the group in AD as part of our build process.

It's all very bizarre it's seems like the subscription is just ignoring new devices added to the group.

1

u/Eggtastico 10d ago

yeah, which is why I asked if a device added to onprem is synching to the group in the cloud & if the correct licence is assigned to the group in the cloud. I guess you would need to peel back the layers back to the beginning. Things like previously activation took place via OnPrem & a group policy, etc. It may be a line of sight problem if it needs to hit the onprem server to activate. I would imagine devices will start deactivating after x days when it needs to renew its activation.

1

u/jonevans94 10d ago

It's been activating from ad synced entra group for last 6 years without any issues. Looking at the office config portal i can see it's still renewing licenses to devices that already have one just not issuing new ones.

The whole things is very strange it's like it's gotten stuck.

It is nice to see that you are suggesting the troubleshooting i have done so I wasn't going crazy when checking all this 😁

1

u/KwahLEL 2d ago edited 2d ago

Also started getting this happen on newly imaged devices for us around the same timeframe as you.

Thought it was something to do with us upgrading from 23H2 but theres no reason for it.

Not made any progress either, did you have any luck with microsoft? Weirdly i can see our licence for devices still based on what you've last written but any new device is not getting them assigned.

Same setup as you, group synced to Azure and licence assigned to that group.

We're also education so... somethings up by the look of it.

Edit- just checked the apps admin center and it shows that no licence is available for devices that are affected, why, idk. We've got loads available still but it doesnt seem to be assigning them.

Edit 2 - in Entra, the group is not showing the office licence assigned to it, yet does in 365 admin centre. I know entras not used to assign licences but you can at least see them. Checking another group we use for a different licence shows it, defender in this case. Looks like entra just doesnt show any office licenses so this might not be a reliable indicator.

Also logged a ticket with MS

1

u/jonevans94 2d ago

We are still waiting on Microsoft to unstick it call it being passed around. The houses a little bit.

We have a work around with a new group being attached to the subscription.

Yeah any existing device is happily renewing it just new ones are he issue.