From 98219285b1a11f47de74c71b1818a1d3f3c6803e Mon Sep 17 00:00:00 2001
From: ImranHabib <47118050+joinimran@users.noreply.github.com>
Date: Sun, 3 Nov 2019 10:14:09 +0500
Subject: [PATCH] Added a note

Added a note if users are not able to connect using RDP 6.0 then follow the steps mentioned in a support article.

Problem: https://github.com/MicrosoftDocs/windows-itpro-docs/issues/4616
---
 windows/client-management/connect-to-remote-aadj-pc.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/windows/client-management/connect-to-remote-aadj-pc.md b/windows/client-management/connect-to-remote-aadj-pc.md
index c265525536..83265eece0 100644
--- a/windows/client-management/connect-to-remote-aadj-pc.md
+++ b/windows/client-management/connect-to-remote-aadj-pc.md
@@ -55,6 +55,8 @@ Ensure [Remote Credential Guard](/windows/access-protection/remote-credential-gu
   >[!TIP]
   >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).
  
 ## Supported configurations