A widespread Microsoft 365 outage that began on Nov 12 has entered its second day, still affecting Outlook, Teams, Copilot, Exchange Online and several consumer services.
Microsoft reported that the first sign of trouble appeared at 11:17 a.m. ET on November 12 when Exchange Online began experiencing errors. A broader Microsoft 365 disruption was logged at 1:26 p.m. ET the same day, expanding to include Outlook, Teams, SharePoint and other cloud components.
The incident quickly spread beyond the United States, reaching users in Europe, Asia‑Pacific and Latin America. Both enterprise and government customers reported loss of access to mailboxes, calendar entries and file shares, confirming the global reach of the failure.

By the morning of November 13, Microsoft’s incident page still listed the same set of services as impaired, indicating that the outage had persisted for more than 24 hours despite ongoing remediation efforts.
Outlook on the web, Outlook desktop clients and Exchange Online were among the most severely affected. Users could not open their inboxes, send new messages or receive incoming mail, and many reported timeout errors when attempting to sync.
Microsoft extended the email timeout window to 48 hours in an effort to prevent delayed messages from being lost, but the extension does not restore real‑time delivery. The issue also touched Outlook.com, the consumer‑facing version of the mail service.
Microsoft Teams remained partially functional; chat and voice calls worked for most users, but calendar integration and meeting scheduling were disrupted. SharePoint Online, Planner and To Do showed intermittent availability, limiting document collaboration and task management.
The AI‑driven Microsoft 365 Copilot experienced outages as well, with some users unable to start new chats or retrieve contextual information. Defender XDR, Intune and other security‑related services were also listed among the impaired components.
Initial diagnostics pointed to an unusually high traffic volume, but deeper analysis revealed that a large number of backend servers became unexpectedly unavailable. Microsoft said the loss of capacity forced the remaining servers to operate under severe load.
The company has not disclosed any malicious activity, and it continues to investigate why the servers dropped out. According to statements posted on the Microsoft 365 admin center and on X, the incident is being treated as a service‑availability issue rather than a security breach.
Engineers first attempted to restart the affected servers, but the machines became unresponsive again once traffic returned. A targeted patch addressing an authentication and routing component was subsequently deployed, which appears to be stabilising traffic flow.
Microsoft also began redistributing connection load across its worldwide infrastructure, a step aimed at balancing demand while additional capacity is brought online. The firm has repeatedly posted status updates, noting early signs of recovery but no definitive ETA for full restoration.
No concrete timeline has been provided for when all services will return to normal operation. Microsoft advises administrators to monitor the incident page and to plan for possible delays in email delivery and file synchronization.
Customers are encouraged to use alternative communication channels, such as phone or third‑party messaging apps, until the core Microsoft 365 stack stabilises. The outage underscores the dependency of modern workplaces on cloud‑based productivity suites and may prompt organisations to review redundancy strategies.
TechTimes Perspective
TechTimes notes that the prolonged Microsoft 365 outage highlights the systemic risk of relying on a single cloud provider for essential communications. While Microsoft works to restore capacity, enterprises in Vietnam may experience delayed email flow and disrupted collaboration, potentially affecting project timelines. Companies are likely to reassess their business‑continuity plans, consider secondary mail routing or hybrid solutions, and keep a closer eye on Microsoft’s service‑health dashboards to mitigate future disruptions.

