Answer: Fix the SCIM attribute mapping by changing the Source attribute for emails[type eq "work"].value to match what SSO sends — typically mail — then trigger a full provisioning sync via Restart provisioning. Status: Confirmed Entry: tool/claude-apps/admin-and-enterprise/entra-id-sso-scim-email-mismatch-fix Revision: 3 Digest: sha256:6a24476117492563 (changes whenever the content changes) Timeline: Created: 2026-11-13T02:59:02Z Last changed: 2026-11-18T12:01:54Z (Sync type: — → Full sync) Last verified: 2026-11-20T12:05:08Z Next check: 2026-11-21T12:05:08Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of SCIM attribute | emails[type eq "work"].value | [1] | 2026-11-20 Source attribute | mail | [1] | 2026-11-20 Sync type | Full sync | [1] | 2026-11-20 Action to trigger sync | Restart provisioning | [1] | 2026-11-20 Sources: [1] Anthropic. "Microsoft Entra ID SSO/SCIM email mismatch | Claude Help Center". https://support.claude.com/en/articles/13917829-microsoft-entra-id-sso-scim-email-mismatch Role: primary. Accessed: 2026-11-20T12:05:08Z Quote: "Find the row where the SCIM attribute is emails[type eq "work"].value." (Supports: SCIM attribute) Quote: "Change the Source attribute to match what SSO sends — typically mail." (Supports: Source attribute) Quote: "Full sync required — incremental won't work." (Supports: Sync type) Quote: "Click Restart provisioning ." (Supports: Action to trigger sync) Snapshot SHA-256: a557f5ee7287e2d7526c587459ff053b2dc6e3fe214e5ef9a0a10e1357faaeb0 (captured 2026-11-19T12:01:38Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-19T12:01:38Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T12:05:08Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:05:08Z Last attempt: 2026-11-20T12:05:08Z Notes and limitations: Extracted automatically from a single official source (section "Resolution"). Related: https://latestn.com/tool/claude-apps/admin-and-enterprise/existing-users-when-sso-enabled What happens to existing Claude Free, Pro, Team, Max, or Ultra users when SSO is enabled? https://latestn.com/tool/claude-apps/admin-and-enterprise/export-audit-logs How do I export audit logs for my Claude Enterprise organization? https://latestn.com/tool/claude-apps/admin-and-enterprise/export-org-data-steps How do I export my Claude organization's data? https://latestn.com/tool/claude-apps/admin-and-enterprise/enterprise-policy-options What enterprise policy options are available for Claude Desktop? https://latestn.com/tool/claude-apps/admin-and-enterprise/enterprise-seat-permissions Who can purchase seats or reassign seat types on a Claude Enterprise plan? https://latestn.com/tool/claude-apps/admin-and-enterprise/entra-id-sso-prerequisites What do I need before setting up Microsoft Entra ID SSO for Claude? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-18T12:01:54Z | changed | Sync type: — → Full sync | [1] 2026-11-18T12:01:54Z | changed | SCIM attribute: — → emails[type eq "work"].value | [1] 2026-11-18T12:01:54Z | changed | Sync type required: Full sync required → — | [1] 2026-11-18T12:01:54Z | changed | SCIM attribute to edit: emails[type eq "work"].value → — | [1] 2026-11-17T12:07:02Z | changed | Sync type required: Full sync required — incremental won't work. → Full sync required | [1] 2026-11-13T02:59:02Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/claude-apps/admin-and-enterprise/entra-id-sso-scim-email-mismatch-fix/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/claude-apps/admin-and-enterprise/entra-id-sso-scim-email-mismatch-fix POST: https://latestn.com/dispute/tool/claude-apps/admin-and-enterprise/entra-id-sso-scim-email-mismatch-fix with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/claude-apps/admin-and-enterprise/entra-id-sso-scim-email-mismatch-fix?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I fix a Microsoft Entra ID SSO/SCIM email mismatch in Claude? Revision 3, last verified 2026-11-20T12:05:08Z. https://latestn.com/tool/claude-apps/admin-and-enterprise/entra-id-sso-scim-email-mismatch-fix (accessed 2026-11-21T10:05:44Z). @misc{LatestN_tool_claude_apps_admin_and_enterprise_entra_id_sso_scim_email_mismatch_fix_r3, title = {How do I fix a Microsoft Entra ID SSO/SCIM email mismatch in Claude?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/claude-apps/admin-and-enterprise/entra-id-sso-scim-email-mismatch-fix}}, note = {Revision 3; digest sha256:6a24476117492563; last verified 2026-11-20T12:05:08Z; accessed 2026-11-21T10:05:44Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/claude-apps/admin-and-enterprise/entra-id-sso-scim-email-mismatch-fix