On February 21, 2022, at ~03:58 am UTC, Microsoft communicated via tweet (@MSFT365status) that they were investigating a service incident impacting Microsoft Planner, Tasks, and Teams.
Initially, Microsoft provided little information as to how users were being impacted, and little information as to the geo regions impacted. For system admins and IT professionals with Microsoft Admin Center access, the incident reference numbers were PL334860 and TM334862.
There were very few responses from the "Twitterverse", which is usually an indication of a minor service incident.
Approximately 1 hour after first reporting, Microsoft communicated a second tweet, advising that it was a recent (MSFT) change which was causing an impact to a certain internal policy service. There were no details or elaborations by Microsoft as to what the change was, when the change was made, and what the impact to the internal policy service was. At this time, Microsoft also confirmed that they were routing connections to remediate.
At approximately 05:53 UTC, Microsoft had declared the matter fully resolved.
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!