cannot login to azure ad joined computer

Read additional information on how to remove registration on the client. It will only prevent access to resources using device as an identity (e.g. Deleting devices in your on-premises AD or Azure AD does not remove registration on the client.🔗 Azure AD Device Registration Flows Explained Once the device registration flow is done, the status changes to Registered with the registered date.Īn excellent article from Microsoft explaining the Device Join Mode Flows can be found here However when it comes to HAADJ, Azure AD sync involves as well and there are few steps involved before it gets registered in Azure AD as a device. Usually Azure AD join mode is straight forward as the device communicates with Azure AD straight away. The device registration state goes on Pending when the device is communicating with the device in order to join in to Azure AD.

Pending state can make the device go to a stale state where a re-registration is required. The Pending state is not an acceptable state when you need your cloud journey to accelerate and when you have to enroll your corporate devices in Endpoint Manager. My Approach is to do a deep dive on this error and to create a quick workflow to get you notified when your devices go pending so you can easily and promptly fix them and leave no Windows device behind. Ideally this is an interim state before the device gets registered in Azure AD. In a Hybrid AAD Joined (HAADJ) environment, ideally what you want the device registration to be show as registered, but due to some factors the device gets the Pending state and will stop communicating with Azure AD. Also there can be engineers who are yet to see this error (among other errors) and want to fix this. Firstly I must say, during your cloud journey you may have seen this error many times and fixed this many times.

Cannot login to azure ad joined computer