Microsoft Says 365 Outage Is Resolved; Check Delayed Outlook Mail

Microsoft said at 06:09 UTC November 14 (11:09 p.m. Mountain time November 13) that it had restored service to the remaining customers and regions affected by its Microsoft 365 outage. For organizations that rely on Outlook mail, Teams scheduling and Copilot access to work data, the immediate task is to check whether time-sensitive work disrupted by the outage was completed.

In Microsoft incident updates published by the University of Pennsylvania, both the broader Microsoft 365 incident, MO1550821, and the Exchange Online incident, EX1550543, are marked service restored. The later public statement confirms that Microsoft’s restoration efforts had reached the remaining affected customers and regions.

Which functions were affected

Microsoft’s record says the disruption, identified November 12, affected Outlook mailbox access and mail delivery. Teams calendars and scheduling, along with Copilot responses or access to work data, were also affected. Most core Teams calling, meetings and messaging were not affected, and direct access to files in SharePoint remained available. That distinction helps organizations identify which messages, appointments or work requests need attention.

Microsoft’s preliminary explanation points to an issue introduced during an earlier network-capacity upgrade that surfaced after a more recent network change. The company described the problem as technical rather than cyber- or AI-agent-related and said a fuller post-incident report would follow.

Check mail that could not wait

Restored service does not reverse an expired message. Delivery provider SparkPost said its deliveries to Microsoft mailboxes returned to normal November 13 and that it retried queued messages. Some messages with short expiration settings may instead have expired and bounced, it said. That notice concerns SparkPost’s deliveries; it does not establish an outage-wide bounce rate.

Administrators can review bounce notices and confirm delivery of time-sensitive mail. Microsoft’s service-health guide directs them to Health → Service health → Issue history for resolved incidents, with a Report an issue option if a problem persists without a listing. Those checks can establish whether particular messages still need follow-up after the platform restoration.