Update troubleshoot-session-creation-errrors.md

Author: johndund

support/power-platform/power-automate/desktop-flows/troubleshoot-session-creation-errrors.md

@@ -53,7 +53,7 @@ To solve the issue:
 - Ensure that you can remote desktop to the machine from another machine on your network. If you're using Windows Server, you can try to remote desktop to "localhost" from the local machine itself when logged in as another account. If these actions fail, see [General Remote Desktop connection troubleshooting](../../../windows-server/remote/rdp-error-general-troubleshooting.md).
 - If you have a legal notice enabled for login, work with your system administrator to try disabling it. To see if the legal notice is activated, open Registry Editor and go to `Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System`. If `legalnoticecaption` or `legalnoticetext` isn't empty, work with your system administrator to disable the legal notice.
 - Ensure that no third-party software is installed that might affect login or interfere with creating a remote desktop connection.
-- If you are connecting using a domain account (DOMAIN\user), connectivity problems may be causing the session not to properly open. Please work with your system administrator to examine connectivity logs. If you are on an Microsoft Entra ID joined or Entra hybrid joined device, please try using a UPN ([email protected]) to see if this resolves the problem. You can find out if you can use a UPN by going to start > run and running `dsregcmd /status`. If under "Device State" you see "AzureAdJoined: YES", then try changing the user specified the connection to the form [email protected].
+- If you are connecting using a domain account (DOMAIN\user), connectivity problems to your domain controller may be causing the session not to properly open. Please work with your system administrator to examine connectivity logs. If you are on an Microsoft Entra ID joined or Entra hybrid joined device, please try using a UPN ([email protected]) to see if this resolves the problem. You can find out if you can use a UPN by going to start > run and running `dsregcmd /status`. If under "Device State" you see "AzureAdJoined: YES", then try changing the user specified the connection to the form [email protected].
 
 
 [!INCLUDE [Third-party disclaimer](../../../includes/third-party-disclaimer.md)]