Microsoft Copilot incident

Users may be unable to use Microsoft Copilot

Minor Resolved

Microsoft Copilot experienced a minor incident on May 29, 2026 affecting Microsoft Copilot and Microsoft 365 Copilot Chat Status, lasting 3h 5m. The incident has been resolved; the full update timeline is below.

Started
May 29, 2026, 02:30 PM UTC
Resolved
May 29, 2026, 05:35 PM UTC
Duration
3h 5m
Detected by Pingoru
May 29, 2026, 02:30 PM UTC

Affected components

Microsoft CopilotMicrosoft 365 Copilot Chat Status

Update timeline

  1. monitoring May 29, 2026, 03:50 PM UTC

    User impact: Users may be unable to use Microsoft Copilot. Current status: We're reviewing service telemetry to isolate the source of the issue. Next update by: Friday, May 29, 2026, at 5:30 PM UTC

  2. monitoring May 29, 2026, 05:01 PM UTC

    User impact: Users may be unable to use Microsoft Copilot. Current status: We've identified high utilization on the underlying infrastructure that the Copilot LLM APIs use and are applying mitigations. Additionally, at the Copilot service level, we're reviewing options to change routing paths, throttling rules and retry logic to allow the underlying infrastructure to recover. Next update by: Friday, May 29, 2026, at 6:30 PM UTC

  3. resolved May 29, 2026, 07:01 PM UTC

    User impact: Users were unable to use Microsoft Copilot. Final status: The underlying infrastructure that the Copilot LLM APIs use has recovered after the mitigation actions were applied. We monitored the environment for an extended period of time and have validated that service has been restored. Start time: Friday, May 29, 2026, at 2:30 PM UTC End time: Friday, May 29, 2026, at 5:35 PM UTC This is the final update for this event.