Events
May 19, 6 PM - May 23, 12 AM
Calling all developers, creators, and AI innovators to join us in Seattle @Microsoft Build May 19-22.
Register todayThis browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Windows supports remote connections to devices joined to Active Directory s well as devices joined to Microsoft Entra ID using Remote Desktop Protocol (RDP).
Microsoft Entra authentication can be used on the following operating systems for both the local and remote device:
There's no requirement for the local device to be joined to a domain or Microsoft Entra ID. As a result, this method allows you to connect to the remote Microsoft Entra joined device from:
Microsoft Entra authentication can also be used to connect to Microsoft Entra hybrid joined devices.
To connect to the remote computer:
Launch Remote Desktop Connection from Windows Search, or by running mstsc.exe
.
Select Use a web account to sign in to the remote computer option in the Advanced tab. This option is equivalent to the enablerdsaadauth
RDP property. For more information, see Supported RDP properties with Remote Desktop Services.
Specify the name of the remote computer and select Connect.
Note
IP address cannot be used when Use a web account to sign in to the remote computer option is used. The name must match the hostname of the remote device in Microsoft Entra ID and be network addressable, resolving to the IP address of the remote device.
When prompted for credentials, specify your user name in user@domain.com
format.
You're then prompted to allow the remote desktop connection when connecting to a new PC. Microsoft Entra remembers up to 15 hosts for 30 days before prompting again. If you see this dialogue, select Yes to connect.
Important
If your organization has configured and is using Microsoft Entra Conditional Access, your device must satisfy the conditional access requirements to allow connection to the remote computer. Conditional Access policies with grant controls and session controls may be applied to the application Microsoft Remote Desktop (a4a365df-50f1-4397-bc59-1a1564b8bb9c) for controlled access.
The Windows lock screen in the remote session doesn't support Microsoft Entra authentication tokens or passwordless authentication methods like FIDO keys. The lack of support for these authentication methods means that users can't unlock their screens in a remote session. When you try to lock a remote session, either through user action or system policy, the session is instead disconnected and the service sends a message to the user explaining they've been disconnected.
Disconnecting the session also ensures that when the connection is relaunched after a period of inactivity, Microsoft Entra ID reevaluates the applicable conditional access policies.
By default, RDP doesn't use Microsoft Entra authentication, even if the remote PC supports it. This method allows you to connect to the remote Microsoft Entra joined device from:
Note
Both the local and remote device must be in the same Microsoft Entra tenant. Microsoft Entra B2B guests aren't supported for Remote desktop.
To connect to the remote computer:
mstsc.exe
.user@domain.com
or AzureAD\user@domain.com
format.Tip
If you specify your user name in domain\user
format, you may receive an error indicating the logon attempt failed with the message Remote machine is Microsoft Entra joined. If you are signing in to your work account, try using your work email address.
Note
For devices running Windows 10, version 1703 or earlier, the user must sign in to the remote device first before attempting remote connections.
This table lists the supported configurations for remotely connecting to a Microsoft Entra joined device without using Microsoft Entra authentication:
Criteria | Client operating system | Supported credentials |
---|---|---|
RDP from Microsoft Entra registered device | Windows 10, version 2004 or later | Password, smart card |
RDP from Microsoft Entra joined device | Windows 10, version 1607 or later | Password, smart card, Windows Hello for Business certificate trust |
RDP from Microsoft Entra hybrid joined device | Windows 10, version 1607 or later | Password, smart card, Windows Hello for Business certificate trust |
Note
If the RDP client is running Windows Server 2016 or Windows Server 2019, to be able to connect to Microsoft Entra joined devices, it must allow Public Key Cryptography Based User-to-User (PKU2U) authentication requests to use online identities.
Note
When a Microsoft Entra group is added to the Remote Desktop Users group on a Windows device, it isn't honored when the user that belongs to the Microsoft Entra group logs in through RDP, resulting in failure to establish the remote connection. In this scenario, Network Level Authentication should be disabled to allow the connection.
Remote Desktop Users group is used to grant users and groups permissions to remotely connect to the device. Users can be added either manually or through MDM policies:
Adding users manually:
You can specify individual Microsoft Entra accounts for remote connections by running the following command, where <userUPN>
is the UPN of the user, for example user@domain.com
:
net localgroup "Remote Desktop Users" /add "AzureAD\<userUPN>"
In order to execute this command, you must be a member of the local Administrators group. Otherwise, you may see an error similar to There is no such global user or group: <name>
.
Adding users using policy:
Starting in Windows 10, version 2004, you can add users to the Remote Desktop Users using MDM policies as described in How to manage the local administrators group on Microsoft Entra joined devices.
Events
May 19, 6 PM - May 23, 12 AM
Calling all developers, creators, and AI innovators to join us in Seattle @Microsoft Build May 19-22.
Register today