



At this time, Microsoft also confirmed that they were routing connections to remediate.Īt approximately 05:53 UTC, Microsoft had declared the matter fully resolved. 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. There were very few responses from the "Twitterverse", which is usually an indication of a minor service incident.Īpproximately 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. For system admins and IT professionals with Microsoft Admin Center access, the incident reference numbers were P元34860 and TM334862. Initially, Microsoft provided little information as to how users were being impacted, and little information as to the geo regions impacted. On February 21, 2022, at ~03:58 am UTC, Microsoft communicated via tweet ( that they were investigating a service incident impacting Microsoft Planner, Tasks, and Teams.
