Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix MCP claude.ai Microsoft 365 connector rejects personal Microsoft accounts (Hotmail/Outlook.com/Live) [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#53408•Fetched 2026-04-26 05:16:41
View on GitHub
Comments
1
Participants
2
Timeline
6
Reactions
0
Author
sandy9214sandy9214
Participants
dengluozhangdengluozhangsandy9214sandy9214
Timeline (top)
labeled ×5commented ×1

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 the error:

You can't sign in here with a personal account. Use your work or school account instead.

Error Message

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 the error:

Root Cause

Likely root cause

Fix Action

Fix / Workaround

Workarounds users currently need

RAW_BUFFERClick to expand / collapse

Summary

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 the error:

You can't sign in here with a personal account. Use your work or school account instead.

Reproduction

  1. In Claude Code, run /mcp.
  2. Select claude.ai Microsoft 365 → start auth flow.
  3. Browser opens https://login.microsoftonline.com/common/oauth2/v2.0/authorize?response_type=code&client_id=08....
  4. Enter a personal MSA email (e.g. [email protected]).
  5. Microsoft displays the rejection above before any consent screen is shown.

Expected

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. Many users' primary mailbox is @hotmail.com.

Likely root cause

Anthropic's OAuth app registration appears to use signInAudience = AzureADMyOrg or AzureADMultipleOrgs (work/school only) instead of AzureADandPersonalMicrosoftAccount. The /common endpoint accepts personal MSA only when the app's audience permits it.

Requested fix

Re-register (or update) the OAuth app with signInAudience = AzureADandPersonalMicrosoftAccount so both work/school and personal accounts can authenticate.

Reference: https://learn.microsoft.com/en-us/azure/active-directory/develop/supported-accounts-validation

Workarounds users currently need

  • Forward Hotmail → a working provider (e.g. Gmail) and ingest via claude.ai Gmail MCP.
  • Build a custom IMAP poller against imap-mail.outlook.com:993 using a Microsoft account app password.

Both are awkward and shouldn't be necessary for what is a primary consumer mail/storage product.

Environment

  • Claude Code (CLI), Opus 4.7
  • macOS 25.4.0 (Darwin)
  • Browser: Chrome
  • Affected MCP: claude.ai Microsoft 365 (claudeai-proxy at https://microsoft365.mcp.claude.com/mcp)
  • Affected account type: personal MSA

extent analysis

TL;DR

Update the OAuth app registration to use signInAudience = AzureADandPersonalMicrosoftAccount to allow personal Microsoft accounts to authenticate.

Guidance

  • Verify the current signInAudience setting in the OAuth app registration to confirm it is set to AzureADMyOrg or AzureADMultipleOrgs.
  • Update the OAuth app registration to use signInAudience = AzureADandPersonalMicrosoftAccount as described in the Microsoft documentation: https://learn.microsoft.com/en-us/azure/active-directory/develop/supported-accounts-validation.
  • Test the updated OAuth flow with a personal Microsoft account to ensure authentication is successful.
  • Consider implementing a temporary workaround, such as forwarding Hotmail emails to a working provider or building a custom IMAP poller, for users who are currently affected.

Example

No code snippet is provided as the issue is related to OAuth app registration configuration.

Notes

The fix relies on updating the OAuth app registration, which may require coordination with the Anthropic team responsible for managing the app registration.

Recommendation

Apply the workaround of updating the OAuth app registration to signInAudience = AzureADandPersonalMicrosoftAccount, as this is the most direct solution to allow personal Microsoft accounts to authenticate.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#container setup#orchestration issue#cache issue#memory leak#API versioning

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix MCP claude.ai Microsoft 365 connector rejects personal Microsoft accounts (Hotmail/Outlook.com/Live) [1 comments, 2 participants]