Skip to content

Commit 9e6a9a3

Browse files
v-tappelgatev-tappelgate
committed
Merge remote-tracking branch 'upstream/main' into AB#7616-Troubleshoot-Windows-Update-Error-0x800719e4
2 parents 5e4a99c + 1ee9850 commit 9e6a9a3

7 files changed

Lines changed: 101 additions & 25 deletions

File tree

‎Exchange/ExchangeOnline/administration/self-help-diagnostics.md‎

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -49,7 +49,6 @@ Several diagnostics currently cover the various areas within Exchange Online and
4949
|Exchange Organization Object check|Check health and resolve issues related to your Exchange Online organization object. For example, Exchange Online tenant provisioning or RBAC-related issues (various commands aren't available even though users have permissions).|[Run Tests: Exchange organization object](https://aka.ms/PillarEXOOrgCheck)||
5050
|Mailbox or message size|Check the size of a mailbox or the size of messages (including attachments).|[Run Tests: Mailbox Size](https://aka.ms/PillarMailboxSize)|[Increase or customize Exchange Online mailbox size](/exchange/troubleshoot/user-and-shared-mailboxes/increase-or-customize-mailbox-size)|
5151
|Deleted mailbox diagnostics|Check the state of recently deleted mailboxes.|[Run Tests: Deleted Mailbox](https://aka.ms/PillarDeletedMailBox)|[Delete or restore user mailboxes in Exchange Online](/exchange/recipients-in-exchange-online/delete-or-restore-mailboxes)|
52-
|Exchange Remote PowerShell throttling policy|Update the Exchange Remote PowerShell throttling policy for the tenant.|[Run Tests: PowerShell Throttling](https://aka.ms/PillarEXOPSThrottle)||
5352
|Email delivery troubleshooter|Check whether email messages are successfully delivered.| [Run Tests: Email Delivery](https://aka.ms/PillarEmailDelivery)|[Find and fix email delivery issues](/exchange/troubleshoot/email-delivery/email-delivery-issues)|
5453
|Outlook user connectivity diagnostics|Diagnose Outlook connectivity issues for users by running several checks on possible service-side settings (root causes) so that a tenant admin can quickly fix the issues without involving the users.|[Run Tests: Outlook User Connectivity](https://aka.ms/PillarOutlookConnectivity)|[Fix Outlook connectivity issue](/exchange/troubleshoot/outlook-issues/outlook-connection-issues)|
5554
|Non-delivery report (NDR) diagnostics|Provide additional information about NDRs that are received through email messages.|[Run Tests: Email NDR](https://aka.ms/PillarEmailNDR)|[Email non-delivery reports in Exchange Online](/exchange/mail-flow-best-practices/non-delivery-reports-in-exchange-online/non-delivery-reports-in-exchange-online)|

‎support/power-platform/power-automate/desktop-flows/troubleshoot-ui-flow-invalid-credentials-error-using-aad-account.md‎

Lines changed: 37 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,15 @@
11
---
22
title: Desktop flow invalid credentials error when using a Microsoft Entra account
3-
description: Resolves the InvalidConnectionCredentials or WindowsIdentityIncorrect error that occurs when you run a desktop flow using a Microsoft Entra account.
4-
ms.reviewer: guco，aartigoyle
3+
description: Learn how to resolve InvalidConnectionCredentials, WindowsIdentityIncorrect, and AADSTS50126 errors in Power Automate desktop flows caused by Microsoft Entra account issues.
4+
ms.reviewer: guco，aartigoyle, v-shaywood
55
ms.date: 08/20/2024
66
ms.custom: sap:Desktop flows\Cannot create desktop flow connection
77
---
88
# Desktop flow invalid credentials error when you use a Microsoft Entra account
99

10-
This article provides a resolution for the `InvalidConnectionCredentials` or `WindowsIdentityIncorrect` error code that occurs when you run a desktop flow using a [Microsoft Entra account](/entra/fundamentals/whatis#terminology).
10+
This article provides resolutions for the `InvalidConnectionCredentials` or `WindowsIdentityIncorrect` errors that might occur when you run a desktop flow using a [Microsoft Entra account](/entra/fundamentals/whatis#terminology). These errors typically indicate issues with device join status, account synchronization, or credential mismatches between the desktop flow connection and the target machine.
11+
12+
This article also covers the `AADSTS50126` error, which occurs when credential validation fails because of an invalid username or password, particularly in scenarios involving federated users.
1113

1214
_Applies to:_   Power Automate
1315
_Original KB number:_   4555623
@@ -34,15 +36,20 @@ When you run a desktop flow using a Microsoft Entra account, it fails with the `
3436
}
3537
```
3638

39+
You might also receive the following error message:
40+
41+
> AADSTS50126: Error validating credentials due to invalid username or password
42+
3743
## Cause
3844

3945
You might encounter the error when using a Microsoft Entra account for several reasons:
4046

41-
- The account credentials entered into the connection might not match those on the machine.
42-
- The device might not be [Microsoft Entra joined](/entra/identity/devices/concept-directory-join) or [Microsoft Entra hybrid joined](/entra/identity/devices/concept-hybrid-join) to support [Microsoft Entra authentication](/entra/identity/authentication/overview-authentication).
43-
- The Microsoft Entra account might not be synchronized to the machine.
47+
- You enter account credentials into the connection that don't match the credentials on the machine.
48+
- The device isn't [Microsoft Entra joined](/entra/identity/devices/concept-directory-join) or [Microsoft Entra hybrid joined](/entra/identity/devices/concept-hybrid-join) to support [Microsoft Entra authentication](/entra/identity/authentication/overview-authentication).
49+
- The Microsoft Entra account isn't synchronized to the machine.
50+
- The user account attempting to connect is a [federated user (ADFS)](/windows-server/identity/ad-fs/ad-fs-overview) while the tenant is configured to run on Microsoft Entra ID.
4451

45-
## Resolution
52+
## Solution
4653

4754
1. Ensure that the device is Microsoft Entra joined or domain-joined:
4855

@@ -54,31 +61,44 @@ You might encounter the error when using a Microsoft Entra account for several r
5461

5562
Make sure that one of the `DomainJoined` or `AzureAdJoined` values is `YES`.
5663

57-
If this isn't the case, a Microsoft Entra account can't be used unless the device is joined. For more information, see [How to join a device](/azure/active-directory/user-help/user-help-join-device-on-network#to-join-an-already-configured-windows-10-device).
64+
If this condition isn't true, you can't use a Microsoft Entra account unless the device is joined. For more information, see [How to join a device](/azure/active-directory/user-help/user-help-join-device-on-network#to-join-an-already-configured-windows-10-device).
5865

59-
2. Identify the Microsoft Entra account to use in the machine configuration:
66+
1. Identify the Microsoft Entra account to use in the machine configuration:
6067

6168
1. Open **Settings** and select **Accounts**.
6269

63-
2. Select **Access work or school**.
70+
1. Select **Access work or school**.
6471

65-
3. Make sure you see text like "Connected to <your_organization> Microsoft Entra ID." The account it's connected to can be used in the connection.
72+
1. Make sure you see text like "Connected to <your_organization> Microsoft Entra ID." The account it's connected to can be used in the connection.
6673

67-
3. Synchronize the Microsoft Entra account on the device:
74+
1. Synchronize the Microsoft Entra account on the device:
6875

6976
1. Select the **Info** button when selecting your Microsoft Entra connection on the **Access work or school** page.
7077

71-
2. This will open a page that describes your connection information and device synchronization status. Select the **Sync** button at the end of the page, and wait for this process to complete.
78+
1. This action opens a page that describes your connection information and device synchronization status. Select the **Sync** button at the end of the page, and wait for this process to complete.
79+
80+
1. Verify that the configured Microsoft Entra account can sign in to the device:
81+
82+
1. Try to sign in to the machine by using the Microsoft Entra account you identified in step 2.
83+
1. The device authentication must be successful to use the account in a connection.
84+
85+
1. Make sure the flow is configured properly with the right username and password. This information must match the account on your computer.
86+
87+
### AADSTS50126 error
88+
89+
To resolve an AADSTS50126 error, the preferred and most secure method is to configure [Certificate-Based Authentication (CBA)](/power-automate/desktop-flows/configure-certificate-based-auth).
90+
91+
If you can't configure CBA, federated users can use an alternative approach when administrators of the on-premises Identity Provider (IdP) configure [password hash synchronization](/entra/identity/hybrid/connect/whatis-phs) (PHS) to synchronize password hashes to the cloud. In this scenario, federated users can authenticate directly against Microsoft Entra ID (ESTS) by configuring a [Home Realm Discovery](/entra/identity/enterprise-apps/home-realm-discovery-policy) (HRD) policy that explicitly allows cloud password validation.
7292

73-
4. Verify that the configured Microsoft Entra account can sign in to the device:
93+
To enable this configuration, set the following HRD policy value:
7494

75-
1. Try to sign in to the machine using the Microsoft Entra account identified in step 2.
76-
2. The device login must be successful in order to be used in a connection.
95+
`"AllowCloudPasswordValidation": true`
7796

78-
5. Make sure the flow is configured properly with the right username and password. This must match the account on your computer.
97+
For detailed instructions, see [Enable direct ROPC authentication of federated users for legacy applications](/entra/identity/enterprise-apps/home-realm-discovery-policy#enable-direct-ropc-authentication-of-federated-users-for-legacy-applications).
7998

8099
## More information
81100

82101
- [Create desktop flow connections](/power-automate/desktop-flows/desktop-flow-connections)
83102
- [Invalid credentials error when running desktop flows in Power Automate for desktop](invalid-credentials-errors-running-desktop-flows.md)
84103
- ["Logon type has not been granted" error when running a desktop flow or creating a connection](logon-type-has-not-been-granted.md)
104+
- [What is federation with Microsoft Entra ID?](/entra/identity/hybrid/connect/whatis-fed)

‎support/sql/releases/download-and-install-latest-updates.md‎

Lines changed: 7 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -37,8 +37,8 @@ Each of the following links provides information for all of the applicable produ
3737

3838
|Version|Latest service pack|Latest GDR|Latest cumulative update|
3939
|---|---|---|---|
40-
|**SQL Server 2025**<br/><br/>- [Build information](#sql-server-2025)<br/>- [Installation](/sql/database-engine/install-windows/install-sql-server?view=sql-server-ver17&preserve-view=true)|None|None|None|
41-
|**SQL Server 2022**<br/><br/>- [Build information](#sql-server-2022)<br/>- [Installation](/sql/database-engine/install-windows/install-sql-server?view=sql-server-ver16&preserve-view=true)|None|[GDR](https://support.microsoft.com/help/5068407) <br/>(16.0.1160.1 - November 2025) |[CU22 for 2022](sqlserver-2022/cumulativeupdate22.md) <br/>(16.0.4225.2 - November 2025) <br/><br/>[CU21 + GDR](https://support.microsoft.com/help/5068406) <br/>(16.0.4222.2 - November 2025)|
40+
|**SQL Server 2025**<br/><br/>- [Build information](#sql-server-2025)<br/>- [Installation](/sql/database-engine/install-windows/install-sql-server?view=sql-server-ver17&preserve-view=true)|None|[GDR](https://support.microsoft.com/help/5073177) <br/>(17.0.1050.2 - January 2026)|None|
41+
|**SQL Server 2022**<br/><br/>- [Build information](#sql-server-2022)<br/>- [Installation](/sql/database-engine/install-windows/install-sql-server?view=sql-server-ver16&preserve-view=true)|None|[GDR](https://support.microsoft.com/help/5073031) <br/>(16.0.1165.1 - January 2026) |[CU22 for 2022](sqlserver-2022/cumulativeupdate22.md) <br/>(16.0.4225.2 - November 2025) <br/><br/>[CU22 + GDR](https://support.microsoft.com/help/5072936) <br/>(16.0.4230.2 - January 2026)|
4242
|**SQL Server 2019**<br/><br/>- [Build information](#sql-server-2019)<br/>- [Installation](/sql/database-engine/install-windows/install-sql-server?view=sql-server-ver15&preserve-view=true)|None|[GDR](https://support.microsoft.com/help/5068405) <br/>(15.0.2155.2 - November 2025)|[CU32 for 2019](sqlserver-2019/cumulativeupdate32.md) <br/>(15.0.4430.1 - February 2025)<br/><br/>[CU32 + GDR](https://support.microsoft.com/help/5068404) <br/>(15.0.4455.2 - November 2025)|
4343
|**SQL Server 2017**<br/><br/>- [Build information](#sql-server-2017)<br/>- [Installation](/sql/database-engine/install-windows/install-sql-server?view=sql-server-2017&preserve-view=true)|[Azure Connect pack](sqlserver-2017/azureconnect.md) <br/>(14.0.3490.10 - March 2025)|[GDR](https://support.microsoft.com/help/5068403) <br/>(14.0.2095.1 - November 2025)|[CU31 for 2017](sqlserver-2017/cumulativeupdate31.md) <br/>(14.0.3456.2 - September 2022)<br/><br/>[CU31 + GDR](https://support.microsoft.com/help/5068402) <br/>(14.0.3515.1 - November 2025)|
4444
|**SQL Server 2016**<br/><br/>- [Build information](#sql-server-2016)<br/>- [Installation](/sql/database-engine/install-windows/install-sql-server?view=sql-server-2016&preserve-view=true)|[Azure Connect pack](sqlserver-2016/servicepack3-azureconnect.md) <br/>(13.0.7000.253 - May 2022)<br/><br/>[SP3](sqlserver-2016/servicepack3.md) <br/>(13.0.6300.2 - September 2021)<br/><br/>[SP2](sqlserver-2016/servicepack2.md) <br/>(13.0.5026.0 - April 2018)<br/><br/>[SP1](sqlserver-2016/servicepack1.md) <br/>(13.0.4001.0 - November 2016)|[GDR for Azure Connect pack](https://support.microsoft.com/help/5068400) <br/>(13.0.7070.1 - November 2025)<br/><br/>[GDR for SP3](https://support.microsoft.com/help/5068401) <br/>(13.0.6475.1 - November 2025)<br/><br/>[GDR for SP2](https://support.microsoft.com/help/5014365) <br/>(13.0.5108.50 - June 2022)<br/><br/>[GDR for SP1](https://support.microsoft.com/help/4505219) <br/>(13.0.4259.0 - July 2019)<br/><br/>[GDR for RTM](https://support.microsoft.com/help/4058560) <br/>(13.0.1745.2 - January 2018)|[CU17 + GDR for SP2](https://support.microsoft.com/help/5014351) <br/>(13.0.5893.48 - June 2022)<br/><br/>[CU17 for 2016 SP2](sqlserver-2016/servicepack2-cumulativeupdate17.md) <br/>(13.0.5888.11 - March 2021)<br/><br/>[CU15 + GDR for SP1](https://support.microsoft.com/help/4505221) <br/>(13.0.4604.0 - July 2019)<br/><br/>[CU15 for SP1](sqlserver-2016/servicepack1-cumulativeupdate15.md) <br/>(13.0.4574.0 - May 2019)<br/><br/>[CU9 for RTM](sqlserver-2016/rtm-cumulativeupdate9.md) <br/>(13.0.2216.0 - November 2017)|
@@ -59,13 +59,16 @@ Each of the following links provides information for all of the applicable produ
5959

6060
| Build number or version | Service pack | Update | Knowledge Base number | Release date |
6161
|-------------------------|--------------|-----------|-------------------------------------------------------|--------------------|
62-
| 17.0.1000.7 | None | RTM/GA | NA | November 18, 2025 |
63-
62+
| 17.0.1050.2 | None | GDR | [KB5073177](https://support.microsoft.com/help/5073177) | January 13, 2026 |
63+
| 17.0.1000.7 | None | RTM/GA | NA |November 18, 2025 |
64+
6465

6566
### SQL Server 2022
6667

6768
| Build number or version | Service pack | Update | Knowledge Base number | Release date |
6869
|-------------------------|--------------|-----------|-------------------------------------------------------|--------------------|
70+
| 16.0.4230.2 | None | CU22 + GDR| [KB5072936](https://support.microsoft.com/help/5072936) | January 13, 2026 |
71+
| 16.0.1165.1 | None | GDR | [KB5073031](https://support.microsoft.com/help/5073031) | January 13, 2026 |
6972
| 16.0.4225.2 | None | CU22 | [KB5068450](sqlserver-2022/cumulativeupdate22.md) | November 13, 2025 |
7073
| 16.0.4222.2 | None | CU21 + GDR| [KB5068406](https://support.microsoft.com/help/5068406) | November 11, 2025 |
7174
| 16.0.1160.1 | None | GDR | [KB5068407](https://support.microsoft.com/help/5068407) | November 11, 2025 |

0 commit comments

Comments
 (0)