Microsoft Entra device management FAQ

Windows 10 or newer devices that are Microsoft Entra hybrid joined don't show up under USER devices. Use the All devices view. You can also use a PowerShell Get-MgDevice cmdlet.

Only the following devices are listed under USER devices:

• All personal devices that aren't Microsoft Entra hybrid joined.
• All non-Windows 10 or newer and Windows Server 2016 or later devices.
• All non-Windows devices.

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 or newer and Windows Server 2016 or later devices, run dsregcmd.exe /status.
• For down-level OS versions, run %programFiles%\Microsoft Workplace Join\autoworkplace.exe.

For troubleshooting information, see these articles:

• Troubleshooting devices using dsregcmd command
• Troubleshooting Microsoft Entra hybrid joined Windows 10 and Windows Server 2016 devices
• Troubleshooting Microsoft Entra hybrid joined down-level devices

Windows clients fetch the PRT from Microsoft Entra ID if the user and the device belong to the same tenant. Users won't get a PRT for another tenant if the device isn't registered or the user isn't a member there. If the two tenants trust each other via B2B, you can always create cross tenant B2B access and trust device claims from your home tenant.

The device join state, shown by deviceID, must match the state on Microsoft Entra ID and meet any evaluation criteria for Conditional Access. For more information, see Require managed devices for cloud app access with Conditional Access.

On Windows 10/11 devices joined or registered with Microsoft Entra ID, users are issued a Primary refresh token (PRT) which enables single sign-on. The validity of the PRT is based on the validity of the device itself. Users see this message if the device is either deleted or disabled in Microsoft Entra ID without initiating the action from the device itself. A device can be deleted or disabled in Microsoft Entra one of the following scenarios:

• User disables the device from the My Apps portal.
• An administrator (or user) deletes or disables the device.
• Microsoft Entra hybrid joined only: An administrator removes the devices OU out of sync scope resulting in the devices being deleted from Microsoft Entra ID.
• Microsoft Entra hybrid joined only: An administrator disables the computer account on premises, resulting in the device being disabled in Microsoft Entra ID.
• Upgrading Microsoft Entra Connect to the version 1.4.xx.x. Understanding Microsoft Entra Connect 1.4.xx.x and device disappearance.

This operation is by design. In this case, the device doesn't have access to resources in the cloud. Administrators can perform this action for stale, lost, or stolen devices to prevent unauthorized access. If this action was performed unintentionally, you need to re-enable or re-register the device using the steps that follow:

• If the device was disabled in Microsoft Entra ID, an administrator with sufficient privileges can enable it in the Microsoft Entra admin center.

  Note

  If you're syncing devices using Microsoft Entra Connect, Microsoft Entra hybrid joined devices will be automatically re-enabled during the next sync cycle. So, if you need to disable a Microsoft Entra hybrid joined device, you need to disable it from your on-premises AD.

• If the device is deleted in Microsoft Entra ID, you need to re-register the device. To re-register, you must take a manual action on the device. See the following steps for instructions to re-register based on the device state.

  To re-register Microsoft Entra hybrid joined Windows 10/11 and Windows Server 2016/2019 devices, take the following steps:

  1. Open the command prompt as an administrator.
  2. Enter dsregcmd.exe /debug /leave.
  3. Sign out and sign in to trigger the scheduled task that registers the device again with Microsoft Entra ID.

  For down-level Windows OS versions that are Microsoft Entra hybrid joined, take the following steps:

  1. Open the command prompt as an administrator.
  2. Enter "%programFiles%\Microsoft Workplace Join\autoworkplace.exe /l".
  3. Enter "%programFiles%\Microsoft Workplace Join\autoworkplace.exe /j".

  For Microsoft Entra joined devices Windows 10/11 devices, take the following steps:

  1. Open the command prompt as an administrator
  2. Enter dsregcmd /forcerecovery (You need to be an administrator to perform this action).
  3. Click "Sign in" in the dialog that opens up and continue with the sign in process.
  4. Sign out and sign back in on the device to complete the recovery.

  For Microsoft Entra registered Windows 10/11 devices, take the following steps:

  1. Go to Settings > Accounts > Access Work or School.
  2. Select the account and select Disconnect.
  3. Click on "+ Connect" and register the device again by going through the sign in process.

