On August 19th at roughly ~3:30 pm UTC, Microsoft reported an issue with users being unable to join Teams meetings.
Shortly after, they determined that any user attempting to join a Teams meeting hosted in North America could be impacted by the issue. They also reported that they had re-routed traffic to an alternative environment and had seen some recovery.
People both inside and outside of North America began confirming that they were experiencing issues and expressed concerns as to when the outage would be resolved.
Some users suggested that the issue was stemming from an increased number of users as some schools throughout the U.S. have begun to start back up with online learning.
At ~7:00 pm UTC, Microsoft reported that they continued to observe recovery within the environment. However, they were still experiencing intermittent increases in traffic.
Finally, a day later at ~6:00 pm UTC, Microsoft confirmed that they had rerouted traffic and implemented configuration changes which had remediated impact.
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.