Event banner
AMA: Microsoft 365 and Windows licensing
Event Ended
Wednesday, Jul 21, 2021, 02:00 PM PDTEvent details
We often see questions about licensing during our Ask Microsoft Anything (AMA) events so we're assembling our licensing experts together in one place to help provide answers! We'll answer live during...
Heather_Poulsen
Updated Jul 21, 2021
SeMeDe
Jul 20, 2021Iron Contributor
Hello everybody, we are not 100% sure if this is a technical issue or works as designed, so I leave it here so maybee some license or AAD or Intune expert could answer this...
We are using hybrid AAD user accounts synced by AD Connect. Licensed with M365 E5.
Sometimes user are getting temporarily disabled in out meta directory (e. g. for some weeks illness).
The disablement gets synched to AAD and altough licenses are removed for the user in AAD.
The associated device in Intune is falling to "Not Compliant" because of "Built-In Compliance" stating "enrolled user exists" and "has compliance policy assigned" is "Not Compliant".
Until here I could agree, this is working as designed.
But then the user comes back, get enabled again, this is synched to AAD and altough licenses get assigned. But the device stays in "Not Compliant".
At the moment the help desk gets it fixed by removing primary user, sync device, set the same user as primary again and sync device again.
Is this behaviour "as designed"?
Is it a missbehaviour, maybee because of some special conditions (than I would open a case)?
Does anybody else see this behaviour?
Thanks in advance.
- Jason_LeznekJul 21, 2021
Microsoft
Hi, thank you for reaching out with this question. My best suggestion is to open a ticket with support and they can help troubleshoot and resolve the issue with you.