Old email and location still appear in Azure DevOps despite source updates. Entra ID team to investigate attribute sync and identity mapping.

S,Harivaran,CH-Nearshore 0 Reputation points
2026-11-18T14:19:47.09+00:00

Issue: User Manisha Prasad’s old email address and location are still displayed in Azure DevOps, despite her current details being correctly updated in the source systems.

Investigation findings:

Azure DevOps confirmed that profile information is sourced from Microsoft Entra ID.

No issue was identified with Azure DevOps configuration or permissions.

Previous investigation INC23683895 confirmed that the current ES email is primary, while the old AOA email remains as a secondary SMTP address under the Single User ID process.

No access or functional impact has been reported.

Required action: Raise with the Microsoft Entra ID Support Team to validate the identity attributes and Azure DevOps identity mapping, and investigate why the old email address and location are still being displayed.

Reference: INC23683895 (previous investigation).

Ticket was raised with nestle

Microsoft Security | Microsoft Entra | Other
0 comments No comments

1 answer

Sort by: Most helpful
  1. AI answer

    2026-11-18T14:21:14.3233333+00:00

    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

    1. 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
    2. 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 lowercase smtp:.
      • Do not remove the legacy secondary address merely because Azure DevOps displays it. proxyAddresses legitimately stores multiple addresses associated with one mailbox, while mail represents the user’s email address for various purposes.^1^
    3. 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^
    4. 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:

    1. Open Organization settings > Microsoft Entra ID and confirm that the organization is connected to the expected tenant.
    2. Open Organization settings > Users and record the affected user’s displayed sign-in address and status.
    3. 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.
    4. 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:

    1. Open User settings > Preview features.
    2. Set Microsoft Entra profile information to Off.
    3. Return to User settings > Profile.
    4. 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

    1. user resource type
    2. Email addresses aren't synced to Microsoft Entra ID
    3. Access via Microsoft Entra FAQs
    4. Connect your organization to Microsoft Entra ID
    5. Stale Azure DevOps identity causing duplicate identities and login loop after domain federation - Microsoft Q&A
    6. Set user preferences
    7. Change your preferred email address for notifications
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.