minor change

lucciz01 · web-flow · commit da4a9804edea · 2024-12-25T13:48:04.000+08:00
diff --git a/support/power-platform/power-automate/desktop-flows/invalid-credentials-errors-running-desktop-flows.md b/support/power-platform/power-automate/desktop-flows/invalid-credentials-errors-running-desktop-flows.md
@@ -50,7 +50,7 @@ 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 `user@domain.com` format instead (or vice versa).|Try to sign in using both the `user@domain.com` 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 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  `user@domain.com` format. If your machine is Microsoft Entra joined, use the `user@domain.com` 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 "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  `user@domain.com` format. If your machine is Microsoft Entra joined, use the `user@domain.com` format for your username. You should only use the `DOMAIN\user` format if your device 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.
 

-Original file line number
+Diff line change
 |-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 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 "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.|
 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.