Skip to content

Commit 0e80ae3

Browse files
Merge pull request #210047 from davidbel/davidbel-41123283-sso-public-preview
SSO and Passwordless updates for Public Preview
2 parents 2049e42 + 01e55f2 commit 0e80ae3

File tree

2 files changed

+16
-16
lines changed

2 files changed

+16
-16
lines changed

articles/virtual-desktop/authentication.md

Lines changed: 7 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: virtual-desktop
55
author: Heidilohr
66
ms.service: virtual-desktop
77
ms.topic: conceptual
8-
ms.date: 08/25/2022
8+
ms.date: 09/22/2022
99
ms.author: helohr
1010
manager: femila
1111
---
@@ -103,16 +103,17 @@ Once you're connected to your remote app or desktop, you may be prompted for aut
103103
### In-session passwordless authentication (preview)
104104

105105
> [!IMPORTANT]
106-
> In-session passwordless authentication is currently in Insider preview.
106+
> In-session passwordless authentication is currently in public preview.
107107
> This preview version is provided without a service level agreement, and is not recommended for production workloads. Certain features might not be supported or might have constrained capabilities.
108108
> For more information, see [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
109109
110-
Azure Virtual Desktop supports in-session passwordless authentication (preview) using [Windows Hello for Business](/windows/security/identity-protection/hello-for-business/hello-overview) or security devices like FIDO keys. Passwordless authentication is currently only available for certain versions of Windows Insider. When deploying new session hosts, choose one of the following images:
110+
Azure Virtual Desktop supports in-session passwordless authentication (preview) using [Windows Hello for Business](/windows/security/identity-protection/hello-for-business/hello-overview) or security devices like FIDO keys when using the [Windows Desktop client](user-documentation/connect-windows-7-10.md). Passwordless authentication is enabled automatically when the session host and local PC are using the following operating systems:
111111

112-
- Windows 11 version 22H2 Enterprise, (Preview) - X64 Gen 2.
113-
- Windows 11 version 22H2 Enterprise multi-session, (Preview) - X64 Gen2.
112+
- Windows 11 Enterprise single or multi-session with the [2022-09 Cumulative Updates for Windows 11 Preview (KB5017383)](https://support.microsoft.com/kb/KB5017383) or later installed.
113+
- Windows 10 Enterprise single or multi-session, versions 20H2 or later with the [2022-09 Cumulative Updates for Windows 10 Preview (KB5017380)](https://support.microsoft.com/kb/KB5017380) or later installed.
114+
- Windows Server 2022 with the [2022-09 Cumulative Update for Microsoft server operating system preview (KB5017381)](https://support.microsoft.com/kb/KB5017381) or later installed.
114115

115-
Passwordless authentication is enabled by default when the local PC and session hosts use one of the supported operating systems above. You can disable it using the [WebAuthn redirection](configure-device-redirections.md#webauthn-redirection) RDP property.
116+
To disable passwordless authentication on your host pool, you must [customize an RDP property](customize-rdp-properties.md). You can find the **WebAuthn redirection** property under the **Device redirection** tab in the Azure portal or set the **redirectwebauthn** property to **0** using PowerShell.
116117

117118
When enabled, all WebAuthn requests in the session are redirected to the local PC. You can use Windows Hello for Business or locally attached security devices to complete the authentication process.
118119

articles/virtual-desktop/configure-single-sign-on.md

Lines changed: 9 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -7,13 +7,13 @@ manager: femila
77

88
ms.service: virtual-desktop
99
ms.topic: how-to
10-
ms.date: 08/25/2022
10+
ms.date: 09/22/2022
1111
ms.author: helohr
1212
---
1313
# Configure single sign-on for Azure Virtual Desktop
1414

1515
> [!IMPORTANT]
16-
> Single sign-on using Azure AD authentication is currently in Insider preview.
16+
> Single sign-on using Azure AD authentication is currently in public preview.
1717
> This preview version is provided without a service level agreement, and is not recommended for production workloads. Certain features might not be supported or might have constrained capabilities.
1818
> For more information, see [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
1919
@@ -24,25 +24,23 @@ This article will walk you through the process of configuring single sign-on (SS
2424
2525
## Prerequisites
2626

27-
Single sign-on is currently only available for certain versions of Windows Insider. When deploying new session hosts, you must choose one of the following images:
27+
Single sign-on is available on session hosts using the following operating systems:
2828

29-
- Windows 11 version 22H2 Enterprise, (Preview) - X64 Gen 2.
30-
- Windows 11 version 22H2 Enterprise multi-session, (Preview) - X64 Gen2.
29+
- Windows 11 Enterprise single or multi-session with the [2022-09 Cumulative Updates for Windows 11 Preview (KB5017383)](https://support.microsoft.com/kb/KB5017383) or later installed.
30+
- Windows 10 Enterprise single or multi-session, versions 20H2 or later with the [2022-09 Cumulative Updates for Windows 10 Preview (KB5017380)](https://support.microsoft.com/kb/KB5017380) or later installed.
31+
- Windows Server 2022 with the [2022-09 Cumulative Update for Microsoft server operating system preview (KB5017381)](https://support.microsoft.com/kb/KB5017381) or later installed.
3132

3233
You can enable SSO for connections to Azure Active Directory (AD)-joined VMs. You can also use SSO to access Hybrid Azure AD-joined VMs, but only after creating a Kerberos Server object. Azure Virtual Desktop doesn't support this solution with VMs joined to Azure AD Domain Services.
3334

34-
> [!NOTE]
35-
> Hybrid Azure AD-joined Windows Server 2019 VMs don't support SSO.
36-
37-
Currently, the [Windows Desktop client](./user-documentation/connect-windows-7-10.md) is the only client that supports SSO. The local PC must be running Windows 10 or later. There's no domain join requirement for the local PC.
35+
You can use the [Windows Desktop client](user-documentation/connect-windows-7-10.md) on local PCs running Windows 10 or later. There's no requirement for the local PC to be joined to a domain or Azure AD. You can also have a single sign-on experience when using the [web client](user-documentation/connect-web.md).
3836

3937
SSO is currently supported in the Azure Public cloud.
4038

4139
## Enable single sign-on
4240

4341
If your host pool contains Hybrid Azure AD-joined session hosts, you must first enable Azure AD Kerberos in your environment by creating a Kerberos Server object. Azure AD Kerberos enables the authentication needed with the domain controller. We recommended you also enable Azure AD Kerberos for Azure AD-joined session hosts if you have a Domain Controller (DC). Azure AD Kerberos provides a single sign-on experience when accessing legacy Kerberos-based applications or network shares. To enable Azure AD Kerberos in your environment, follow the steps to [Create a Kerberos Server object](../active-directory/authentication/howto-authentication-passwordless-security-key-on-premises.md#create-a-kerberos-server-object) on your DC.
4442

45-
To enable SSO on your host pool, you must [customize an RDP property](customize-rdp-properties.md). You can find the **Azure AD Authentication** property under the **Connection information** tab in the Azure portal or set the **enablerdsaadauth:i:1** property using PowerShell.
43+
To enable SSO on your host pool, you must [customize an RDP property](customize-rdp-properties.md). You can find the **Azure AD Authentication** property under the **Connection information** tab in the Azure portal or set the **enablerdsaadauth** property to **1** using PowerShell.
4644

4745
> [!IMPORTANT]
4846
> If you enable SSO on your Hybrid Azure AD-joined VMs before you create the Kerberos server object, you won't be able to connect to the VMs, and you'll see an error message saying the specific log on session doesn't exist.
@@ -55,4 +53,5 @@ When enabling single sign-on, you'll currently be prompted to authenticate to Az
5553

5654
- Check out [In-session passwordless authentication (preview)](authentication.md#in-session-passwordless-authentication-preview) to learn how to enable passwordless authentication.
5755
- If you're accessing Azure Virtual Desktop from our Windows Desktop client, see [Connect with the Windows Desktop client](./user-documentation/connect-windows-7-10.md).
56+
- If you're accessing Azure Virtual Desktop from our web client, see [Connect with the web client](./user-documentation/connect-web.md).
5857
- If you encounter any issues, go to [Troubleshoot connections to Azure AD-joined VMs](troubleshoot-azure-ad-connections.md).

0 commit comments

Comments
 (0)