Update, November 14, 2026, 1:04 PM IST: Microsoft’s public service-health dashboard now says “All products are operational,” ending the service-degradation status carried during the Microsoft 365 outage.
France 24, reporting with Reuters and AFP, says Microsoft has restored service to the remaining affected customers and regions across Teams, Outlook, Copilot and other applications. The earlier recovery updates below record the incident’s progression and are no longer the current service status.
Earlier on Saturday: stability and email-backlog monitoring
Update, November 14, 2026, 8:05 AM IST: Microsoft says service recovery is continuing across previously affected environments, but it is keeping the incident open while it monitors stability and the email backlog. Its public service-health notice, last updated at 3:30 AM IST, says most affected scenarios appear to have been addressed.
The company is watching recovery for an extended period and checking that queued email messages process successfully before calling the issue resolved. The dashboard still lists service degradation. That is a more cautious status than a global all-clear, even if an individual mailbox or app is working again.
Earlier overnight recovery update
Update, November 14, 2026, 12:04 AM IST: Microsoft says it has addressed the underlying issue behind the Microsoft 365 outage and is seeing broad recovery and stability. Its public service-health update, issued at 11:27 PM IST on November 13, links the incident to an earlier network capacity upgrade whose problem surfaced after a recent network change.
The company describes it as a technical issue, not one related to cyber activity or AI/agents. This is still not a global all-clear: Microsoft says restoration continues for remaining customers and regions, and the public dashboard still shows service degradation. A full post-incident report will follow its review. BBC News’ live reporting also carries the company’s explanation and apology.
Earlier on Friday evening
Update, November 13, 2026, 9:04 PM IST: Microsoft’s latest public status update, issued at 8:26 PM IST, reports sustained improvements across affected Microsoft 365 services. The company says it is concentrating on the remaining problems and checking recovery across different connection methods.
This is still not an all-clear: some users may face intermittent connection problems or delayed email. Microsoft continues to say it has no evidence of malicious activity, rather than declaring a final cause. A post-incident report with the root cause is promised after mitigation. BBC News’ live reporting corroborates the improvement and continuing disruption.
Earlier recovery updates
Update, November 13, 2026, 5:18 PM IST: Microsoft says recovery actions have been completed across parts of the affected infrastructure in the Asia Pacific region. Its public service-health update reports gradual traffic restoration and improvements in mailbox access and delayed-email processing, while warning that some users may still face intermittent problems.
The company is now extending those recovery actions to affected infrastructure in other regions and adding capacity. This is regional progress, not a global all-clear. Reducing email backlogs remains a priority, and the extended 48-hour timeout window is still in place to help protect delayed messages.
Earlier on Friday: what was affected
Microsoft 365 recovery is still under way, with Outlook and other services facing uneven access on Friday. At a 4:18 PM IST check on November 13, Microsoft’s public service-health page continued to show service degradation, despite incremental improvement across parts of its infrastructure.
The important distinction is that this is not a complete shutdown of every Microsoft app. The official status page says features that interact with Exchange Online and email are affected, while functions that do not depend on those connections can remain available.
What was affected in Outlook, Teams and Copilot?
Microsoft says Exchange Online users may be unable to open mailboxes through Outlook on the web, the desktop app and other connections. Email delivery can also be delayed.
Teams is more mixed. Microsoft says most core calling, meeting, group-chat and channel-message functions are not affected. Features connected to Exchange Online, including calendar scheduling, invitations and meeting edits, can fail. That means a working Teams chat does not prove the wider incident is over, and a calendar problem does not mean every Teams function is down.
Microsoft 365 Copilot users may have trouble loading chat, getting responses or accessing work information such as email, calendars and files. SharePoint external sharing and features tied to Exchange Online can also be affected, although Microsoft says direct access to files stored in SharePoint Online remains functional.
The earlier recovery phase
Before the operational status returned, Microsoft reported sustained recovery and said it was monitoring stability and the email backlog. That earlier phase should not be confused with the operational status shown at the top of this report.
The company says it is prioritising email queues and backlogs. It has extended the email timeout window to 48 hours to help preserve delayed messages during recovery. That is a protection measure, not a promise that every email will arrive within a particular time.
BBC reporting describes disruption across businesses and public services, with users experiencing different levels of access. The Guardian also reports that signs of stabilisation have not yet meant a full return to normal.
What to check if problems continue
Start with Microsoft’s service-health page or your organisation’s IT team before treating this as a problem with one device or account. The public dashboard now shows operational status. If a problem persists, an organisation’s IT team can check its tenant-specific service notices and distinguish a local or account problem from any remaining effects.
For Power Apps and Field Service mobile users specifically, Microsoft says the web versions may provide an alternative. It also says users already signed in may avoid some impact by not signing out, clearing app data or reinstalling while the issue continues. That guidance is specific to those apps, not a general fix for every affected Microsoft product.
Microsoft now attributes the outage to a technical issue involving network changes, rather than cyber activity or AI/agents. The full post-incident report is still pending. The public dashboard now reports operational status; the earlier dated entries explain how recovery developed.
Status rechecked November 14, 2026, at 1:04 PM IST. Earlier dated entries record the progression of recovery on November 13 and overnight; the service-by-service breakdown records the features flagged during the incident, not a current list of outages. Archive photo: Building 92 at Microsoft’s Redmond campus on June 18, 2015, not the affected infrastructure or a photograph of this outage. Photo: Jiaqian AirplaneFan, via Wikimedia Commons, CC BY 3.0. Resized and compressed to WebP.