• For Windows 10 or newer and Windows Server 2016 or later, 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.
• A Microsoft Entra joined machine that's wiped, reinstalled, and rejoined with the same name shows up as another record with the same device name.

Windows 10/11 device registration is only supported for FIPS-compliant TPM 2.0 and not supported for TPM 1.2. If your devices have FIPS-compliant TPM 1.2, you must disable them before proceeding with Microsoft Entra join or Microsoft Entra hybrid join. Microsoft doesn't provide any tools for disabling FIPS mode for TPMs as it is dependent on the TPM manufacturer. Contact your hardware OEM for support.

It takes up to an hour for a revoke to be applied from the time the Microsoft Entra device is marked as disabled.

Microsoft Entra ID added support for multiple Microsoft Entra accounts starting in Windows 10 1803 release. However, Windows 10/11 restricts the number of Microsoft Entra accounts on a device to 3 to limit the size of token requests and enable reliable single sign-on (SSO). Once 3 accounts are added, users see an error for subsequent accounts. The additional problem information on the error screen provides the following message indicating the reason - "Add account operation is blocked because account limit is reached".

The MS-Organization-Access certificates are issued by the Microsoft Entra Device Registration Service during the device registration process. These certificates are issued to all join types supported on Windows - Microsoft Entra joined, Microsoft Entra hybrid joined and Microsoft Entra registered devices. Once issued, they're used as part of the authentication process from the device to request a Primary Refresh Token (PRT). For Microsoft Entra joined and Microsoft Entra hybrid joined devices, this certificate is present in Local Computer\Personal\Certificates whereas for Microsoft Entra registered devices, certificate is present in Current User\Personal\Certificates. All MS-Organization-Access certificates have a default lifetime of 10 years. These certificates are deleted from the corresponding certificate store when the device is unregistered from Microsoft Entra ID. Any inadvertent deletion of this certificate leads to authentication failures for the user, and requiring re-registration of the device in such cases.

For pure Microsoft Entra joined devices, make sure you have an offline local administrator account or create one. You can't sign in with any Microsoft Entra 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.

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 Microsoft Entra ID, 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.

Yes, but only for a limited time. When a user is deleted or disabled in Microsoft Entra ID, 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 Microsoft Entra ID, 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.

No, currently, guest users can't sign in to a Microsoft Entra joined device.

Organizations can choose to deploy Windows Server Hybrid Cloud Print with Pre-Authentication or Universal Print for their Microsoft Entra joined devices.

See Connect to remote Microsoft Entra joined PC.

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.

Common reasons for this scenario are as follows:

• Your user credentials are no longer valid.
• Your computer can't communicate with Microsoft Entra ID. 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.

Currently, Microsoft Entra joined devices don't force users to change password on the lock screen. So, users with temporary or expired passwords will be forced to change passwords only when they access an application (that requires a Microsoft Entra token) after they log in to Windows.

This error happens when you set up Microsoft Entra autoenrollment with Intune without proper license assigned. Make sure that the user who tries to Microsoft Entra join has the correct Intune license assigned. For more information, see Set up enrollment for Windows devices.

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 Microsoft Entra join to finish the setup.

The P2P Server application is application registered by Microsoft Entra ID to enable Remote Desktop Protocol (RDP) connections to any Microsoft Entra joined or Microsoft Entra hybrid joined Windows devices in your tenant. This application creates a tenant wide certificate issued by Microsoft Entra's certificate authority and is used to issue RDP device and user certificates for RDP connectivity. To ensure this is the correct application, you can find the Object ID of the P2P Server application in the Microsoft Entra admin center > Applications > Enterprise Applications. Remove the default filter applied do you can see all applications. Compare this Object ID using the Microsoft Graph API to query for the details using GET /servicePrincipals/{objectid} and confirm that the servicePrincipalNames property is urn:p2p_cert.

