Microsoft traced the Microsoft 365 outage to a problem introduced during an earlier network capacity upgrade and exposed by a subsequent network change. On November 13, the company said it had addressed the underlying issue and was restoring services in stages. Microsoft incident bulletin MO1550821, reproduced by the University of Pennsylvania

The incident began on November 12 at 18:26 UTC. In its November 13 update at 22:00 UTC, Microsoft was still monitoring service stability and the backlog of email messages. The company described the outage as a technical issue unrelated to malicious cyber activity or AI agents.

Why a mail outage reached calendars and other services

Exchange Online provides mailboxes, calendars and other work data. Some users struggled to access Outlook, and message delivery could be delayed. In Teams, disruption centered on Exchange-dependent functions such as scheduling and invitations. Microsoft said most core calling, meeting and messaging functions remained available.

The same dependency showed up in integrations. Microsoft Graph requests for email, calendar data or contacts could time out. Some Copilot features struggled to access work data. For teams operating these integrations, successful sign-in tells them little about whether a request to another part of the platform will succeed.

What still had to happen before closure

Microsoft said it restored services in stages and checked stability before moving on. Outlook access can return while queued messages are still being delivered. Those are separate signals for teams trying to establish whether invitations, notifications and email-driven processes are back to normal.

Microsoft said it would publish a technical report after completing its review. The bulletin connects the outage to two network changes. The report will be needed to explain how the problem escaped earlier checks and what Microsoft plans to change to prevent a recurrence.