Office 365 Monitoring: Microsoft Forms Service Incident (Feb. 24, 22)
On February 24, 2022, at ~01:31 am UTC, Microsoft communicated via tweet (@MSFT365status) that they were investigating a service incident impacting Microsoft Forms.
For system admins and IT professionals with Microsoft Admin Center access, the incident reference number was FM335798. Where @MSFT365status was deficient with details, the Admin Center likely had more detailed information.
Less than 30 minutes later, Microsoft tweeted again that some users were seeing restoration of service. However, @MSFT365status gave no details as to root cause of the issue, nor details as to what were their remediation efforts thus far.
Approximately 60 minutes after first reporting the issue, Microsoft was now stating that the matter was fully resolved. Again, Microsoft gave no substantive details via @MSFT365status as to issue cause / issue resolution efforts.
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.