The MS-Organization-P2P-Access certificates are issued by Microsoft Entra ID to both, Microsoft Entra joined and Microsoft Entra hybrid 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 Microsoft Entra ID. The user certificate isn't persistent and is valid for one hour, but it's issued on-demand when a user attempts a remote desktop session to another Microsoft Entra joined device. It isn't 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 Microsoft Entra ID during device registration.

It isn't possible to disable or expire previous cached logons on Microsoft Entra joined devices.

For Microsoft Entra hybrid joined devices, make sure to turn off automatic registration in AD using the Controlled validation article. Then the scheduled task won'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 troubleshooting information, see these articles:

• Troubleshooting Microsoft Entra hybrid joined Windows 10 and Windows Server 2016 devices
• Troubleshooting Microsoft Entra hybrid joined down-level devices

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 Microsoft Entra ID. The trust type is marked as Microsoft Entra registered. After you enable Microsoft Entra hybrid join in your organization, the device also gets Microsoft Entra hybrid joined. Then two device states show up for the same device.

In most cases, Microsoft Entra hybrid join takes precedence over the Microsoft Entra registered state, resulting in your device being considered Microsoft Entra hybrid joined for any authentication and Conditional Access evaluation. However, sometimes, this dual state can result in a nondeterministic evaluation of the device and cause access issues. We strongly recommend upgrading to Windows 10 version 1803 and above where we automatically clean up the Microsoft Entra registered state. Learn how to avoid or clean up this dual state on the Windows 10 machine.

UPN changes are supported with Windows 10 2004 update and also applicable to Windows 11. Users on devices with this update won't have any issues after changing their UPNs.

UPN changes on older versions of Windows 10 aren't fully supported with Microsoft Entra hybrid joined devices. While users can sign in to the device and access their on-premises applications, authentication with Microsoft Entra ID fails after a UPN change. As a result, users have SSO and Conditional Access issues on their devices. You need to unjoin the device from Microsoft Entra ID (run "dsregcmd /leave" with elevated privileges) and rejoin (happens automatically) to resolve the issue.

No, except when the user's password is changed. After Windows 10/11 Microsoft Entra hybrid 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/11 can get single sign-on to Microsoft Entra 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 Microsoft Entra applications even after a password change, even if they don't have line of sight to their domain controller.

If a password is changed outside the corporate network (for example, by using Microsoft Entra SSPR), then the user sign-in with the new password fails. For Microsoft Entra hybrid joined devices, on-premises Active Directory is the primary authority. When a device doesn't have line of sight to a domain controller, it's unable to validate the new password. The user needs to establish a 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 sign-in capability in Windows. However, the old password is invalidated by Microsoft Entra ID during token requests and hence, prevents single sign-on and fails any device-based Conditional Access policies until the user authenticates with their new password in an app or browser. This issue doesn't occur if you use Microsoft Entra joined devices.

• For Windows 10/11 Microsoft Entra registered devices, Go to Settings > Accounts > Access Work or School. Select your account and select Disconnect. Device registration is per user profile on Windows 10/11.
• For iOS and Android, you can use the Microsoft Authenticator application Settings > Device Registration and select Unregister device.
• For macOS, you can use the Microsoft Intune Company Portal application to unenroll the device from management and remove any registration.

For Windows 10 version 2004 and older, this process can be automated with the Workplace Join (WPJ) removal tool.

Enable the following registry to block your users from adding other work accounts to your corporate domain joined, Microsoft Entra joined, or Microsoft Entra hybrid joined Windows 10/11 devices. This policy can also be used to block domain joined machines from inadvertently getting Microsoft Entra registered with the same user account.

HKLM\SOFTWARE\Policies\Microsoft\Windows\WorkplaceJoin, "BlockAADWorkplaceJoin"=dword:00000001

Related content

• The Microsoft Error Lookup Tool