{"slug": "microsoft-officially-apologized-for-yesterday-s-outages", "title": "Microsoft Officially Apologized for Yesterday's Outages", "summary": "Microsoft apologized on Friday for a Thursday outage that degraded Microsoft 365, Teams, Outlook, Copilot, OneDrive and other services, with Downdetector logging hundreds of thousands of Outlook user reports and still over 50,000 reports every 15 minutes on Thursday afternoon. Microsoft said the incident was \"a technical issue not related to cyber or AI [or] agents\" introduced during an earlier network capacity upgrade that surfaced after a recent network change, and that it has addressed the underlying issue while continuing to restore service to remaining customers and regions. Microsoft said it is \"deeply sorry\" and will publish a full post-incident report after completing its review.", "body_md": "If you were having trouble accessing certain services like Microsoft Teams or Outlook, you were not alone. Early Thursday afternoon, many of Microsoft's biggest apps and services were experiencing downtime. [According to Downdetector](https://downdetector.com/), which tracks user reports of issues with websites and platforms, Microsoft 365, Teams, Copilot, Teams, and OneDrive were all experiencing issues. As of Friday afternoon, Microsoft has restored service to many users, and has officially apologized for the outages.  \n\n## Which Microsoft services were affected by the outages?\n\nWhen I first published this article on Thursday, I couldn't even load [Microsoft 365's status page](https://status.cloud.microsoft/m365/referrer=serviceStatusRedirect). (I've reported on many service outages, but I can't recall a time when a service's status page was also down.) Even as of Friday afternoon, the page still says \"Service degradation on Microsoft 365 (Business or Enterprise),\" and Microsoft says the following services may be affected: Exchange Online, Microsoft 365 admin center, Microsoft 365 apps, Microsoft 365 Apps Admin Center, Microsoft 365 Education, Microsoft Copilot 365, Microsoft Defender for Office 365, Microsoft Defender XDR, Microsoft Fabric, Microsoft Graph, Microsoft Intune, Microsoft Planner, Microsoft Power Apps, Microsoft Purview, Microsoft Teams, Microsoft To Do, Power BI, SharePoint Online, Universal Print, and Windows 365. \n\n[Looking specifically at Outlook](https://downdetector.com/status/outlook/), Microsoft's email service had hundreds of thousands of user reports Thursday afternoon, signaling a major issue somewhere in Microsoft's pipeline. The reports did \"slow down\" throughout the day, but Downdetector still showed over 50,000 reports coming in every 15 minutes when I checked Thursday afternoon. \n\n## What caused these Microsoft outages?\n\nWhile the root cause of the issue was a mystery throughout Thursday's outage, [Microsoft confirmed the problem in an apology on Friday](https://x.com/Microsoft/status/2121282013600907325?a=3hrRKuFoW0rsg8OkWyA&s=20). According to the company, \"This was a technical issue not related to cyber or AI [or] agents. The incident was introduced by an issue during an earlier network capacity upgrade that surfaced following a recent network change. We have addressed the underlying issue and continue to restore service to remaining customers and regions.\" \n\nMicrosoft says it is \"deeply sorry\" for the disruption to its customers and partners. The company says the fix rolled out slower than some might expect, since it wanted to restore service gradually to evaluate stability at each stage. It also says it will release a full post-incident report once it completes a review.\n\nDuring the outage, the company had confirmed that some of its infrastructure was experiencing elevated load, which it said was likely contributing to the issues. Microsoft then said it was pausing all deployments and moving traffic from affected infrastructure, and that it found that a number of its servers were unexpectedly unavailable after failing health checks. The company then thought a specific component responsible for processing server health may be the reason the system is failing health checks. Microsoft said an alternative service health check method successfully restarted some of the affected servers. The company was then actively restarting and validating affected servers to bring them back to service.\n\n        [This Tweet is currently unavailable. It might be loading or has been removed.](https://twitter.com/MSFT365Status/status/2120938282204688468)", "url": "https://wpnews.pro/news/microsoft-officially-apologized-for-yesterday-s-outages", "canonical_source": "https://lifehacker.com/tech/microsoft-officially-apologized-for-yesterdays-outages?utm_medium=RSS", "published_at": "2026-11-13 17:55:20+00:00", "updated_at": "2026-11-13 18:53:59.349606+00:00", "lang": "en", "topics": ["ai-products"], "entities": ["Microsoft", "Microsoft 365", "Microsoft Teams", "Outlook", "Microsoft Copilot", "OneDrive", "Downdetector"], "also_reported_by": [], "alternates": {"html": "https://wpnews.pro/news/microsoft-officially-apologized-for-yesterday-s-outages", "markdown": "https://wpnews.pro/news/microsoft-officially-apologized-for-yesterday-s-outages.md", "text": "https://wpnews.pro/news/microsoft-officially-apologized-for-yesterday-s-outages.txt", "jsonld": "https://wpnews.pro/news/microsoft-officially-apologized-for-yesterday-s-outages.jsonld"}}