Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] REGRESSION: Microsoft 365 connector disappeared from Cowork connectors list after disconnect [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#48975•Fetched 2026-04-17 08:54:17
View on GitHub
Comments
0
Participants
1
Timeline
5
Reactions
0
Author
gh-vsgh-vs
Participants
gh-vsgh-vs
Timeline (top)
labeled ×5

The Microsoft 365 connector has completely disappeared from the Cowork connectors list after disconnecting it. The connector was previously available and connected. After disconnecting it (to attempt a reconnect and test write capabilities beyond read-only), the M365 connector no longer appears in the connectors list at all. There is no way to reconnect it.

Current connectors visible: GitHub Integration, Gmail, Google Drive. Microsoft 365 is missing entirely.

Root Cause

The Microsoft 365 connector has completely disappeared from the Cowork connectors list after disconnecting it. The connector was previously available and connected. After disconnecting it (to attempt a reconnect and test write capabilities beyond read-only), the M365 connector no longer appears in the connectors list at all. There is no way to reconnect it.

Current connectors visible: GitHub Integration, Gmail, Google Drive. Microsoft 365 is missing entirely.

RAW_BUFFERClick to expand / collapse

Description

The Microsoft 365 connector has completely disappeared from the Cowork connectors list after disconnecting it. The connector was previously available and connected. After disconnecting it (to attempt a reconnect and test write capabilities beyond read-only), the M365 connector no longer appears in the connectors list at all. There is no way to reconnect it.

Current connectors visible: GitHub Integration, Gmail, Google Drive. Microsoft 365 is missing entirely.

Environment

  • Product: Claude Desktop (Cowork mode)
  • Platform: macOS
  • Subscription: Max plan (with Microsoft 365 Basic account)
  • App version: Latest (April 2026)

Steps to Reproduce

  1. Have Microsoft 365 connector connected in Cowork
  2. Disconnect the M365 connector (e.g., to attempt reconnecting with different permissions)
  3. Go to Connectors list to reconnect
  4. Microsoft 365 connector is no longer listed as an available connector

Expected Behavior

Microsoft 365 should remain in the connectors list as an available connector that can be reconnected after disconnecting.

Actual Behavior

Microsoft 365 connector completely disappears from the connectors list after disconnecting. No way to add it back.

Notes

  • The connector was visible and functional before disconnecting
  • Gmail and Google Drive connectors remain visible and functional
  • User has an active Microsoft 365 Basic subscription
  • This effectively locks users out of M365 integration permanently after a disconnect

extent analysis

TL;DR

The Microsoft 365 connector's disappearance from the Cowork connectors list after disconnection may be resolved by checking the connector's configuration or subscription status.

Guidance

  • Verify that the Microsoft 365 subscription is active and valid, as an inactive subscription might cause the connector to disappear.
  • Check if there are any specific requirements or settings for reconnecting the Microsoft 365 connector, such as permissions or authentication tokens.
  • Attempt to restart the Claude Desktop application or check for any available updates, as this might refresh the connectors list.
  • If the issue persists, consider reaching out to support to investigate potential configuration or subscription-related issues.

Example

No code snippet is provided, as the issue seems to be related to configuration or subscription status rather than code.

Notes

The exact cause of the issue is unclear, and further investigation may be necessary to determine the root cause. The provided information suggests that the issue might be related to the subscription or configuration of the Microsoft 365 connector.

Recommendation

Apply workaround: Check the Microsoft 365 subscription status and connector configuration to ensure everything is set up correctly, as this is the most likely cause of the issue.

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…
#installation#tensor shape#autograd error#model save/load#optimization

Still need to ship something?

×6

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

Back to top recommendations

TRENDING