Reassigning a device to another user
What is the recommended process for reassigning a device to a new user in an environment where all devices are enrolled in Autopilot, Intune Defender, and Entra ID, and users have M365 E5 licenses? Currently, to maintain compliance while the device is awaiting reassignment, I have been deleting it from the Intune and Defender portals, but not from Autopilot. However, since the device remains in Autopilot, it cannot be deleted from Entra ID and continues to display the old name and user assignment, even after being renamed in Autopilot. Is there a better approach to this situation?Azure AD Join Fails with Error 80072ee2 - EnterpriseRegistration URL Resolves OK
Hi there. Looking for some assistance with this error on a machine we have not been able to join to Azure AD/Entra ID: https://learn.microsoft.com/en-us/troubleshoot/windows-server/identity/workplace-join-fail-error-0x80072ee7 Some information: It's on Windows 11 Pro. We have wiped it and tried again, no change. It CAN 'join' AAD if you select 'enroll in MDM only' option. No errors, it shows up in the tenant, etc. But we want a full join. It can resolve the enterpriseregistration.domain.com URL. Here's the output (redacted a bit): Addresses: 2603:1037:1:18:: 2603:1037:1:8::7 2603:1036:3000:8:: 2603:1036:3000:10::2 2603:1037:1:10:: 40.126.24.16 40.126.24.145 20.190.152.144 20.190.152.80 20.190.152.23 Aliases: enterpriseregistration.domain.com enterpriseregistration.windows.net na.privatelink.msidentity.com prdf.aadg.msidentity.comI have attempted to use a provisioning package created by a deployment tool we use, and that also failed. I got the MDMDiagReport.xml from the MDMDiagReport.cab and found this in there: I can provide more info from the .cab logs if anyone wants to see. Does anyone have an idea of why the join would fail, while the MDM enrollment would go just fine? Any help much appreciated.
