Answer: Align both SCIM and SAML email mappings to primaryEmail, then trigger a full re-sync of the provisioning cycle. An incremental sync will not update existing records after you change an attribute mapping, so you must temporarily suspend and re-enable provisioning (or remove and re-add affected people) to force a full sync. Status: Confirmed Entry: tool/claude-apps/troubleshooting/fix-google-workspace-sso-scim-email-mismatch Revision: 3 Digest: sha256:c601963b27f1c052 (changes whenever the content changes) Timeline: Created: 2026-11-13T02:59:00Z Last changed: 2026-11-19T12:01:34Z (SAML email attribute mapping: — → Basic Information → Primary email) Last verified: 2026-11-20T12:05:05Z Next check: 2026-11-21T12:05:05Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of SCIM email attribute mapping | primaryEmail | [1] | 2026-11-20 SAML Name ID setting | Basic Information → Primary email | [1] | 2026-11-20 SAML email attribute mapping | Basic Information → Primary email | [1] | 2026-11-20 Sync type required | Full sync required | [1] | 2026-11-20 Full sync method | Temporarily suspend provisioning, then re-enable it | [1] | 2026-11-20 Sources: [1] Anthropic. "Google Workspace SSO/SCIM email mismatch | Claude Help Center". https://support.claude.com/en/articles/13917817-google-workspace-sso-scim-email-mismatch Role: primary. Accessed: 2026-11-20T12:05:05Z Quote: "ensure the email attribute maps to primaryEmail" (Supports: SCIM email attribute mapping) Quote: "set Name ID to Basic Information → Primary email" (Supports: SAML Name ID setting) Quote: "ensure the email attribute is mapped to Basic Information → Primary email" (Supports: SAML email attribute mapping) Quote: "Critical — Full sync required: An incremental sync will not update existing records after you change an attribute mapping." (Supports: Sync type required) Quote: "Temporarily suspend provisioning, then re-enable it. This triggers a full sync of everyone assigned." (Supports: Full sync method) Snapshot SHA-256: acf3a7b623860c94d79d6d0ca407c97ba1351d58b007ded014b34e6afe7e0d5f (captured 2026-11-20T12:05:05Z) 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:34Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T12:05:05Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:05:05Z Last attempt: 2026-11-20T12:05:05Z Notes and limitations: Extracted automatically from a single official source (section "Resolution"). Related: https://latestn.com/tool/claude-apps/troubleshooting/fix-login-errors How do I fix a Claude login error? https://latestn.com/tool/claude-apps/troubleshooting/fix-ping-identity-email-mismatch How do I fix a Ping Identity SSO/SCIM email mismatch in Claude? https://latestn.com/tool/claude-apps/troubleshooting/foundry-support-options Where can I get support while using Claude through Microsoft Foundry? https://latestn.com/tool/claude-apps/troubleshooting/find-api-documentation Where can I find the Claude API documentation? https://latestn.com/tool/claude-apps/troubleshooting/firewall-vpn-blocking-api What should I check if my firewall or VPN is blocking the Claude API? https://latestn.com/tool/claude-apps/troubleshooting/fix-api-connection-error How do I fix an API connection error in Claude? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-19T12:01:34Z | changed | SAML email attribute mapping: — → Basic Information → Primary email | [1] 2026-11-19T12:01:34Z | changed | Full sync method: Temporarily suspend provisioning, then re-enable it. → Temporarily suspend provisioning, then re-enable it | [1] 2026-11-19T12:01:34Z | changed | SAML attribute mapping: Basic Information → Primary email → — | [1] 2026-11-18T12:01:49Z | changed | Sync type required: — → Full sync required | [1] 2026-11-18T12:01:49Z | changed | SAML attribute mapping: — → Basic Information → Primary email | [1] 2026-11-18T12:01:49Z | changed | SAML Name ID setting: — → Basic Information → Primary email | [1] 2026-11-18T12:01:49Z | changed | SCIM email attribute mapping: — → primaryEmail | [1] 2026-11-18T12:01:49Z | changed | Full sync method: Temporarily suspend provisioning, then re-enable it → Temporarily suspend provisioning, then re-enable it. | [1] 2026-11-18T12:01:49Z | changed | Sync requirement: Full sync required → — | [1] 2026-11-18T12:01:49Z | changed | SAML email attribute mapping: Basic Information → Primary email → — | [1] 2026-11-18T12:01:49Z | changed | SAML Name ID: Basic Information → Primary email → — | [1] 2026-11-18T12:01:49Z | changed | SCIM email mapping: primaryEmail → — | [1] 2026-11-13T02:59:00Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/claude-apps/troubleshooting/fix-google-workspace-sso-scim-email-mismatch/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/troubleshooting/fix-google-workspace-sso-scim-email-mismatch POST: https://latestn.com/dispute/tool/claude-apps/troubleshooting/fix-google-workspace-sso-scim-email-mismatch with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/claude-apps/troubleshooting/fix-google-workspace-sso-scim-email-mismatch?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I fix a Google Workspace SSO/SCIM email mismatch in Claude? Revision 3, last verified 2026-11-20T12:05:05Z. https://latestn.com/tool/claude-apps/troubleshooting/fix-google-workspace-sso-scim-email-mismatch (accessed 2026-11-21T10:05:04Z). @misc{LatestN_tool_claude_apps_troubleshooting_fix_google_workspace_sso_scim_email_mismatch_r3, title = {How do I fix a Google Workspace SSO/SCIM email mismatch in Claude?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/claude-apps/troubleshooting/fix-google-workspace-sso-scim-email-mismatch}}, note = {Revision 3; digest sha256:c601963b27f1c052; last verified 2026-11-20T12:05:05Z; accessed 2026-11-21T10:05:04Z} } 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/troubleshooting/fix-google-workspace-sso-scim-email-mismatch