From 0a1acf8ef0410fde34085d066025734ca49b8ed8 Mon Sep 17 00:00:00 2001
From: ImranHabib <47118050+joinimran@users.noreply.github.com>
Date: Sun, 3 Nov 2019 22:55:09 +0500
Subject: [PATCH] Update windows/client-management/connect-to-remote-aadj-pc.md

Co-Authored-By: Trond B. Krokli <38162891+illfated@users.noreply.github.com>
---
 windows/client-management/connect-to-remote-aadj-pc.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/windows/client-management/connect-to-remote-aadj-pc.md b/windows/client-management/connect-to-remote-aadj-pc.md
index 83265eece0..e78fb9db09 100644
--- a/windows/client-management/connect-to-remote-aadj-pc.md
+++ b/windows/client-management/connect-to-remote-aadj-pc.md
@@ -56,7 +56,7 @@ Ensure [Remote Credential Guard](/windows/access-protection/remote-credential-gu
   >When you connect to the remote PC, enter your account name in this format: `AzureAD UPN`. The local PC must either be domain-joined or Azure AD-joined. The local PC and remote PC must be in the same Azure AD tenant.
 
 > [!Note]
-> If you cannot connect using Remote Desktop Connection 6.0 then turn off new features of RDP 6.0 and revert back to RDP 5.0 by tweaking a few changes in the RDP file. See the details in the support [article](https://support.microsoft.com/en-ph/help/941641/remote-desktop-connection-6-0-prompts-you-for-credentials-before-you-e).
+> If you cannot connect using Remote Desktop Connection 6.0, then turn off new features of RDP 6.0 and revert back to RDP 5.0 by tweaking a few changes in the RDP file. See the details in the [support article](https://support.microsoft.com/en-ph/help/941641/remote-desktop-connection-6-0-prompts-you-for-credentials-before-you-e).
  
 ## Supported configurations