On January 10, 2023, at ~5:32 AM ET, Microsoft communicated from their Twitter account @MSFT365status that they were investigating an issue in which some users were experiencing delays in sending and receiving messages in Microsoft Teams.
For system administrators and IT professionals with access to the Microsoft admin center, the service incident number to reference was TM495986.
Microsoft's next message, some 90 minutes later, confirmed that a "backend database issue" was the cause of the Teams messaging delays and failures, and, more importantly, this event was impacting users worldwide. Microsoft had not at this time confirmed that a fix was in place, but only that they were exploring mitigation options.
And by 8:21 AM ET, approximately 3 hours after first messaging as to this issue, Microsoft was confirming that the worldwide issue had been remediated.
The Importance of Teams Monitoring
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 Teams 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:
- The ability to monitor networks and entire environments in one place with ENow’s OneLook dashboard which makes identifying a problem fast and easy without having to scramble through Twitter and the Service Health Dashboard looking for answers.
- A full picture of all services and subset of services affected during an outage with ENow’s remote probes which covers several Office 365 apps and other cloud-based collaboration services.
Identify the scope of Teams outage impacts and restore workplace productivity with ENow’s Teams Monitoring and Reporting solution. Access your free 14-day trial today!
