diff --git a/browsers/edge/docfx.json b/browsers/edge/docfx.json index f021f6aafb..2205218007 100644 --- a/browsers/edge/docfx.json +++ b/browsers/edge/docfx.json @@ -29,6 +29,7 @@ "globalMetadata": { "uhfHeaderId": "MSDocsHeader-MSEdge", "recommendations": true, + "adobe-target": true, "ms.collection": [ "tier3" ], diff --git a/browsers/internet-explorer/docfx.json b/browsers/internet-explorer/docfx.json index 626d8e7d35..ed0fa381c5 100644 --- a/browsers/internet-explorer/docfx.json +++ b/browsers/internet-explorer/docfx.json @@ -24,6 +24,7 @@ ], "globalMetadata": { "recommendations": true, + "adobe-target": true, "ms.collection": [ "tier3" ], diff --git a/education/docfx.json b/education/docfx.json index 993809eee6..8662cf333f 100644 --- a/education/docfx.json +++ b/education/docfx.json @@ -28,6 +28,7 @@ ], "globalMetadata": { "recommendations": true, + "adobe-target": true, "ms.topic": "article", "ms.collection": [ "education", diff --git a/store-for-business/docfx.json b/store-for-business/docfx.json index 4be7b72365..c0b85a8a1d 100644 --- a/store-for-business/docfx.json +++ b/store-for-business/docfx.json @@ -32,6 +32,7 @@ "externalReference": [], "globalMetadata": { "recommendations": true, + "adobe-target": true, "ms.collection": [ "tier2" ], diff --git a/windows/application-management/docfx.json b/windows/application-management/docfx.json index 1c1b014b8d..76647fae53 100644 --- a/windows/application-management/docfx.json +++ b/windows/application-management/docfx.json @@ -34,6 +34,7 @@ "externalReference": [], "globalMetadata": { "recommendations": true, + "adobe-target": true, "breadcrumb_path": "/windows/resources/breadcrumb/toc.json", "ms.collection": [ "tier2" diff --git a/windows/client-management/connect-to-remote-aadj-pc.md b/windows/client-management/connect-to-remote-aadj-pc.md index 2abfcd2135..42c1d58c19 100644 --- a/windows/client-management/connect-to-remote-aadj-pc.md +++ b/windows/client-management/connect-to-remote-aadj-pc.md @@ -22,8 +22,8 @@ ms.technology: itpro-manage From its release, Windows has supported remote connections to devices joined to Active Directory using Remote Desktop Protocol (RDP). Windows 10, version 1607 added the ability to connect to a device that is joined to Azure Active Directory (Azure AD) using RDP. - Starting in Windows 10, version 1809, you can [use biometrics to authenticate to a remote desktop session](/windows/whats-new/whats-new-windows-10-version-1809#remote-desktop-with-biometrics). -- Starting in Windows 10/11, with 2022-09 preview update installed, you can [use Azure AD authentication to connect to the remote Azure AD device](#connect-with-azure-ad-authentication). - +- Starting in Windows 10/11, with 2022-10 update installed, you can [use Azure AD authentication to connect to the remote Azure AD device](#connect-with-azure-ad-authentication). + ## Prerequisites - Both devices (local and remote) must be running a supported version of Windows. @@ -34,28 +34,35 @@ From its release, Windows has supported remote connections to devices joined to ## Connect with Azure AD Authentication -Azure AD Authentication can be used on the following operating systems: - -- Windows 11 with [2022-09 Cumulative Updates for Windows 11 Preview (KB5017383)](https://support.microsoft.com/kb/KB5017383) or later installed. -- Windows 10, version 20H2 or later with [2022-09 Cumulative Updates for Windows 10 Preview (KB5017380)](https://support.microsoft.com/kb/KB5017380) or later installed. -- Windows Server 2022 with [2022-09 Cumulative Update for Microsoft server operating system preview (KB5017381)](https://support.microsoft.com/kb/KB5017381) or later installed. +Azure AD Authentication can be used on the following operating systems for both the local and remote device: +- Windows 11 with [2022-10 Cumulative Updates for Windows 11 (KB5018418)](https://support.microsoft.com/kb/KB5018418) or later installed. +- Windows 10, version 20H2 or later with [2022-10 Cumulative Updates for Windows 10 (KB5018410)](https://support.microsoft.com/kb/KB5018410) or later installed. +- Windows Server 2022 with [2022-10 Cumulative Update for Microsoft server operating system (KB5018421)](https://support.microsoft.com/kb/KB5018421) or later installed. + There's no requirement for the local device to be joined to a domain or Azure AD. As a result, this method allows you to connect to the remote Azure AD joined device from: - [Azure AD joined](/azure/active-directory/devices/concept-azure-ad-join) or [Hybrid Azure AD joined](/azure/active-directory/devices/concept-azure-ad-join-hybrid) device. - Active Directory joined device. - Workgroup device. + +Azure AD authentication can also be used to connect to Hybrid Azure AD joined devices. To connect to the remote computer: - Launch **Remote Desktop Connection** from Windows Search, or by running `mstsc.exe`. -- Specify the name of the remote computer. - 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](/windows-server/remote/remote-desktop-services/clients/rdp-files). +- 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 Azure AD 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. Azure AD 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 [Azure AD Conditional Access](/azure/active-directory/conditional-access/overview), your device must satisfy the conditional access requirements to allow connection to the remote computer. +> If your organization has configured and is using [Azure AD Conditional Access](/azure/active-directory/conditional-access/overview), your device must satisfy the conditional access requirements to allow connection to the remote computer. Conditional Access policies with [grant controls](/azure/active-directory/conditional-access/concept-conditional-access-grant) and [session controls](/azure/active-directory/conditional-access/howto-conditional-access-session-lifetime) may be applied to the application **Microsoft Remote Desktop (a4a365df-50f1-4397-bc59-1a1564b8bb9c)** for controlled access. ### Disconnection when the session is locked @@ -87,7 +94,7 @@ To connect to the remote computer: ### Supported configurations -This table lists the supported configurations for remotely connecting to an Azure AD joined device: +This table lists the supported configurations for remotely connecting to an Azure AD joined device without using Azure AD authentication: | **Criteria** | **Client operating system** | **Supported credentials** | |--------------------------------------------|-----------------------------------|--------------------------------------------------------------------| @@ -99,7 +106,7 @@ This table lists the supported configurations for remotely connecting to an Azur > If the RDP client is running Windows Server 2016 or Windows Server 2019, to be able to connect to Azure AD joined devices, it must [allow Public Key Cryptography Based User-to-User (PKU2U) authentication requests to use online identities](/windows/security/threat-protection/security-policy-settings/network-security-allow-pku2u-authentication-requests-to-this-computer-to-use-online-identities). > [!NOTE] -> When an Azure AD group is added to the **Remote Desktop Users** group on a Windows device, it isn't honoured when the user that belongs to the Azure AD 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. +> When an Azure AD group is added to the **Remote Desktop Users** group on a Windows device, it isn't honored when the user that belongs to the Azure AD 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. ## Add users to Remote Desktop Users group @@ -122,3 +129,5 @@ Remote Desktop Users group is used to grant users and groups permissions to remo ## Related articles [How to use Remote Desktop](https://support.microsoft.com/windows/how-to-use-remote-desktop-5fe128d5-8fb1-7a23-3b8a-41e636865e8c) + + diff --git a/windows/client-management/docfx.json b/windows/client-management/docfx.json index ae506a8cb0..1fcb22e3c9 100644 --- a/windows/client-management/docfx.json +++ b/windows/client-management/docfx.json @@ -34,6 +34,7 @@ "externalReference": [], "globalMetadata": { "recommendations": true, + "adobe-target": true, "ms.collection": [ "tier2" ], diff --git a/windows/configuration/docfx.json b/windows/configuration/docfx.json index 90a28bb7e6..ae433621cc 100644 --- a/windows/configuration/docfx.json +++ b/windows/configuration/docfx.json @@ -34,6 +34,7 @@ "externalReference": [], "globalMetadata": { "recommendations": true, + "adobe-target": true, "ms.collection": [ "tier2" ], diff --git a/windows/deployment/docfx.json b/windows/deployment/docfx.json index 1387984499..066cd3ec04 100644 --- a/windows/deployment/docfx.json +++ b/windows/deployment/docfx.json @@ -34,6 +34,7 @@ "externalReference": [], "globalMetadata": { "recommendations": true, + "adobe-target": true, "ms.collection": [ "tier2" ], diff --git a/windows/hub/docfx.json b/windows/hub/docfx.json index c1b07ce9d8..92c7e04bad 100644 --- a/windows/hub/docfx.json +++ b/windows/hub/docfx.json @@ -34,6 +34,7 @@ "externalReference": [], "globalMetadata": { "recommendations": true, + "adobe-target": true, "ms.collection": [ "tier1" ], diff --git a/windows/privacy/docfx.json b/windows/privacy/docfx.json index 79774ab7cc..9527d8b80f 100644 --- a/windows/privacy/docfx.json +++ b/windows/privacy/docfx.json @@ -34,6 +34,7 @@ "externalReference": [], "globalMetadata": { "recommendations": true, + "adobe-target": true, "breadcrumb_path": "/windows/resources/breadcrumb/toc.json", "uhfHeaderId": "MSDocsHeader-M365-IT", "ms.technology": "windows", diff --git a/windows/security/docfx.json b/windows/security/docfx.json index 0310c13313..7591454011 100644 --- a/windows/security/docfx.json +++ b/windows/security/docfx.json @@ -34,6 +34,7 @@ "externalReference": [], "globalMetadata": { "recommendations": true, + "adobe-target": true, "ms.collection": [ "tier2" ], diff --git a/windows/whats-new/docfx.json b/windows/whats-new/docfx.json index bd292f17c7..e833279c7f 100644 --- a/windows/whats-new/docfx.json +++ b/windows/whats-new/docfx.json @@ -34,6 +34,7 @@ "externalReference": [], "globalMetadata": { "recommendations": true, + "adobe-target": true, "ms.collection": [ "tier2" ],