You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/virtual-desktop/configure-session-lock-behavior.md
+7-11Lines changed: 7 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,12 +4,12 @@ description: Learn how to configure session lock behavior for Azure Virtual Desk
4
4
ms.topic: how-to
5
5
author: dknappettmsft
6
6
ms.author: daknappe
7
-
ms.date: 09/02/2024
7
+
ms.date: 09/17/2024
8
8
---
9
9
10
10
# Configure the session lock behavior for Azure Virtual Desktop
11
11
12
-
You can choose whether the session is disconnected or the remote lock screen shown when a remote session is locked, either by the user or by policy. When the session lock behavior is set to disconnect, a dialog is shown to let users know they were disconnected. Users can choose the **Reconnect** option from the dialog when they're ready to connect again.
12
+
You can choose whether the session is disconnected or the remote lock screen is shown when a remote session is locked, either by the user or by policy. When the session lock behavior is set to disconnect, a dialog is shown to let users know they were disconnected. Users can choose the **Reconnect** option from the dialog when they're ready to connect again.
13
13
14
14
When used with single sign-on using Microsoft Entra ID, disconnecting the session provides the following benefits:
15
15
@@ -23,7 +23,7 @@ When used with single sign-on using Microsoft Entra ID, disconnecting the sessio
23
23
24
24
- You can require multifactor authentication to return to the session and prevent users from unlocking with a simple username and password.
25
25
26
-
For scenarios that rely on legacy authentication, including NTLM, CredSSP, RDSTLS, TLS, and RDP basic authentication protocols, users are prompted to re-enter their credentials.
26
+
For scenarios that rely on legacy authentication, including NTLM, CredSSP, RDSTLS, TLS, and RDP basic authentication protocols, users are prompted to re-enter their credentials when they reconnect or start a new connection.
27
27
28
28
The default session lock behavior is different depending on whether you're using single sign-on with Microsoft Entra ID or legacy authentication. The following table shows the default configuration for each scenario:
29
29
@@ -128,9 +128,9 @@ To configure the session lock experience using Intune:
128
128
129
129
To configure the session lock experience using Group Policy, follow these steps.
130
130
131
-
1. The Group Policy settings are only available the operating systems listed in [Prerequisites](#prerequisites). To make them available on other versions of Windows Server, you need to copy the administrative template files `C:\Windows\PolicyDefinitions\terminalserver.admx` and `C:\Windows\PolicyDefinitions\en-US\terminalserver.adml` from a session host to the same location on your domain controllers or the [Group Policy Central Store](/troubleshoot/windows-client/group-policy/create-and-manage-central-store), depending on your environment. In the file path for `terminalserver.adml` replace `en-US` with the appropriate language code if you're using a different language.
131
+
1. The Group Policy settings are only available on the operating systems listed in [Prerequisites](#prerequisites). To make them available on other versions of Windows Server, you need to copy the administrative template files `C:\Windows\PolicyDefinitions\terminalserver.admx` and `C:\Windows\PolicyDefinitions\en-US\terminalserver.adml` from a session host to the same location on your domain controllers or the [Group Policy Central Store](/troubleshoot/windows-client/group-policy/create-and-manage-central-store), depending on your environment. In the file path for `terminalserver.adml` replace `en-US` with the appropriate language code if you're using a different language.
132
132
133
-
1. Open the **Group Policy Management** console on device you use to manage the Active Directory domain.
133
+
1. Open the **Group Policy Management** console on the device you use to manage the Active Directory domain.
134
134
135
135
1. Create or edit a policy that targets the computers providing a remote session you want to configure.
136
136
@@ -154,9 +154,9 @@ To configure the session lock experience using Group Policy, follow these steps.
154
154
155
155
1. Double-click **Disconnect remote session on lock for legacy authentication** to open it.
156
156
157
-
- To disconnect the remote session when the session locks, select **Enabled** or **Not configured**.
157
+
- To disconnect the remote session when the session locks, select **Enabled**.
158
158
159
-
- To show the remote lock screen when the session locks, select **Disabled**.
159
+
- To show the remote lock screen when the session locks, select **Disabled** or **Not configured**.
160
160
161
161
1. Select **OK**.
162
162
@@ -169,7 +169,3 @@ To configure the session lock experience using Group Policy, follow these steps.
169
169
## Related content
170
170
171
171
- Learn how to [Configure single sign-on for Azure Virtual Desktop using Microsoft Entra ID](configure-single-sign-on.md).
172
-
173
-
- Check out [In-session passwordless authentication](authentication.md#in-session-passwordless-authentication) to learn how to enable passwordless authentication.
174
-
175
-
- For more information about Microsoft Entra Kerberos, see [Deep dive: How Microsoft Entra Kerberos works](https://techcommunity.microsoft.com/t5/itops-talk-blog/deep-dive-how-azure-ad-kerberos-works/ba-p/3070889)
Copy file name to clipboardExpand all lines: articles/virtual-desktop/configure-single-sign-on.md
+4-6Lines changed: 4 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ description: Learn how to configure single sign-on for an Azure Virtual Desktop
4
4
ms.topic: how-to
5
5
author: dknappettmsft
6
6
ms.author: daknappe
7
-
ms.date: 09/02/2024
7
+
ms.date: 09/17/2024
8
8
---
9
9
10
10
# Configure single sign-on for Azure Virtual Desktop using Microsoft Entra ID
@@ -17,7 +17,7 @@ To enable single sign-on using Microsoft Entra ID authentication, there are five
17
17
18
18
1. Enable Microsoft Entra authentication for Remote Desktop Protocol (RDP).
19
19
20
-
1.Configure the target device groups.
20
+
1.Hide the consent prompt dialog.
21
21
22
22
1. Create a *Kerberos Server object*, if Active Directory Domain Services is part of your environment. More information on the criteria is included in its section.
23
23
@@ -31,9 +31,9 @@ Before you enable single sign-on, review the following information for using it
31
31
32
32
### Session lock behavior
33
33
34
-
When single sign-on using Microsoft Entra ID is enabled and the remote session is locked, either by the user or by policy, you can choose whether the session is disconnected or the remote lock screen shown. The default behavior is to disconnect the session when it locks.
34
+
When single sign-on using Microsoft Entra ID is enabled and the remote session is locked, either by the user or by policy, you can choose whether the session is disconnected or the remote lock screen is shown. The default behavior is to disconnect the session when it locks.
35
35
36
-
When the session lock behavior is set to disconnect, and a dialog is shown to let users know they were disconnected. Users can choose the **Reconnect** option from the dialog when they're ready to connect again. This behavior is done for security reasons and to ensure full support of passwordless authentication. Disconnecting the session provides the following benefits:
36
+
When the session lock behavior is set to disconnect, a dialog is shown to let users know they were disconnected. Users can choose the **Reconnect** option from the dialog when they're ready to connect again. This behavior is done for security reasons and to ensure full support of passwordless authentication. Disconnecting the session provides the following benefits:
37
37
38
38
- Consistent sign-in experience through Microsoft Entra ID when needed.
39
39
@@ -89,8 +89,6 @@ Before you can enable single sign-on, you must meet the following prerequisites:
89
89
90
90
-[Android client](users/connect-android-chrome-os.md), version 10.0.16 or later.
91
91
92
-
- To configure allowing Active Directory domain administrator account to connect when single sign-on is enabled, you need an account that is a member of the **Domain Admins** security group.
93
-
94
92
## Enable Microsoft Entra authentication for RDP
95
93
96
94
You must first allow Microsoft Entra authentication for Windows in your Microsoft Entra tenant, which enables issuing RDP access tokens allowing users to sign in to your Azure Virtual Desktop session hosts. You set the `isRemoteDesktopProtocolEnabled` property to true on the service principal's `remoteDesktopSecurityConfiguration` object for the following Microsoft Entra applications:
0 commit comments