Is Intune currently experiencing delays with Autopilot, ESP, and license assignments?

0
0
Asked By MellowOrbit42 On

Since earlier this week, several Intune operations in our cloud-native environment have become extremely slow or fail altogether. Autopilot deployments through the Enrollment Status Page can take a very long time and sometimes end in a timeout. Assigning an Autopilot profile to a device also takes nearly four hours, even when the group tag is correct and the device is already a member of the assigned group. User Intune license assignments are not recognized until roughly 24 hours later. Has anyone else seen similar delays or service issues recently? A support case with Microsoft is already open.

4 Answers

Answered By QuietHarbor31 On

We also had trouble deploying scripts, forcing syncs, and even loading the Intune portal in a government cloud tenant while working with Microsoft support. That points more toward an Intune-side outage or regional degradation than an Autopilot profile or group-tag problem.

Answered By AmberKite56 On

One enrollment problem we encountered may have involved DNS propagation. Newly registered devices could not consistently reach the required services, and different DNS resolvers updated at very different speeds. It is worth checking DNS resolution from the affected network, but widespread delays in licensing and portal operations would still suggest a separate Microsoft-side problem.

Answered By NovaPebble7 On

Before assuming the device configuration is wrong, check the tenant and enrollment status with the available Autopilot diagnostic PowerShell tools. They can show whether the device is waiting on profile assignment, policy processing, licensing, or ESP requirements. If several unrelated Intune functions are delayed at the same time, though, it is more likely a backend service issue.

Answered By CedarFox88 On

We have seen similar behavior during what appeared to be a Microsoft service incident. Autopilot deployments took more than an hour, and some enrollment attempts kept looping. In our case, the service eventually started working normally again without any configuration changes.

Related Questions

LEAVE A REPLY

Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.