Skip to content

Commit c3a58ff

Browse files
Fix .md references
1 parent ee9a6c0 commit c3a58ff

1 file changed

Lines changed: 5 additions & 5 deletions

File tree

windows-365/enterprise/identity-and-authentication.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -69,7 +69,7 @@ To complete the end to end connection of accessing a Cloud PC, users must first
6969
The Windows 365 service authentication surfaces in one of two ways:
7070

7171
- 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.
7373

7474
This authentication triggers an Azure Active Directory prompt, allowing any credential type that is supported by both Azure Active Directory and your OS.
7575

@@ -78,7 +78,7 @@ This authentication triggers an Azure Active Directory prompt, allowing any cred
7878
The Cloud PC authentication surfaces in one of the two ways:
7979

8080
- 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.
8282

8383
>[!NOTE]
8484
>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:
8787
- Windows desktop client
8888
- Username and password
8989
- 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)
9292
- Windows store client
9393
- Username and password
9494
- Web client
@@ -101,7 +101,7 @@ The following credential types are supported for Cloud PC authentication:
101101
- Username and password
102102

103103
>[!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).
105105
106106
<!-- ########################## -->
107107
## Next steps

0 commit comments

Comments
 (0)