Microsoft 365 outage continues to affect Outlook and Teams users
A major service disruption has left global users unable to access core Microsoft apps, with the company currently working on traffic optimization.
The short version
- The outage began around 12:30 p.m. ET on Thursday, affecting Outlook, Teams, Copilot, and the Microsoft Store.
- Microsoft has extended the email timeout window to 48 hours to protect messages that were delayed during the disruption.
- The company ruled out a cyberattack as the cause of the incident.
- Service health remains variable as Microsoft implements traffic optimization across affected regions.
Why it matters
Because millions of businesses rely on Microsoft 365 for daily operations, these outages can halt productivity on a global scale. Understanding how these systems recover helps users manage expectations during large-scale infrastructure failures.
Scope of the disruption
A significant service disruption has impacted a wide range of Microsoft 365 applications over the last several days. Users across the globe have reported being unable to access core tools including Outlook, Teams, and Copilot. The issues also appeared to affect the Microsoft Store, creating a broad hurdle for both personal and professional users.
The problems first gained visibility on Downdetector starting around 12:30 p.m. ET on Thursday. While the volume of reports began to decrease in the United States overnight, the situation remained critical in other parts of the world. Reports of login failures and general service instability continued to surface in markets such as India and the United Kingdom.
Microsoft has acknowledged the severity of the situation and stated that it is treating the matter with urgency. The company has been providing regular updates through its official Microsoft 365 Status account on social media. These updates indicate that while some progress is being made, the recovery process is still ongoing and inconsistent across different regions.
Technical recovery efforts
To address the backlog of communications, Microsoft has taken the specific step of extending the email timeout window to 48 hours. This measure is designed to protect delayed emails from being lost or discarded while the system works to process the queue. It ensures that messages sent during the peak of the outage eventually reach their intended recipients.
The company has also initiated traffic optimization actions to stabilize the services. These actions are intended to manage the flow of data more effectively as the system attempts to return to its baseline capacity. Microsoft noted that these optimizations are being rolled out more broadly across the regions that were most heavily impacted by the downtime.
Despite these efforts, the company admitted that service health remains variable. They noted that capacity has not yet fully returned to baseline levels for everyone. This means that even if a user can log in, they might still experience slower speeds or intermittent issues as the infrastructure settles back into a normal state.
Security and root causes
In response to the widespread nature of the outage, many users expressed concern regarding the possibility of a malicious breach. Microsoft addressed these concerns directly on its Cloud Status page by ruling out a cyberattack. The company stated that it is not aware of any malicious activity that is causing the current incident.
While the cause has not been fully disclosed yet, Microsoft has committed to transparency regarding the technical failure. They have promised to provide a detailed post-incident report once the issue is completely resolved. This report will aim to explain the root cause of the disruption to help prevent similar occurrences in the future.
The lack of a clear cause has led to a variety of reactions online, including a surge of memes on social media. Because so many businesses depend on these tools for day-to-day operations, the inability to work has created a unique situation for employees. The outage has essentially forced a period of forced downtime for many organizations that rely on the Microsoft ecosystem.
User experience and status
The experience of the outage has varied significantly depending on the specific application and the user's geographic location. For example, some users reported that while they could still access Teams and Copilot, their Outlook inboxes remained completely inaccessible. This suggests that different components of the Microsoft 365 suite may be recovering at different speeds.
Microsoft has shared that they are seeing positive results for service stability as a result of their latest technical interventions. However, the goal of attaining persistent recovery is still the primary objective. The company is working to ensure that the fixes applied are durable and do not result in further fluctuations in service quality.
As the situation develops, the company continues to monitor the situation closely to identify any remaining pockets of instability. They are aiming to move from a state of active mitigation to a state of full restoration. Users are encouraged to keep an eye on official status pages for the most accurate information regarding their specific region.
What to watch
- The release of the official post-incident report detailing the root cause.
- Whether capacity returns to baseline for all international markets.
Try it
Check the official Microsoft 365 Status page for real-time updates on your specific region's service health.
Sources and links
- Officialdowndetector.com/status/outlook/ downdetector.com
- Postx.com/metamom23/status/2121082428274127014 x.com
- Postx.com/MSFT365Status/status/2121199246959378803 x.com
- Reportingpcmag.com: the article we sourced
Liked it? Say why
Add a line for other readers.
No account needed. We never show your email. Comments with links, ads or abuse are held and not shown. Your comment shows after a quick check.
Listen to the AI Wire headlines
Listen to the AI WireListen to our daily AI shows every morning: on your commute, in the shower, wherever you are
Listen to the daily showsFirst reported by pcmag.com · Read the original. Written by the SI Agent News Desk from the reporting above.Written with AI from the source above. Every number is checked against the source. Spot a mistake? Corrections.
