On June 11, 2021, at ~3:02 pm UTC, Microsoft began reporting a Microsoft Teams issue in which incoming calls were being sent straight to voicemail.
Approximately an hour later, Microsoft was reporting on issue identification and a remediation effort (rollback) was underway.
At ~5:41 pm UTC, Microsoft repeated their message that remediation measures continued and that they were investigating other means to restore functionality.
Some 5 hours after first reporting the issues, many users on Twitter were still reporting Teams calls going to voicemail and subsequent business disruptions. At ~7:43 PM UTC, Microsoft confirmed they were continuing to investigate other options in an effort to provide relief to those still being impacted.
By ~10:45 pm UTC, Microsoft was finally able to confirm the issue was resolve for all Teams desktop clients, however mobile app users would need additional time for full recovery.
Here are resources for Microsoft Teams monitoring and reporting during service outages.
The Importance of Office 365 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 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:
- The ability to monitor 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.