GitHub issue #53408 in anthropics/claude-code, opened 2026-04-26 by sandy9214, records a report that the bundled claude.ai Microsoft 365 MCP connector cannot authenticate personal Microsoft accounts (@hotmail.com, @outlook.com, @live.com): the OAuth flow halts at the Microsoft sign-in page with "You can't sign in here with a personal account. Use your work or school account instead."; the report suggests Anthropic's OAuth app registration uses a work/school-only signInAudience instead of AzureADandPersonalMicrosoftAccount; the report was filed against Claude Code CLI (Opus 4.7) on macOS 25.4.0.
Verbatim Excerpts from Cited Records
“The bundled `claude.ai Microsoft 365` MCP connector cannot authenticate personal Microsoft accounts (`@hotmail.com`, `@outlook.com`, `@live.com`).”
·
anthropics/claude-code (issue 53408 opening body, Summary section)
·
2026-04-26T01:10:36Z
·GitHub Issue ↗
“You can't sign in here with a personal account. Use your work or school account instead.”
·
anthropics/claude-code (issue 53408 opening body, Summary section)
·
2026-04-26T01:10:36Z
·GitHub Issue ↗
“Personal Microsoft accounts (Outlook.com / Hotmail / Live) should be accepted, since the connector targets Outlook mail and OneDrive — both of which are first-class personal-account services.”
·
anthropics/claude-code (issue 53408 opening body, Expected section)
·
2026-04-26T01:10:36Z
·GitHub Issue ↗
“Anthropic's OAuth app registration appears to use `signInAudience = AzureADMyOrg` or `AzureADMultipleOrgs` (work/school only) instead of `AzureADandPersonalMicrosoftAccount`.”
·
anthropics/claude-code (issue 53408 opening body, Likely root cause section)
·
2026-04-26T01:10:36Z
·GitHub Issue ↗
Counter-record: Issue open as of the fetch; 18 comments were read. Users confirmed the same rejection through 2026-11-18, most recently wyattm14, who shared third-party workarounds; AI-OWEN (2026-07-15) retested after a Desktop update listing MS365-connector auth fixes that did not touch this issue, and VernonLKury (2026-08-27) and Lux87 (2026-10-16) confirmed it persists. lumman-pro (2026-09-27) shared a custom connector workaround. Shorteeeee (2026-08-28) speculated the restriction may be deliberate. No maintainer response or fix appears in the surveyed thread, and no retraction of the original report appears. The claim documents only the original report, not a verified current state.
Falsification probe: If GitHub issue #53408 is deleted without archive, if the author edits the opening body so the quoted sentences no longer match verbatim, or if the author posts a retraction of the report, this claim drops to Withdrawn.
Audit verification: Verified 100% continuous verbatim substring against official GitHub REST API by
scripts/verify_claim_verbatim.py.