Low severityauthentication
Power BI Error:
AADSTS50043
What does this error mean?
Azure AD/Entra ID cannot generate a Pairwise Subject Identifier (PPID) because the user account is linked to multiple salt values.
Common causes
- 1The user object in Microsoft Entra ID (formerly Azure AD) has multiple salt values stored, preventing a deterministic PPID from being generated
- 2Directory synchronization issues (e.g. Entra Connect) caused duplicate or conflicting immutableId/SecurityIdentifier values on the user
- 3User was migrated between tenants or hard-matched after a soft-match, leaving residual identifier metadata
- 4Application is configured to use Pairwise Subject Identifiers (PPID) but the user object is in an inconsistent state
- 5Stale or corrupted ProxyAddresses / alternateSecurityIds on the affected user account
How to fix it
- 1Identify the affected user — this error is user-specific, so confirm which account fails to sign in and capture the correlation ID from the sign-in logs in the Entra admin center
- 2Have a Global Administrator inspect the user object in Microsoft Entra ID for duplicate or conflicting identifier attributes (immutableId, alternateSecurityIds, onPremisesSecurityIdentifier)
- 3If the user is synced via Microsoft Entra Connect, check the sync engine for duplicate-attribute or source-anchor conflicts and resolve them at the source (on-premises AD)
- 4As a workaround, delete and recreate the user object (or reset the source anchor) so a single, clean salt is generated — note this may impact licensing and group memberships
- 5If the issue persists after directory cleanup, open a support ticket with Microsoft referencing AADSTS50043 and the sign-in correlation ID, since pairwise identifier metadata can only be reset server-side