Additional Microsoft Entra services and features related to identity, access, and network security
Raise the case with the Microsoft Entra ID support team to validate the affected user’s cloud attributes and confirm that Azure DevOps is mapped to the current Entra object rather than a stale identity record.
Entra administrator checks
- Open the affected user in the Microsoft Entra admin center and record:
- Entra Object ID
- User principal name
- Email/mail
- Proxy addresses
- The profile attribute supplying the displayed location or geography
- Whether the user is synchronized from on-premises AD
- Confirm which system is authoritative for each stale field:
- For synchronized users, inspect the corresponding on-premises object and the Entra Connect synchronization result.
- Confirm that the current primary SMTP address is represented by uppercase
SMTP:and the retained legacy address by lowercasesmtp:. - Do not remove the legacy secondary address merely because Azure DevOps displays it.
proxyAddresseslegitimately stores multiple addresses associated with one mailbox, whilemailrepresents the user’s email address for various purposes.^1^
- Check for synchronization errors or duplicate-address conflicts. Duplicate SMTP proxy addresses can prevent the expected address from synchronizing; the Microsoft 365 admin center exposes affected accounts under Users > Active users > Users with errors.^2^
- If Entra already shows every current value correctly, allow up to one hour for Entra changes to become visible in Azure DevOps.^3^
Because the source-system and Azure DevOps configuration checks are already complete, do not reconnect the organization to its directory or alter permissions for this profile-only issue.
Azure DevOps identity-mapping validation
Have the Azure DevOps organization owner or Project Collection Administrator:
- Open Organization settings > Microsoft Entra ID and confirm that the organization is connected to the expected tenant.
- Open Organization settings > Users and record the affected user’s displayed sign-in address and status.
- Provide the Entra Object ID collected from the Entra user’s Overview page to support. Do not assume the Object ID is exposed in the Azure DevOps Users page.
- Ask support to compare that Object ID with the internal Azure DevOps identity mapping and determine whether Azure DevOps is linked to:
- The current Entra user object
- An older or duplicate identity
- A personal Microsoft account using the same address
- A disconnected identity requiring remapping
The documented Resolve action under Organization settings > Users is intended for users shown as disconnected after a directory connection; it should only be used if that status is actually displayed.^4^
Do not remove and re-add the user unless Microsoft support confirms a stale or duplicate mapping. That remediation resolved a similar duplicate-identity case, but that case also involved a login loop and therefore does not directly establish the appropriate fix for profile-only stale data.^5^
Conditional user-level workaround
If Microsoft Entra profile information (preview) is enabled for the affected user, Azure DevOps automatically populates the profile picture, display name, contact email, and geography from Entra. To temporarily restore the previous Azure DevOps-specific profile:
- Open User settings > Preview features.
- Set Microsoft Entra profile information to Off.
- Return to User settings > Profile.
- Verify or restore the contact email and region, then select Save.
Microsoft documents disabling this preview when Entra profile information is incorrect.^6^
This is a display workaround, not a correction to the underlying Entra attributes or identity mapping. If Entra authentication controls the profile email and the field is read-only, the value must be corrected by the Entra administrator.^7^
Information to include in the support case
Include:
- Azure DevOps organization name and connected Entra tenant
- Affected user’s Entra Object ID and current UPN
- Current
mail, primary SMTP, secondary SMTP, and location/geography values - Screenshots of the Entra profile and stale Azure DevOps profile
- Whether Microsoft Entra profile information preview is enabled
- Last source update and successful synchronization timestamps
- Confirmation that more than one hour has elapsed
- Confirmation that access and permissions are unaffected
- The earlier incident reference and its finding that the old address remains only as a secondary SMTP address
- A request to validate the Azure DevOps-to-Entra identity correlation and remove or remap a stale identity only if support confirms one exists
References
- user resource type
- Email addresses aren't synced to Microsoft Entra ID
- Access via Microsoft Entra FAQs
- Connect your organization to Microsoft Entra ID
- Stale Azure DevOps identity causing duplicate identities and login loop after domain federation - Microsoft Q&A
- Set user preferences
- Change your preferred email address for notifications