On October 19, 2021, at ~5:40 am UTC, Microsoft communicated via tweet (@MSFT365status) that they were investigating an issue impacting users in the European geo not being unable to join or create meetings.
If you had access to the Microsoft admin center, the issue reference # was TM292507.
Responses from the public on Twitter were very few. which is usually indicative of a minor event. Although a business interruption for any business, large or small, is still a significant event, it does appear that this was a minor event.
Approximately one hour after first reporting the issue, at 7:06 am UTC, Microsoft reported that the issue had "self-recovered". Microsoft also confirmed the service impact was to Teams as to a "transient issue" resulting in degraded video and audio during calls. Little or no information was provided additionally by Microsoft as to the root cause of the "transient issue" nor as to the issue having "self-recovered". A check of status.office.com as of midday October 19, 2021, showed no ongoing service issues.
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 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.