Microsoft 365 - Service Health

Overview

The Service Health monitoring test appears in the Microsoft 365 section of the monitoring console.

Monitoring Benefit

The Service Health test surfaces the status Microsoft publishes on the Microsoft 365 Service Health dashboard, presented in the ENow console alongside the rest of your environment, together with the update posts Microsoft adds to an incident as it progresses.

The value is not that it detects anything Microsoft has not — it is that you stop having to watch two places. A Microsoft-side incident shows up next to your own on-premises and hybrid indicators, so when something breaks you can tell at a glance whether it is yours to fix.

This test relays Microsoft's own reporting. It does not independently probe the service. That distinction matters in both directions, and it is the single most useful thing to understand about this indicator:

• If Microsoft has not declared an incident, this indicator stays green — even when your users are affected. A green Service Health indicator is not evidence that a workload is healthy for you.
• If this indicator turns, Microsoft has declared something. That is a reliable signal, but it usually arrives after your users have noticed.

For that reason, treat Service Health as corroboration rather than detection. ENow's synthetic transaction tests are what tell you whether a workload is working for your tenant; Service Health tells you whether Microsoft agrees there is a problem, and what they are saying about it.

How do we verify the monitoring test results?

1. Compare against the source. The status shown here comes from the Microsoft 365 admin center. Sign in and open Health > Service health to see the same incidents Microsoft is reporting for your tenant. The two should agree; if they do not, the collection has not refreshed yet.

2. Read the update posts. Microsoft adds updates to an incident as it progresses, and those updates carry the detail — which workloads and regions are affected, whether mitigation is underway, and the expected timeline. The indicator alone only tells you an incident exists.

3. Check whether the incident actually affects you. Service health incidents are scoped to particular services and often to particular regions or infrastructure. An incident being reported does not always mean your users are among those impacted.

4. Corroborate with your own tests. Where a Microsoft incident is declared, the ENow synthetic transaction tests for that workload show whether it is actually degraded for your tenant. Where users are complaining and Service Health is green, trust the synthetic tests — Microsoft has not declared anything yet.

Common warning or error results, and potential solutions

Related

• Microsoft 365 Service Health and Continuity — background on how Microsoft classifies incidents, what a post-incident review contains, and the notification cadence Microsoft commits to.