Back End "Hybrid" Account stuck through cloud identity.

Question

I am hoping someone here can help, I am not sure if this is the right subsect or not, seeing as my device has all provisionings in place it seems it could even have. I have contacted Microsoft support many times over this issue, and I am at a loss of what to do.

I own a personal computer and it is stuck looping through an obscene amount of Management provisioning. I have been working on fixing it for months now, and each time I have deleted, reset and clean installed thinking I finally fixed it, it comes back with a vengeance. I have autopilot in every other folder in my registry, logs exporting huge file folders, my list of provisions range far and wide across many OS versioning of windows clear back to Vista. Microsoft never sends the right updates as it seems I am now somehow on a test build due to it.

I have never enrolled in Intune, MDM, Enterprise anything, nor even logged in to my device with a work or school account. I have only had the PC for just under a year and neither Dell nor Microsoft has resolved the issue. Tho getting confirmation it was a "back end cloud identity" and not user error or fixable, I am directed to the business account support to troubleshoot each time, seeing as I have and operate only personal accounts, I cannot even get through to them to make this issue known.

Any trouble shooting beyond a "clean" install or deleting a few registries and tasks would be beyond appreciated bc I am using a shell of a device, unsure of what open ports this even created fully to my device.

Answer 1

It sounds like you're experiencing significant issues with your device related to a cloud identity that is causing management provisioning loops. Since you've already tried clean installs and registry edits without success, here are a few suggestions that might help you troubleshoot further:

1. Check Device Management Settings: Even if you haven't enrolled in Intune or any MDM, ensure that your device is not inadvertently linked to any management service. You can check this in the Settings under Accounts > Access work or school.
2. Use the DSRegCmd Tool: Run the command dsregcmd /status in an elevated Command Prompt to check the current state of your device's registration with Azure AD. This can provide insights into whether your device is incorrectly registered.
3. Manual Recovery: If your device is hybrid joined, you might need to perform a manual recovery. You can do this by running dsregcmd /leave in an elevated Command Prompt, followed by a restart of your device.
4. Contact Microsoft Support Again: Since you've already contacted support multiple times, consider escalating the issue or asking for a specialist who deals with Azure AD and device identity issues specifically.
5. Community Forums: Sometimes, other users may have experienced similar issues. Checking Microsoft community forums or tech support forums might provide additional insights or solutions that have worked for others.

If these steps do not resolve the issue, you may need to continue working with Microsoft support to address the backend cloud identity problem directly.

---

References:

• Troubleshoot Microsoft Entra hybrid joined devices
• Connection issues when signing in after updating to Office 2016 build 16.0.7967 on Windows 10