Skip to content

Commit a82c68e

Browse files
committed
Added more info
1 parent 6f5d927 commit a82c68e

File tree

1 file changed

+10
-4
lines changed

1 file changed

+10
-4
lines changed

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

Lines changed: 10 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -34,12 +34,18 @@ Before you enable single sign-on, review the following information for using it
3434
When single sign-on is enabled and the remote session is locked, either by the user or by policy, the session is instead disconnected and a dialog is shown. Users can select the Reconnect option from the dialog when they are ready to connect again. This is done for security reason and to ensure full support of passwordless authentication. Disconnecting provides the following benefits:
3535

3636
- Consistent sign-in experience through Microsoft Entra ID when needed.
37+
- Single sign-on experience and reconnection without authentication prompt when allowed by conditional access policies.
3738
- Supports passwordless authentication like passkeys and FIDO2 devices, contrary to the remote lock screen.
39+
- Conditional access policies, including multifactor authentication and sign-in frequency, are re-evaluated when the user reconnects to their session.
3840
- Can require multi-factor authentication to return to the session and prevent users from unlocking with a simple username and password.
39-
- Reevaluates any applicable Microsoft Entra conditional access policies including sign-in frequency.
40-
- When meeting all conditional access requirements, users benefit from Entra single sign-on when reconnecting and are not prompted to re-authenticate.
4141

42-
If you prefer to show the remote lock screen instead of disconnecting the session, you can configure your session hosts using Intune, Group Policy or the registry.
42+
If you prefer to show the remote lock screen instead of disconnecting the session, your session hosts must use the following operating systems:
43+
44+
- Windows 11 single or multi-session with the [2024-05 Cumulative Updates for Windows 11 (KB5037770)](https://support.microsoft.com/kb/KB5037770) or later installed.
45+
- Windows 10 single or multi-session, versions 20H2 or later with the [2024-06 Cumulative Updates for Windows 10 (KB5039211)](https://support.microsoft.com/kb/KB5039211) or later installed.
46+
- Windows Server 2022 with the [2024-05 Cumulative Update for Microsoft server operating system (KB5037782)](https://support.microsoft.com/kb/KB5037782) or later installed.
47+
48+
You can configure the session lock behavior of your session hosts by using Intune, Group Policy or the registry.
4349

4450
# [Intune](#tab/intune)
4551

@@ -103,7 +109,7 @@ To configure the session lock experience using Group Policy, follow these steps.
103109
1. Once the policy is configured, it will take effect after the user initiate a new session.
104110

105111
> [!TIP]
106-
> During the preview, you can also configure Group Policy centrally in an Active Directory domain by copying the `terminalserver.admx` and `terminalserver.adml` administrative template files from a session host to the [Group Policy Central Store](/troubleshoot/windows-client/group-policy/create-and-manage-central-store) in a test environment.
112+
> To configure the Group Policy centrally on Active Directory Domain Controllers using Windows Server 2019 or Windows Server 2016, copy the `terminalserver.admx` and `terminalserver.adml` administrative template files from a session host to the [Group Policy Central Store](/troubleshoot/windows-client/group-policy/create-and-manage-central-store) on the domain controller.
107113
108114
# [Registry](#tab/registry)
109115

0 commit comments

Comments
 (0)