User Device Registration Admin log – EventID 204 or 304 – Error code: 0x801c03f2 (“The public key user certificate is not found on the device object with id (xxx).”) – make sure the userCertificate attribute is selected in the Azure AD Connect “Select Attributes” settings of the on-premises connector. User Device Registration Admin log – EventID 204 – Error code: 0x801c03f2 or 0x801c03f3 (“The device object by the given id (xxx) is not found.”) – make sure the on-premises computer object is synchronized to Azure AD. User Device Registration Admin log – EventID 305 – AdalErrorCode: 0xcaa90006 – make sure the computer is able to reach and authenticate to specified in the error text description Identity Provider endpoint. User Device Registration Admin log – wmain: Unable to retrieve access token 0x80004005 – recommended step is to check the AD FS claim rules. Other way to configure correct claim rules for your Office 365 Relying Party is to use official AD FS claims generator. Microsoft also recommends using Azure AD Connect wizard to set up device registration. It is important to have the AD FS claim rules in the described order and if you have multiple verified domains, do not forget remove any existing IssuerID rule that might have been created by Azure AD Connect or other means. User Device Registration Admin log – EventID 304 or 305 – adalResponseCode: 0xcaa1000e – recommended step is to check the AD FS claim rules per mentioned above article. Below are some examples of the errors and possible solutions to try. If the AzureAdJoined says NO, next step will be to collect information from the Application and Services – Microsoft – Windows – User Device Registration – Admin logs.įirst thing, try to locate and read the text description in the error to see if it gives any clue. For the Azure AD registered devices, it should be set to YES. To check if the device was joined to Azure AD run “dsregcmd /status” command in command prompt and look at AzureAdJoined value. If you are looking for troubleshooting guide for the issue when Azure AD Conditional Access policy is treating your successfully joined station as Unregistered, see my other recent post.

Even when you followed the Hybrid Azure AD join instructions to set up your environment, you still might experience some issues with the computers not registering with Azure AD.

Aad logs