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/active-directory/devices/howto-vm-sign-in-azure-ad-windows.md
+15-4Lines changed: 15 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,8 +31,8 @@ There are many benefits of using Azure AD authentication to log in to Windows VM
31
31
- Azure RBAC allows you to grant the appropriate access to VMs based on need and remove it when it is no longer needed.
32
32
- Before allowing access to a VM, Azure AD Conditional Access can enforce additional requirements such as:
33
33
- Multi-factor authentication
34
-
- Sign-in risk
35
-
- Automate and scale Azure AD join for Azure based Windows VMs.
34
+
- Sign-in risk check
35
+
- Automate and scale Azure AD join of Azure Windows VMs that are part for your VDI deployments.
36
36
37
37
## Requirements
38
38
@@ -65,7 +65,7 @@ To use Azure AD login in for Windows VM in Azure, you need to first enable Azure
65
65
There are multiple ways you can enable Azure AD login for your Windows VM:
66
66
67
67
- Using the Azure portal experience when creating a Windows VM
68
-
- Using the Azure Cloud Shell experience when creating a Windows VM or for an existing Windows VM
68
+
- Using the Azure Cloud Shell experience when creating a Windows VM **or for an existing Windows VM**
69
69
70
70
### Using Azure portal create VM experience to enable Azure AD login
71
71
@@ -184,6 +184,14 @@ For more information on how to use RBAC to manage access to your Azure subscript
184
184
-[Manage access to Azure resources using RBAC and the Azure portal](https://docs.microsoft.com/azure/role-based-access-control/role-assignments-portal)
185
185
-[Manage access to Azure resources using RBAC and Azure PowerShell](https://docs.microsoft.com/azure/role-based-access-control/role-assignments-powershell).
186
186
187
+
## Using Conditional Access
188
+
189
+
You can enforce Conditional Access policies such as multi-factor authentication or user sign-in risk check before authorizing access to Windows VMs in Azure that are enabled with Azure AD sign in. To apply Conditional Access policy, you must select "Azure Windows VM Sign-In" app from the cloud apps or actions assignment option and then use Sign-in risk as a condition and/or
190
+
require multi-factor authentication as a grant access control.
191
+
192
+
> [!NOTE]
193
+
> If you use "Require multi-factor authentication" as a grant access control for requesting access to "Azure Windows VM Sign-In" app, then you must supply multi-factor authentication claim as part of the client that initiates the RDP session to the target Windows VM in Azure. The only way to achieve this on a Windows 10 client is to use Windows Hello for Business PIN or biometric auth during RDP. Biometric auth for RDP is supported starting Windows 10 1809. Using Windows Hello for Business auth during RDP is only available for deployments that use cert trust model and currently not available for key trust model.
194
+
187
195
## Log in using Azure AD credentials to a Windows VM
188
196
189
197
> [!IMPORTANT]
@@ -334,7 +342,10 @@ If you see the following error message when you initiate a remote desktop connec
334
342
335
343

336
344
337
-
If you have configured a Conditional Access policy that requires MFA to be done before you can access the RBAC resource, then you need to ensure that the Windows 10 PC initiating the remote desktop connection to your VM signs in using a strong authentication method such as Windows Hello. If you do not use a strong authentication method for your remote desktop connection, you will see the following error.
345
+
If you have configured a Conditional Access policy that requires MFA to be done before you can access the RBAC resource, then you need to ensure that the Windows 10 PC initiating the remote desktop connection to your VM signs in using a strong authentication method such as Windows Hello. If you do not use a strong authentication method for your remote desktop connection, you will see the following error. If you have not deployed Windows Hello for Business and if that is not an option for now, you can exlcude MFA requirement by configuring Conditional Access policy that excludes "Azure Windows VM Sign-In" app from the list of cloud apps that require MFA. To learn more about Windows Hello for Business, see [Windows Hello for Business Overview] (https://docs.microsoft.com/en-us/windows/security/identity-protection/hello-for-business/hello-identity-verification).
346
+
347
+
> [!NOTE]
348
+
> Windows Hello for Business PIN auth during RDP has been supported for long now, however using Biometric auth for RDP is supported starting Windows 10 1809. Using Windows Hello for Business auth during RDP is only available for deployments that use cert trust model and currently not available for key trust model.
0 commit comments