Azure Active Directory device management FAQ
Q: I registered the device recently. Why can’t I see the device under my user info in the Azure portal? Or why is the device owner marked as N/A for hybrid Azure Active Directory (Azure AD) joined devices?
A: Windows 10 devices that are hybrid Azure AD joined don't show up under USER devices. Use the All devices view in the Azure portal. You can also use a PowerShell Get-MsolDevice cmdlet.
Only the following devices are listed under USER devices:
- All personal devices that aren't hybrid Azure AD joined.
- All non-Windows 10 or Windows Server 2016 devices.
- All non-Windows devices.
Q: How do I know what the device registration state of the client is?
A: In the Azure portal, go to All devices. Search for the device by using the device ID. Check the value under the join type column. Sometimes, the device might be reset or reimaged. So it's essential to also check the device registration state on the device:
- For Windows 10 and Windows Server 2016 or later devices, run
- For down-level OS versions, run
%programFiles%\Microsoft Workplace Join\autoworkplace.exe.
Q: I see the device record under the USER info in the Azure portal. And I see the state as registered on the device. Am I set up correctly to use Conditional Access?
A: The device join state, shown by deviceID, must match the state on Azure AD and meet any evaluation criteria for Conditional Access. For more information, see Require managed devices for cloud app access with Conditional Access.
Q: I deleted my device in the Azure portal or by using Windows PowerShell. But the local state on the device says it's still registered.
A: This operation is by design. The device doesn't have access to resources in the cloud.
If you want to re-register, you must take a manual action on the device.
To clear the join state from Windows 10 and Windows Server 2016 that are on-premises Active Directory domain joined, take the following steps:
Open the command prompt as an administrator.
dsregcmd.exe /debug /leave.
Sign out and sign in to trigger the scheduled task that registers the device again with Azure AD.
For down-level Windows OS versions that are on-premises Active Directory domain joined, take the following steps:
- Open the command prompt as an administrator.
"%programFiles%\Microsoft Workplace Join\autoworkplace.exe /l".
"%programFiles%\Microsoft Workplace Join\autoworkplace.exe /j".
Q: Why do I see duplicate device entries in the Azure portal?
For Windows 10 and Windows Server 2016, repeated tries to unjoin and rejoin the same device might cause duplicate entries.
Each Windows user who uses Add Work or School Account creates a new device record with the same device name.
For down-level Windows OS versions that are on-premises Azure Directory domain joined, automatic registration creates a new device record with the same device name for each domain user who signs in to the device.
An Azure AD joined machine that's wiped, reinstalled, and rejoined with the same name shows up as another record with the same device name.
Q: Does Windows 10 device registration in Azure AD support TPMs in FIPS mode?
A: No, currently device registration on Windows 10 for all device states - Hybrid Azure AD join, Azure AD join and Azure AD registered - does not support TPMs in FIPS mode. To successfully join or register to Azure AD, FIPS mode needs to be turned off for the TPMs on those devices
Q: Why can a user still access resources from a device I disabled in the Azure portal?
A: It takes up to an hour for a revoke to be applied.
For enrolled devices, we recommend that you wipe the device to make sure users can't access the resources. For more information, see What is device enrollment?.
Azure AD join FAQ
Q: How do I unjoin an Azure AD joined device locally on the device?
For hybrid Azure AD joined devices, make sure to turn off automatic registration. Then the scheduled task doesn't register the device again. Next, open a command prompt as an administrator and enter
dsregcmd.exe /debug /leave. Or run this command as a script across several devices to unjoin in bulk.
For pure Azure AD joined devices, make sure you have an offline local administrator account or create one. You can't sign in with any Azure AD user credentials. Next, go to Settings > Accounts > Access Work or School. Select your account and select Disconnect. Follow the prompts and provide the local administrator credentials when prompted. Reboot the device to finish the unjoin process.
Q: Can my users sign in to Azure AD joined devices that are deleted or disabled in Azure AD?
A: Yes. Windows has a cached username and password capability that allows users who signed in previously to access the desktop quickly even without network connectivity.
When a device is deleted or disabled in Azure AD, it's not known to the Windows device. So users who signed in previously continue to access the desktop with the cached username and password. But as the device is deleted or disabled, users can't access any resources protected by device-based Conditional Access.
Users who didn't sign in previously can't access the device. There's no cached username and password enabled for them.
Q: Can disabled or deleted users sign in to Azure AD joined devices?
A: Yes, but only for a limited time. When a user is deleted or disabled in Azure AD, it's not immediately known to the Windows device. So users who signed in previously can access the desktop with the cached username and password.
Typically, the device is aware of the user state in less than four hours. Then Windows blocks those users' access to the desktop. As the user is deleted or disabled in Azure AD, all their tokens are revoked. So they can't access any resources.
Deleted or disabled users who didn't sign in previously can't access a device. There's no cached username and password enabled for them.
Q: Why do my users have issues on Azure AD joined devices after changing their UPN?
A: Currently, UPN changes are not fully supported on Azure AD joined devices. So their authentication with Azure AD fails after their UPN changes. As a result, users have SSO and Conditional Access issues on their devices. At this time, users need to sign in to Windows through the "Other user" tile using their new UPN to resolve this issue. We are currently working on addressing this issue. However, users signing in with Windows Hello for Business do not face this issue.
Q: My users can't search printers from Azure AD joined devices. How can I enable printing from those devices?
A: To deploy printers for Azure AD joined devices, see Deploy Windows Server Hybrid Cloud Print with Pre-Authentication. You need an on-premises Windows Server to deploy hybrid cloud print. Currently, cloud-based print service isn't available.
Q: How do I connect to a remote Azure AD joined device?
Q: Why do my users see You can’t get there from here?
A: Did you configure certain Conditional Access rules to require a specific device state? If the device doesn't meet the criteria, users are blocked, and they see that message. Evaluate the Conditional Access policy rules. Make sure the device meets the criteria to avoid the message.
Q: Why don't some of my users get Azure Multi-Factor Authentication prompts on Azure AD joined devices?
A: A user might join or register a device with Azure AD by using Multi-Factor Authentication. Then the device itself becomes a trusted second factor for that user. Whenever the same user signs in to the device and accesses an application, Azure AD considers the device as a second factor. It enables that user to seamlessly access applications without additional Multi-Factor Authentication prompts.
Is applicable to Azure AD joined and Azure AD registered devices - but not for hybrid Azure AD joined devices.
Isn't applicable to any other user who signs in to that device. So all other users who access that device get a Multi-Factor Authentication challenge. Then they can access applications that require Multi-Factor Authentication.
Q: Why do I get a username or password is incorrect message for a device I just joined to Azure AD?
A: Common reasons for this scenario are as follows:
Your user credentials are no longer valid.
Your computer can't communicate with Azure Active Directory. Check for any network connectivity issues.
Federated sign-ins require your federation server to support WS-Trust endpoints that are enabled and accessible.
You enabled pass-through authentication. So your temporary password needs to be changed when you sign in.
Q: Why do I see the Oops… an error occurred! dialog when I try to Azure AD join my PC?
A: This error happens when you set up Azure Active Directory enrollment with Intune. Make sure that the user who tries to Azure AD join has the correct Intune license assigned. For more information, see Set up enrollment for Windows devices.
Q: Why did my attempt to Azure AD join a PC fail, although I didn't get any error information?
A: A likely cause is that you signed in to the device by using the local built-in administrator account. Create a different local account before you use Azure Active Directory join to finish the setup.
Q:What are the MS-Organization-P2P-Access certificates present on our Windows 10 devices?
A: The MS-Organization-P2P-Access certificates are issued by Azure AD to both, Azure AD joined and hybrid Azure AD joined devices. These certificates are used to enable trust between devices in the same tenant for remote desktop scenarios. One certificate is issued to the device and another is issued to the user. The device certificate is present in
Local Computer\Personal\Certificates and is valid for one day. This certificate is renewed (by issuing a new certificate) if the device is still active in Azure AD. The user certificate is present in
Current User\Personal\Certificates and this certificate is also valid for one day, but it is issued on-demand when a user attempts a remote desktop session to another Azure AD joined device. It is not renewed on expiry. Both these certificates are issued using the MS-Organization-P2P-Access certificate present in the
Local Computer\AAD Token Issuer\Certificates. This certificate is issued by Azure AD during device registration.
Q:Why do I see multiple expired certificates issued by MS-Organization-P2P-Access on our Windows 10 devices? How can I delete them?
A: There was an issue identified on Windows 10 version 1709 and lower where expired MS-Organization-P2P-Access certificates continued to exist on the computer store because of cryptographic issues. Your users could face issues with network connectivity, if you are using any VPN clients (e.g. Cisco AnyConnect) that cannot handle the large number of expired certificates. This issue was fixed in Windows 10 1803 release to automatically delete any such expired MS-Organization-P2P-Access certificates. You can resolve this issue by updating your devices to Windows 10 1803. If you are unable to update, you can delete these certificates without any adverse impact.
Hybrid Azure AD join FAQ
Q: Where can I find troubleshooting information to diagnose hybrid Azure AD join failures?
A: For troubleshooting information, see these articles:
Q: Why do I see a duplicate Azure AD registered record for my Windows 10 hybrid Azure AD joined device in the Azure AD devices list?
A: When your users add their accounts to apps on a domain-joined device, they might be prompted with Add account to Windows? If they enter Yes on the prompt, the device registers with Azure AD. The trust type is marked as Azure AD registered. After you enable hybrid Azure AD join in your organization, the device also gets hybrid Azure AD joined. Then two device states show up for the same device.
Hybrid Azure AD join takes precedence over the Azure AD registered state. So your device is considered hybrid Azure AD joined for any authentication and Conditional Access evaluation. You can safely delete the Azure AD registered device record from the Azure AD portal. Learn to avoid or clean up this dual state on the Windows 10 machine.
Q: Why do my users have issues on Windows 10 hybrid Azure AD joined devices after changing their UPN?
A: Currently UPN changes are not fully supported with hybrid Azure AD joined devices. While users can sign in to the device and access their on-premises applications, authentication with Azure AD fails after a UPN change. As a result, users have SSO and Conditional Access issues on their devices. At this time, you need to unjoin the device from Azure AD (run "dsregcmd /leave" with elevated privileges) and re-join (happens automatically) to resolve the issue. We are currently working on addressing this issue. However, users signing in with Windows Hello for Business do not face this issue.
Q: Do Windows 10 hybrid Azure AD joined devices require line of sight to the domain controller to get access to cloud resources?
A: Generally no, except when the user's password is changed. Ater Windows 10 hybrid Azure AD join is complete, and the user has signed in at least once, the device doesn't require line of sight to the domain controller to access cloud resources. Windows 10 can get single sign on to Azure AD applications from anywhere with an internet connection, except when a password is changed. Users who sign in with Windows Hello for Business continue to get single sign on to Azure AD applications even after a password change, even if they don't have line of sight to their domain controller.
Q: What happens if a user changes their password and tries to login to their Windows 10 hybrid Azure AD joined device outside the corporate network?
A: If a password is changed outside the corporate network (for example, by using Azure AD SSPR), then the user logon with the new password will fail. For hybrid Azure AD joined devices, on-premises Active Directory is the primary authority. When a device does not have line of sight to the domain controller, it is unable to validate the new password. So, user needs to establish connection with the domain controller (either via VPN or being in the corporate network) before they're able to sign in to the device with their new password. Otherwise, they can only sign in with their old password because of cached logon capability in Windows. However, the old password is invalidated by Azure AD during token requests and hence, prevents single sign on and fails any device-based Conditional Access policies. This issue doesn't occur if you use Windows Hello for Business.
Azure AD register FAQ
Q: Can I register Android or iOS BYOD devices?
A: Yes, but only with the Azure device registration service and for hybrid customers. It's not supported with the on-premises device registration service in Active Directory Federation Services (AD FS).
Q: How can I register a macOS device?
A: Take the following steps:
The users included in your Conditional Access policy need a supported version of Office for macOS to access resources.
During the first access try, your users are prompted to enroll the device by using the company portal.
Send feedback about: