Tech · Microsoft 365 outageContinuing story · report 4 of 5
Microsoft protects delayed mail for 48 hours as outage recovery remains incomplete
Visa processing and hospital communications show the stakes as Microsoft protects delayed messages for 48 hours but reports unstable service and incomplete capacity recovery.
Written 6 min read · 219 sources
What changed since our last report
2 hours later
Then
Microsoft outage delays medical scans and a final job interview as recovery remains partialWhat we said was still open
The initiating cause, audited totals of affected users and organizations, aggregate losses and full connector-restoration times remain unresolved.
Still openThe initiating cause, audited affected-user and organization totals, aggregate losses and full connector-restoration times remain unestablished. The new notice adds protection for delayed mail, not answers to those outstanding questions.
Whether restored capacity stays responsive as traffic returns—and whether Microsoft’s promised incident report explains why repeated recovery attempts failed.
Still openMicrosoft still reports variable service health and incomplete capacity recovery, so sustained responsiveness under returning traffic is not established. Its full post-incident report, including root cause and protective measures, is promised after mitigation, without a publication date.199
Now
Visa processing and hospital communications show the stakes as Microsoft protects delayed messages for 48 hours but reports unstable service and incomplete capacity recovery.
For someone waiting on a visa, a working inbox is only the beginning of recovery. Immigration New Zealand announced that all visa application processing was paused until further notice during the worldwide Microsoft outage, and customers could not apply through its enhanced online platform. No subsequent resumption is established in the available reporting. Behind the service-status notices are decisions people cannot get and work agencies cannot finish.23214
Microsoft has now added a specific protection for the messages caught in that disruption: an extended, 48-hour email timeout. Its public incident notice updated at 10:01 UTC on November 13 says several workloads are improving, but service health remains variable and capacity has not fully returned to normal. The classification is still “Service degradation,” not restored.199
The distinction matters. Forty-eight hours is two days, but it is neither a delivery promise nor a forecast of how long the outage will last. Microsoft says the extension is intended to preserve delayed messages while it prioritizes queues and backlogs. It has not established how many messages are waiting, how much mail may have been lost or when the backlog will be cleared.199
In our November 13 report, aired at 09:26 UTC, we described continuing disruption alongside Microsoft’s early gains from traffic optimization. We also reported individual consequences: delayed or cancelled medical scans, interrupted occupational therapy, blocked invoice processing and a missed final job interview. Those were accounts of particular work that could not proceed—not an audited measure of financial loss or evidence of a medical injury caused by the outage.
The 10:01 notice advances that recovery account with an explicit message-preservation measure and a fresh acknowledgement that capacity remains below baseline. It does not replace incomplete recovery with an all-clear.199
Recovery must survive returning traffic
The disruption began on Thursday, November 12, and continued into Friday across time zones. Reports differ on its precise onset, and descriptions of five, nine, twelve or fourteen hours were snapshots during an ongoing incident, not competing measurements of its final duration. The evidence supports one continuing outage, not a separately established second failure.33221728
Microsoft’s explanation of the capacity problem is more specific than “too many people logged on.” Servers unexpectedly became unavailable, shifting their work onto the infrastructure still running. The company distinguished that reduced usable capacity from a sudden surge in customer traffic. Earlier restoration attempts brought some servers back only for them to become unresponsive again when requests returned.1423
Engineers have paused deployments, restarted servers, rerouted or restricted traffic, rolled back changes and tested an alternative way to check server health. Selected regions improved, but restarting equipment is useful only if it stays responsive under load. Recovery also has to accommodate the accumulated work arriving behind ordinary traffic.212217
Publication times can obscure that sequence. Friday-morning reports continued to carry Microsoft’s statement that fixes were not working as expected, while other accounts described positive results. The failed-remediation account was already circulating before the improvement update; its appearance in a newer article does not establish another failed intervention afterward. Microsoft’s 10:01 assessment explicitly accommodates both realities: incremental improvement and continuing instability.20620316199
The initiating cause remains unconfirmed. Server configuration and a faulty software update have been suggested; Australian Home Affairs Minister Tony Burke relayed the update explanation as Microsoft’s apparent assessment, not a verified technical finding. Microsoft says it has no evidence of malicious activity associated with the incident. That is its current security assessment, not a completed forensic investigation excluding every possible attack.2214199
What works depends on the dependency
Microsoft’s notice contains 20 product-and-service entries. That does not mean 20 applications are wholly unavailable. Many failures involve features that interact with Exchange Online, its cloud email system, while functions without that dependency remain usable. This helps explain why colleagues can experience the same incident very differently.199
Outlook users may be unable to open mailboxes, send or receive messages, or read message bodies and attachments—even when a sender and subject line appear. Problems can affect web and desktop access, mobile synchronization and software connections to Exchange. Some Microsoft 365 administrative pages and recently used file views may fail, without establishing that locally stored documents or offline editing have stopped working.16199
Teams needs particular care. Microsoft says most core functions—including joining calls and meetings, group chats and channel messages—are not affected. Calendar scheduling, invitations and meeting edits can fail, as can the creation of Live or Virtual events and some contact, chat-history and Copilot operations. Standard channels remain functional. Direct access to SharePoint Online files also remains available, although external sharing and email-dependent features can be impaired.199
The wider effects reach education features such as Assignments and Reading Progress; Copilot’s access to work email, calendars and files; Intune enrollment and compliance checks; and Planner and To Do operations. Microsoft Graph requests involving mail, calendars and contacts can time out, interrupting connected applications and notifications.199
Security and compliance teams face their own constraints. Defender pages may not load, while policy evaluation relying on Purview protection signals can be delayed or fail. Purview problems include authorization, labeling, data-loss prevention, audit and investigation searches, exports and access to protected content. Fabric and Power BI can encounter failures involving sensitivity-labeled material. These are consequential feature impairments, not evidence that attackers have breached customers.199
Workarounds are application-specific. Web access may help some Power Apps and Field Service users; people already signed in may potentially avoid disruption by staying signed in and not clearing application data or reinstalling. Removing a sensitivity label from affected reporting material is an option only where an organization’s protection rules permit it—not a general instruction to weaken security.199
The work waiting behind the inbox
The international footprint is clear; the affected population is not. Downdetector reports came from 74 countries and regions across the Americas and parts of Europe, Asia and Africa. Peak US reports exceeded 130,000, while other accounts described worldwide Outlook snapshots approaching 140,000. Different products, places and reporting windows cannot be added into a reliable total of affected people.151432
Australia activated its priority-restoration agreement with Microsoft after intelligence and federal-police impacts. Agency leaders Mike Burgess and Krissy Barrett confirmed their organizations were affected; that does not establish that intelligence or policing operations shut down entirely. Most Norwegian ministries supported by the government’s digital-services organization were affected, with the Justice Ministry identified as an exception.143028
Healthcare accounts show why both disruption and reassurance need precise boundaries. The University of Iowa hospital network lost email and voicemail access and directed patients to its online portal. Unity Health Toronto declared a Code Grey after email failed, while saying patient and resident care remained unaffected and its hospitals were safe and open. Neither account establishes a universal healthcare failure—or a subsequent restoration of those communications.15124
IndiGo and CemAir reported messaging difficulties without reporting flight disruption in those announcements. Connected AI functions were affected too: OpenAI and Anthropic reported Microsoft connector problems, and full connector restoration is not established. Workhorse Group postponed its quarterly results announcement to November 16 because of outage-related business disruption. A communications platform can remain partly usable while the work depending on it cannot proceed.1536
At the 10:01 checkpoint, Microsoft promised its next update by 11:00 UTC on November 13. That is a deadline for information, not restoration. The meaningful tests remain sustained capacity and backlog clearance: an inbox that opens is not proof that the messages—and the public-service work waiting behind them—have caught up.199
Timeline
Day 4 · 5 reports
We aired · Update 4You are here
Microsoft protects delayed mail for 48 hours as outage recovery remains incompleteMicrosoft's stated end of active customer impact.
Microsoft says service is restored to the remaining affected customers and regions and keeps monitoring delayed mail.
Preliminary report published; Lamanna apologises on X.
Sources163
Every source, by outlet
219 sources from 163 outlets· Most cited first
Google News Singapore (SG:en)channelnewsasia.com5
- First reported
- Some Singapore government systems affected by Microsoft outage: GovTech - CNA
- Microsoft 365, Outlook down for thousands of users - CNA
- Microsoft outage drags on for hours, disrupting Outlook, Teams for thousands, including Singapore users - CNA
- Microsoft Outlook outage: Disruptions hit workers worldwide amid setback in recovery efforts - CNA
- Australia's spy agency, federal police hit by Microsoft outage - CNA
Workhorse Group, Inc.workhorse.com5
BBCbbc.com4
- First reported
- Microsoft outage: Outlook and Teams impacted globally as company struggles to restore service - BBC News
- Outlook: falha na Microsoft deixa email fora do ar email e afeta Teams, Microsoft 365 e outras plataformas; o que se sabe
- Una falla en Microsoft deja fuera de servicio el correo electrónico de Outlook y otras plataformas
- Microsoft outage sees Teams, Outlook and Copilot suffer 'connectivity issues'
Google News Pakistan (PK:en)theguardian.com4
- First reported
- Microsoft ‘restarting’ as outage impacts global users, with Outlook and Teams affected | Microsoft | The Guardian
- A global Microsoft 365 outage has hit thousands – what happened and when will it be fixed? - The Guardian
- Microsoft outage live: Microsoft scrambling for new ways to fix global outage after initial attempts fail to restore Outlook services | Microsoft | The Guardian
- ‘Looks like we’ll have to talk to people’: Australia sent back to time before email with major Microsoft outage | Microsoft | The Guardian
Google News السعودية (SA:ar)cnn.com4
- First reported
- Global Microsoft outage disrupts Outlook, Teams and other services
- Global Microsoft outage leaves millions without access to Outlook email, Teams and other tools - CNN
- "عطل" يصيب مايكروسوفت 365 وأوتلوك.. والشركة تعلق - CNN Arabic
- Massive Microsoft outage disrupts businesses, schools and governments around the world | CNN Business
franceinfofranceinfo.fr3
- First reported
- DIRECT. Crise sociale : la réunion entre les syndicats de fonctionnaires et le Premier ministre a débuté
- Une panne mondiale touche la messagerie Outlook de Microsoft, "aucun signe d'action malveillante ou de cyberattaque" n'a été trouvé à ce stade
- DIRECT. Panne mondiale de Microsoft : "Des résultats positifs en matière de stabilité du service" constatés par le géant américain
As aired
- Microsoft has extended its email timeout to forty-eight hours to protect delayed messages. Hospitals, government agencies and businesses are waiting on recovery, while Microsoft's available capacity remains below normal.
- On November thirteenth, we reported continuing disruption and Microsoft's early gains from traffic optimization. Its latest assessment describes further improvement alongside unstable service. Can Microsoft restore enough lasting capacity to clear the mail and restart the work waiting behind it?
- Reports of problems came from seventy-four countries and regions, across the Americas and parts of Europe, Asia and Africa. The disruption began Thursday and continued into Friday, reaching public services as well as workplace inboxes.
- The international reach is clear. The number of people affected hasn't been counted. Submitted outage reports measure complaints, and their totals depend on the product, place and time being measured.
- Peak reports exceeded one hundred thirty thousand in the United States. A worldwide Outlook snapshot approached one hundred forty thousand. Smaller national snapshots also showed problems. These figures cover different windows and scopes, so adding them would exaggerate what they tell us.
- Microsoft says servers unexpectedly became unavailable, pushing their work onto the infrastructure still running. The company distinguished that loss of usable capacity from a sudden surge in customer traffic. Some servers returned to service, then stopped responding again when requests came back.
- Restarting a server only helps if it keeps responding when work returns. Engineers have been managing traffic while bringing capacity back. At the same time, they have to process the email that accumulated during the disruption.
- Recovery measures have included pausing deployments, restarting servers, rolling back changes and testing another way to check server health. Microsoft also rerouted and restricted traffic. Selected regions improved, including an earlier improvement in North American Teams issues, while other customers continued having problems.
- Microsoft's latest assessment puts those two experiences together. Several services are improving, but health still varies and capacity hasn't fully recovered. Earlier failed repair attempts predated Friday's progress, so continuing disruption can coexist with genuine improvement.
- The extended timeout gives delayed email a two-day preservation window while Microsoft prioritizes queues and backlogs. It doesn't promise every message will arrive within two days, or predict an outage lasting that long. Microsoft hasn't given a time for clearing the backlog.
- Subscribe to this channel as we follow Microsoft's recovery and the public services waiting for it.
- Microsoft still hasn't confirmed what first made the servers fail. Server configuration and a faulty update have been suggested as possibilities. Australian Home Affairs Minister Tony Burke relayed the update explanation as Microsoft's apparent assessment.
- Mike Burgess, Australia's intelligence chief, and federal police commissioner Krissy Barrett confirmed their organizations were affected. Australia activated its priority-restoration agreement with Microsoft. Those confirmations concern affected systems and communications within agencies that also carry out many other operations.
- Microsoft says it has found no evidence of malicious activity associated with the incident. That's its current security assessment while the cause remains under investigation. The company plans to publish its root-cause findings and further protective measures after mitigation is complete.
- Microsoft's notice lists twenty product-and-service entries. Across those services, many failures involve features that interact with Exchange Online, its cloud email system. Other functions remain available, which helps explain why colleagues can have very different experiences of the same incident.
- Outlook users may struggle to open mailboxes, send or receive messages, or read message bodies and attachments. A sender and subject line can appear while the contents won't open. Problems can affect web and desktop Outlook, mobile synchronization and software connections to Exchange.
- Some Microsoft 365 administrative pages may fail to load. Recently used file views can break, while administrators can lose access to cloud update, policy and inventory controls. Locally stored documents and offline editing can remain usable.
- Education features that may be affected include Assignments, Reading Progress and Speaker Progress. Copilot Chat may fail to load or answer. Other Copilot experiences can lose access to work email, calendars and files needed to complete a request.
- Most core Teams functions, including joining calls and meetings, group chats and channel messages, remain unaffected. Calendar scheduling, invitations and meeting edits can fail. Creating Live or Virtual events can also fail, alongside some contact, chat-history and Copilot operations.
- Standard Teams channels remain functional. Direct access to files in SharePoint Online also remains available, although external sharing and email-dependent features can be impaired. Microsoft Graph, the software connection used by other applications, can time out on mail, calendars and contacts, affecting connected Teams operations and notifications.
- Device enrollment, check-ins and compliance checks through Intune may be intermittent. Planner has plan and task reliability problems, and To Do may fail to load or finish operations. Power Apps and Field Service mobile users may encounter sign-in failures.
- Web access may offer an alternative for Power Apps and Field Service. People already signed in may avoid disruption by staying signed in, keeping application data and avoiding reinstallation during the incident. Those options depend on the application and the user's situation.
- Security teams face problems too. Defender for Office 365 can experience delays or failures when evaluating policies using Purview protection signals. Defender XDR pages may not load. Features governing software identities can also fail when they depend on sensitivity labels.
- Purview problems reach authorization, automatic labeling and data-loss prevention. Protected content may not open. Audit searches, investigation searches and exports, classification and on-demand scans may be impaired. Communication compliance, protection policies and role-based access controls are also affected.
- Fabric and Power BI can have trouble with sensitivity-labeled files and exports. That includes PDF and PowerPoint exports, updates to labeled material and opening labeled Power BI Desktop files. Removing a label is an option only where an organization's protection rules allow it.
- Universal Print may fail to submit jobs or perform administrative operations. Windows 365 connections can be impaired for customers using Purview Customer Key protection for their tenants and Cloud PCs. These feature failures can disrupt work without showing that attackers have breached a customer.
- Immigration New Zealand announced that all visa application processing was paused until further notice. Customers also couldn't apply through its enhanced online platform. Its foreign ministry experienced trouble receiving email at home and at overseas missions, while some offices and businesses reverted to manual methods.
- Most Norwegian ministries supported by the government's digital-services organization were affected, with the Justice Ministry identified as an exception. US House users were affected too. Officials in Japan also described government-system impacts. In Australia, reported disruption extended to schools, courts and businesses.
- The University of Iowa hospital network lost email and voicemail access and directed patients to its online portal. Unity Health Toronto declared a Code Grey alert after email failed, while saying patient and resident care was unaffected and its hospitals remained safe and open.
- Earlier personal accounts showed other clinical workflows breaking down. Maria Derosa said scans after a car accident were delayed or cancelled because she and the clinic couldn't access referrals. Occupational therapist Lauren Van Ingen said she couldn't work with clients.
- Melbourne job-seeker Manny Flores said he missed a final Teams interview, rescheduled for the following week. Adelaide business owner Peter Roche said authentication problems blocked accounting and invoice processing. He described losing thousands of dollars as orders and invoices stopped moving.
- Those were individual experiences described in the earlier November thirteenth report. Students and vocational-education users also described interrupted study support and virtual classes. The accounts show specific work that couldn't proceed, without providing a total financial loss or a medical outcome from the delayed scans.
- IndiGo and CemAir reported messaging difficulties without reporting flight disruption in those announcements. An earlier second-hand account described a flight to Papua New Guinea waiting for printed pre-flight documents. The carrier, length of that delay and final outcome weren't identified.
- Air India said its flight operations remained unaffected. Those different experiences show how a communications failure can interrupt one workflow while another continues. They also explain why an operating meeting, clinic or aircraft can't stand in for every service dependent on the same platform.
- OpenAI continues investigating problems with new Microsoft connector connections and related tools. Anthropic's latest displayed update still describes most Microsoft 365 connector mail, calendar and search requests failing. Claude for Outlook remains affected in that update, which dates from Thursday night.
- Earlier Anthropic updates also described SharePoint, Teams chat and add-in problems. These failures affect assistants' access to connected Microsoft information. Workhorse Group also postponed its quarterly results and results-and-outlook call because of the outage. The call moved to November sixteenth at four-thirty in the afternoon, US Eastern.
- Microsoft has added protection for delayed messages while it rebuilds capacity. But service health remains variable, and the incident still carries the classification of service degradation. Sustained capacity and backlog clearance are the tests still ahead, with no full-restoration time announced.
- Microsoft's next update is due by eleven UTC on November thirteenth. That's a target for more information. The company has promised its full post-incident findings after mitigation, but hasn't set a publication date.





