Merge pull request #8576 from MicrosoftDocs/users/johndund/newerrorcodes

AB#5291: Update credential issues documentation with some new error codes from a CSS case

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: 02/17/2025
+ms.date: 04/08/2025
 ---
 # Invalid credentials error when running desktop flows in Power Automate for desktop
 
@@ -52,6 +52,8 @@ To see an error message with specific details on what went wrong, ensure you hav
 |-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 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. |
+|-1073741714|User account restriction has prevented successful authentication | The referenced username and authentication information are valid, but a user account restriction, such as time-of-day restrictions, has prevented successful authentications.| Confirm that no security or account restriction policies prevent this user from successfully signing in.|
+|-1073741712|The user account is restricted such that it may not be used to log on from the source workstation | | Confirm that no security or account restriction policies prevent this user from successfully signing in.|
 
 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.