Nothing Enrols
Twenty new starters signed in to their new laptops this morning. The laptops joined Microsoft Entra ID, but none of them enrolled in Intune, so they have no apps, no Wi-Fi profile and no security policies. Induction starts at 10.
Three locks to open
- 1Find the cause. Why are the laptops joining Entra ID but not Intune?
- 2Fix it. Let the new starters' laptops enrol, without opening the door to anything else.
- 3Prove it. Get one of the laptops to enrol.
The new starters have their laptops but there's nothing on them. No Teams, no Outlook. Induction is at 10!
They all show as Entra joined, but Intune isn't managing any of them. Last week's starters were fine.
You escaped Nothing Enrols
What happened
To stop his test laptop enrolling, Tom set the MDM user scope for automatic enrolment to None on Friday and forgot to change it back. Joining Microsoft Entra ID still worked, but with the scope at None, Windows didn't enrol any of Monday's new laptops in Intune and logged event 76 with error 0x8018002b.
How you'd fix it for real
- Confirm the device is Entra joined but not managed by Intune.
- Check the device's DeviceManagement-Enterprise-Diagnostics-Provider Admin log for event 76 and its error code.
- Set the MDM user scope to All, or to Some with the right groups.
- Have users restart or sign out and back in so enrolment runs again, and check the devices appear in Intune.
Stop it happening again
- Test with a separate group (Some), never by setting the scope to None for everyone.
- Review the audit log for Intune and Entra changes made late on Fridays.
- Use Windows Autopilot for new devices, so enrolment problems show up during setup rather than after it.