Understanding Intune Autopilot Error 0x8007052e

Two days ago, Microsoft had an outage affecting Intune AutoPilot Pre-Provisionning. Users performing Windows Autopilot pre-provisioning or self-deploying mode were being blocked to do so. We decided to document the Intune Autopilot Error 0x8007052e issue since there’s no post or information on the web as we write down those lines.

The good news is that if you are affected by this error in the future, chances are that it’s caused by a service outage at Microsoft. We’ll guide you through steps to verify that it’s not on your end and lost precious troubleshooting time.

Identifying the Intune Autopilot Error code 0x8007052e

Let’s dig into this error and see the behaviour. This is a summary of this Reddit post that has multiple users reporting the issue on April 30th 2024. There have been numerous different errors:

• Error is Registering your device for mobile management (4, 0x8007052e)
• Error is We couldn’t find the corresponding MDM information for this Azure AD device. Error: 0x8007052e
• Event Viewer under -moderndeployment-diagnostics-provider-autopilot shows the error : AutopilotManager failed during device enrollment phase DeviceDiscovery. HRESULT = 0x8007052E
• Couldn’t find corresponding MDM info, error 0x8007052E

Troubleshooting the 0x8007052e Error

Here’s the main troubleshooting that users made to find the root cause :

• At the Device Preparation phase, you get Registering your device for mobile management (4, 0x8007052e) error

• The Autopilot Diagnostics scripts show ESP Diagnostics info does not (yet) Exist (or blank)
• dsregcmd /status is blank

Fixing the error

Microsoft has released a statement (ID: IT788996) on the affected tenant. On the Service Health Status page. If you don’t see the statement, it’s simply because your tenant is not affected.

So for now, if you are experiencing this issue, chances are that the issue is on Microsoft’s side. We hope that this post has been helpful.