Merge pull request #8184 from MicrosoftDocs/users/johndund/credsupdate

AB#3780: Update creds management page with updated error codes and guidance

Author: lucciz01

support/power-platform/power-automate/desktop-flows/invalid-credentials-errors-running-desktop-flows.md

@@ -3,7 +3,7 @@ title: Invalid credentials error running desktop flows
 description: Provides a resolution for the invalid credentials error that might occur when you run a desktop flow in Power Automate.
 ms.reviewer: guco, johndund
 ms.custom: sap:Desktop flows\Cannot create desktop flow connection
-ms.date: 01/03/2025
+ms.date: 02/17/2025
 ---
 # Invalid credentials error when running desktop flows in Power Automate for desktop
 
@@ -31,15 +31,15 @@ _Original KB number:_   5021155
   ```
 
 > [!NOTE]
-> In case of a connection error, the best test is to connect to the same machine with  Remote Desktop and use the same credentials that you used when creating the desktop flow.
+> If there's a connection error, the best test is to connect to the same machine with  Remote Desktop and use the same credentials that you used when creating the desktop flow.
 
 ## Cause
 
 The error messages occur because the credentials in the connection can't authenticate on the target machine.
 
 When you create a connection, Power Automate checks to ensure the credentials are valid. If the credentials don't authenticate on the target machine, the connection can't be made, and you receive an error describing the problem.
 
-If you successfully created your connection earlier but now encounter an error when running your flow, it indicates that something has changed in your user account or machine (for example, your password might have expired.)
+If you successfully created your connection earlier but now encounter an error when running your flow, it indicates that something has changed in your user account or machine. For example, your password might have expired.
 
 ## Resolution
 
@@ -50,7 +50,8 @@ To see an error message with specific details on what went wrong, ensure you hav
 |-1073741477|A user has requested a type of logon (for example, interactive or network) that has not been granted. An administrator has control over who can logon interactively and through the network.|The user account doesn't have logon rights on the machine, or the administrator changed the policies of the machine (check the [User Rights Assignment](/previous-versions/windows/it-pro/windows-10/security/threat-protection/security-policy-settings/user-rights-assignment) settings).|To solve this issue, see ["Logon type has not been granted" error when running a desktop flow or creating a connection](logon-type-has-not-been-granted.md).|
 |-1073445812|The user's UPN isn't in the expected format|The user signed in using `DOMAIN\user` but should use the `[email protected]` format instead (or vice versa).|Try to sign in using both the `[email protected]` and `DOMAIN\user` formats.|
 |-1073741062|Smart card logon is required and was not used| |Connections to machines that require smart card logons aren't supported. Use a machine without this requirement.|
-|-1073741715|Bad username or authentication information| The "executing account name" or the format of your username is incorrect. |Run the [dsregcmd /status](/entra/identity/devices/troubleshoot-device-dsregcmd) command in the context of the desktop flow connection account. Check the `Executing Account Name` section in the output and make sure it matches the username that was used. [Microsoft Entra joined](/entra/identity/devices/concept-directory-join) or hybrid devices always prefer the UPN  `[email protected]` format. If your machine is Microsoft Entra joined, use the `[email protected]` format for your username. You should only use the `DOMAIN\user` format if your device is domain-only joined.|
+|-1073741715|Bad username or authentication information| The given credentials aren't correct. This issue might occur due to an incorrect user/password combination or username format.|1. Double-check that your username and password work on the machine. You can do this by signing out and signing back in with the same credentials. </br>2. If that works, verify you're using the correct username format by running the [dsregcmd /status](/entra/identity/devices/troubleshoot-device-dsregcmd) command in the context of the desktop flow connection account. Check the `Executing Account Name` value (in the `Diagnostic Data` section) in the output and make sure it matches the username that was used. </br>3. If your machine is [Microsoft Entra joined](/entra/identity/devices/concept-directory-join) or hybrid, use the `[email protected]` format. If your machine is domain-only joined, use the `DOMAIN\user` format. </br></br>To determine the correct username format, check your machine's join state:</br> a. Run the [dsregcmd /status](/entra/identity/devices/troubleshoot-device-dsregcmd) command. </br>b. Look for the `Device State` section in the output: </br>- If you see `AzureAdJoined : YES`, your machine is Microsoft Entra joined. </br>- If it says `NO` after `AzureAdJoined` but `YES` after `DomainJoined`, your machine is domain-only joined. |
+|-1073741730|The domain isn't available| | Make sure you're using the correct username format for your machine join state. If your machine is [Microsoft Entra joined](/entra/identity/devices/concept-directory-join) or hybrid, use the `[email protected]` format. If your machine is domain-only joined, use the `DOMAIN\user` format. </br></br>To determine the correct username format, check your machine's join state: </br>1. Run the [dsregcmd /status](/entra/identity/devices/troubleshoot-device-dsregcmd) command. </br>2. Look for the `Device State` section in the output: </br>- If you see `AzureAdJoined : YES`, your machine is Microsoft Entra joined. </br>- If it says `NO` after `AzureAdJoined` but `YES` after `DomainJoined`, your machine is domain-only joined. |
 
 If you don't have a more specific error associated with the problem, the easiest way to troubleshoot is to sign in to the machine with the exact credentials you entered in your connection. You can try this method by signing in to the machine locally or through a Remote Desktop connection. You should receive the same error message that Power Automate receives when trying to authenticate your credentials, which should help you troubleshoot the issue.