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: windows-365/enterprise/identity-and-authentication.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -69,7 +69,7 @@ To complete the end to end connection of accessing a Cloud PC, users must first
69
69
The Windows 365 service authentication surfaces in one of two ways:
70
70
71
71
- When users access [windows365.microsoft.com](https://windows365.microsoft.com) or launch the web browser URL that maps directirecly to their Cloud PC.
72
-
- When users access through one of the [Remote Desktop clients](/windows-server/remote/remote-desktop-services/clients/remote-desktop-clients) and list their Cloud PCs.
72
+
- When users access through one of the [Remote Desktop clients](/windows-server/remote/remote-desktop-services/clients/remote-desktop-clients.md) and list their Cloud PCs.
73
73
74
74
This authentication triggers an Azure Active Directory prompt, allowing any credential type that is supported by both Azure Active Directory and your OS.
75
75
@@ -78,7 +78,7 @@ This authentication triggers an Azure Active Directory prompt, allowing any cred
78
78
The Cloud PC authentication surfaces in one of the two ways:
79
79
80
80
- When users launch the web browser URL that maps directly to their Cloud PC.
81
-
- When users access through one of the [Remote Desktop clients](/windows-server/remote/remote-desktop-services/clients/remote-desktop-clients) and select the specific Cloud PC.
81
+
- When users access through one of the [Remote Desktop clients](/windows-server/remote/remote-desktop-services/clients/remote-desktop-clients.md) and select the specific Cloud PC.
82
82
83
83
>[!NOTE]
84
84
>If a user launches the web browser URL that maps directly to their Cloud PC, they will encounter the Windows 365 service authentication first, then encounter the Cloud PC authentication.
@@ -87,8 +87,8 @@ The following credential types are supported for Cloud PC authentication:
87
87
- Windows desktop client
88
88
- Username and password
89
89
- Smartcard
90
-
-[Windows Hello for Business certificate trust](/windows/security/identity-protection/hello-for-business/hello-hybrid-cert-trust)
91
-
-[Windows Hello for Business key trust with certificates](/windows/security/identity-protection/hello-for-business/hello-deployment-rdp-certs)
90
+
-[Windows Hello for Business certificate trust](/windows/security/identity-protection/hello-for-business/hello-hybrid-cert-trust.md)
91
+
-[Windows Hello for Business key trust with certificates](/windows/security/identity-protection/hello-for-business/hello-deployment-rdp-certs.md)
92
92
- Windows store client
93
93
- Username and password
94
94
- Web client
@@ -101,7 +101,7 @@ The following credential types are supported for Cloud PC authentication:
101
101
- Username and password
102
102
103
103
>[!IMPORTANT]
104
-
>In order for authentication to work properly, the user's local machine must also be able to access the URLs in the [Remote Desktop clients](safe-url-list.md#remote-desktop-clients) section of the [Azure Virtual Desktop required URL list](safe-url-list.md).
104
+
>In order for authentication to work properly, the user's local machine must also be able to access the URLs in the [Remote Desktop clients](/azure/virtual-desktop/safe-url-list.md#remote-desktop-clients) section of the [Azure Virtual Desktop required URL list](/azure/virtual-desktop/safe-url-list.md).
0 commit comments