You can specify individual Azure AD accounts for remote connections by running the following PowerShell cmdlet: net localgroup 'Remote Desktop Users' /add 'AzureAD he-UPN-attribute-of-your-user'

Users can be added either manually or through MDM policies: To allow more users or groups to connect to the PC, you must allow remote connections for the specified users or groups. If the user who joined the PC to Azure AD is the only one who is going to connect remotely, no other configuration is needed. Open system properties for the remote PC.Įnable Allow remote connections to this computer and select Allow connections only from computers running Remote Desktop with Network Level Authentication. Azure AD B2B guests aren't supported for Remote desktop.Įnsure Remote Credential Guard, a new feature in Windows 10, version 1607, is turned off on the client PC you're using to connect to the remote PC. The local PC and remote PC must be in the same Azure AD tenant.Remote connections to an Azure AD-joined PC from an unjoined device or a non-Windows 10 device aren't supported. Your local PC (where you're connecting from) must be either Azure AD-joined or Hybrid Azure AD-joined if using Windows 10, version 1607 and above, or Azure AD registered if using Windows 10, version 2004 and above.Remote connections to an Azure AD-joined PC running earlier versions of Windows 10 aren't supported. Both PCs (local and remote) must be running Windows 10, version 1607 or later.Starting in Windows 10, version 1809, you can use biometrics to authenticate to a remote desktop session. Starting in Windows 10, version 1607, you can also connect to a remote PC that is joined to Azure Active Directory (Azure AD). From its release, Windows 10 has supported remote connections to PCs joined to Active Directory.

Anydesk remote access configuration