claude-code - 💡(How to fix) Fix Microsoft 365 MCP connector shows 'Needs Auth' in VS Code despite being connected in desktop app [1 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#55021Fetched 2026-05-01 05:48:17
View on GitHub
Comments
0
Participants
1
Timeline
4
Reactions
0
Participants
Timeline (top)
labeled ×4

The claude.ai Microsoft 365 MCP connector shows Needs Auth in the VS Code extension's MCP servers panel, even though it shows as Connected in both the Claude desktop app and at https://claude.ai/customize/connectors.

Other claude.ai connectors (HubSpot, Marketing Ads MCP) show as Connected in VS Code without issue — this appears specific to Microsoft 365.

Root Cause

The claude.ai Microsoft 365 MCP connector shows Needs Auth in the VS Code extension's MCP servers panel, even though it shows as Connected in both the Claude desktop app and at https://claude.ai/customize/connectors.

Other claude.ai connectors (HubSpot, Marketing Ads MCP) show as Connected in VS Code without issue — this appears specific to Microsoft 365.

Fix Action

Fix / Workaround

Attempted workarounds (none resolved it)

RAW_BUFFERClick to expand / collapse

Description

The claude.ai Microsoft 365 MCP connector shows Needs Auth in the VS Code extension's MCP servers panel, even though it shows as Connected in both the Claude desktop app and at https://claude.ai/customize/connectors.

Other claude.ai connectors (HubSpot, Marketing Ads MCP) show as Connected in VS Code without issue — this appears specific to Microsoft 365.

Steps to reproduce

  1. Connect Microsoft 365 connector at https://claude.ai/customize/connectors (OAuth via Microsoft login)
  2. Open VS Code with the Claude Code extension
  3. Open the MCP servers panel — Microsoft 365 shows "Needs Auth"

Attempted workarounds (none resolved it)

  • Developer: Reload Window in VS Code
  • Sign out and sign back into Claude Code in VS Code
  • Disconnect and reconnect Microsoft 365 at claude.ai/customize/connectors while VS Code was open (VS Code showed "Authenticating..." then reverted to "Needs Auth")

Expected behavior

Microsoft 365 should show as Connected in VS Code, consistent with the desktop app and other connectors.

Environment

  • OS: Windows 11 Pro
  • Claude Code: VS Code extension
  • Other connectors working in VS Code: HubSpot, Marketing Ads MCP (custom)
  • Microsoft 365 auth flow uses redirect_uri=https://claude.ai/api/mcp/auth_callback (server-side callback, not localhost)

extent analysis

TL;DR

The Microsoft 365 connector in the VS Code extension may require a specific authentication token or callback configuration to show as Connected.

Guidance

  • Verify that the redirect_uri parameter in the Microsoft 365 auth flow is correctly configured to match the expected callback URL in the VS Code extension.
  • Check if the authentication token obtained during the OAuth flow is being properly stored and passed to the VS Code extension.
  • Investigate potential differences in authentication handling between the Claude desktop app and the VS Code extension.
  • Review the documentation for the Claude Code extension and Microsoft 365 connector to ensure that all required configuration steps have been completed.

Example

No code snippet is provided due to lack of specific implementation details.

Notes

The issue may be related to the specific authentication flow used by the Microsoft 365 connector, which could be different from other connectors. Further investigation is needed to determine the root cause.

Recommendation

Apply workaround: Investigate and adjust the authentication token storage and callback configuration to ensure compatibility with the VS Code extension, as the issue appears to be specific to this environment.

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…

FAQ

Expected behavior

Microsoft 365 should show as Connected in VS Code, consistent with the desktop app and other connectors.

Still need to ship something?

×6

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

Back to top recommendations

TRENDING