Live

Elevated errors affecting the Microsoft 365 connector

Partial outageOfficial update
0

Anthropic reports elevated errors and slow responses that affect the Microsoft 365 connector on claude.ai and Claude Cowork. Mail, calendar and search tools fail for most requests, and new connections to the connector may not complete. Anthropic identified an issue with an upstream provider and continues to work on it.

State

Identified

Started

Ongoing for

1 h 1 min

Worst impact

Partial outage

Timeline

2 updates
17:5218:0818:2318:3818:53
Partial outageUpdate postedTimes in UTC

Investigating

44 min 71%

Identified

18 min 29%

Updates

Times in UTC

As posted by Anthropic

Identified

We have identified an issue with an upstream provider affecting the Microsoft 365 connector. Mail, calendar and search tools are failing for most requests, and new connections to the connector may not complete. We are in contact with them and will provide an update as soon as possible.

Investigating

We are investigating elevated errors and slow responses affecting the Microsoft 365 connector. Requests to mail, SharePoint, Teams chat and calendar through the connector may fail, and new connections to the connector may not complete. We will provide an update as soon as possible.

Affected components

2
claude.aiClaude Cowork

Anthropic in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

47

Days with an incident

41

Median duration

42 min

This incident

1.5× the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

6 days
median 42 min
90 days agoToday

Other Anthropic incidents

All incidents

Follow Anthropic

Your coding agent knows when Anthropic is down, and tells you when a failure is theirs, not yours. You can also get Anthropic incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "anthropic" and tell me if Anthropic has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.live/feed.xml?providers=anthropic
Slack
/feed subscribe https://outages.live/feed.xml?providers=anthropic

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane