Office 365 Monitoring: Teams Outage December 7, 2020
On December 7, 2020, at ~3:00 pm UTC, Microsoft reported an issue with call quality within Microsoft Teams and that more details would be reported shortly.
Soon after, Microsoft reported that the impact described wasn't affecting all calls. They also reported that they were looking at recent deployments to confirm if any constituent elements were contributing to the impact.
Many users took to Twitter asking for the latest updates on the outage. Others expressed their frustrations with the impact this outage had on company productivity including pushing trainings and meetings.
A few hours later at 7:00 pm UTC, Microsoft reported that they identified some processing infrastructure with a higher number of failures than expected and have redirected traffic to accommodate. They also reported seeing signs of improvement and they would provide further details in the admin center.
Roughly an hour later, at 8:00 pm UTC Microsoft confirmed that rerouting traffic had mitigated the issue.
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.