![Microsoft 365 Exchange and Outlook Service Outage: Preliminary Details Revealed [Update]](https://cdn.thefilibusterblog.com/wp-content/uploads/2025/03/1594835886_outlook_red_story-640x375.webp)
Microsoft 365 Services Experience Outage
Microsoft has officially acknowledged an ongoing outage affecting key services, including Outlook, which is part of the Microsoft 365 suite. This announcement came through the company’s verified Microsoft 365 Status account on X, leaving many users unable to access critical features and services within Outlook.
We’re investigating an issue in which users may be unable to access Outlook features and services. Additional details can be found under MO1020913 in the admin center.
— Microsoft 365 Status (@MSFT365Status) March 1, 2025
While the official Microsoft 365 Service Health Status page currently indicates that all services are operational, users can expect the site to undergo updates to accurately reflect the incident as it unfolds.
Feedback from users on the Microsoft 365 Status thread suggests that the Admin Center portal is also facing accessibility issues, further complicating the situation.
Latest Updates on the Outage
We will keep you informed with any pertinent updates as more information becomes available.
Update – March 1, 9:45 PM PST: Since our initial communication, Microsoft has provided ongoing updates via their official X handle. The underlying issue was rapidly identified, with the company attributing the disruption to “problematic code.”
We’re reviewing available telemetry and customer provided logs to understand the impact. We’ve confirmed this issue is impacting various Microsoft 365 services. Refer to MO1020913 for more detailed information.
— Microsoft 365 Status (@MSFT365Status) March 1, 2025
We’ve identified a potential cause of impact and have reverted the suspected code to alleviate impact. We’re monitoring telemetry to confirm recovery. Refer to MO1020913 for more detailed information.
— Microsoft 365 Status (@MSFT365Status) March 1, 2025
Our telemetry indicates that a majority of impacted services are recovering following our change. We’ll keep monitoring until impact has been resolved for all services. Refer to MO1020913 or https://t.co/vB5FHDUOHj for more detailed information.
— Microsoft 365 Status (@MSFT365Status) March 1, 2025
Following our reversion of the problematic code change, we’ve monitored service telemetry and worked with previously impacted users to confirm that service is restored. Please refer to MO1020913 in the admin center for detailed information.
— Microsoft 365 Status (@MSFT365Status) March 2, 2025
For further updates and comprehensive information regarding this situation, please visit our source linked here: Source & Images.
Leave a Reply ▼