On February 25, 2022, at ~09:37 am UTC, Microsoft communicated via tweet (@MSFT365status) that they were investigating a service incident in which users were experiencing issues within the Health section of the Admin Center.
Initially, Microsoft provided no incident number, since system admins and IT professionals who may have been unable to access the Microsoft Admin Center would be unable to reference any incident number for further details. Instead, Microsoft advised any users impacted to check status.office.com.
This was the third service incident this week, with prior issues as to Microsoft Teams on Feb. 21, and Microsoft Forms just yesterday Feb. 24.
Approximately one hour after first reporting the matter, Microsoft communicated via tweet that they were reverting a recent update in an effort to fix the issue.
Then, after almost four hours removed from their last tweet, Microsoft communicated a final message indicating that the issue was now fully resolved. It was at this time that Microsoft provided an incident number: MO336402.
Checks of status.office.com later in the day, showed no information as to the Admin Center service incident earlier in the day.
In a cloud-world, outages are bound to happen. While Microsoft is responsible for restoring service during outages, IT needs to take ownership of their environment and user experience. It is crucial to have greater visibility into business impacts during a service outage the moment it happens.
ENow’s Office 365 Monitoring and Reporting solution enables IT Pros to pinpoint the exact services effected and root cause of the issues an organization is experiencing during a service outage by providing:
Identify the scope of Office 365 service outage impacts and restore workplace productivity with ENow’s Office 365 Monitoring and Reporting solution. Access your free 14-day trial today!