Where to check a Microsoft 365 service problem
Verdict: When sign-in itself is blocked, check the public service status page - it works without authentication. Once signed in, check the Message center, filtered to Plan for change, for upcoming changes; Service health only covers current and past incidents.
| Criterion | Correct resource | Wrong pick to avoid |
|---|---|---|
| Admins locked out of the admin centre entirely, suspect a sign-in outage | The public service status page (works without sign-in) | Service health dashboard, Message center feed or organization profile (all live inside the admin centre, unreachable while locked out); the Azure Service Health blade also misses it, but because it covers Azure resources, not Microsoft 365 sign-in |
| Need advance notice of an upcoming Exchange Online change and how to prepare, Service health shows nothing relevant | Message center, filtered to Plan for change | Service health's Issue history, Reported issues or Overview tabs (show current or past incidents, not future plans) |
Rules
- Check the public service status page when sign-in itself is blocked; it works without authentication.
- Check the Message center, filtered to Plan for change, for advance notice of an upcoming change and how to prepare.
- Service health's Issue history, Reported issues and Overview tabs cover current and past incidents, never future planned changes.
- When locked out tenant-wide, of the admin-centre resources only the public service status page works without signing in.
Traps
- Candidates check Service health or the Message center when locked out entirely; both live inside the admin centre, which is exactly what's unreachable.
- Candidates check Service health's Issue history, Reported issues or Overview tabs for an upcoming planned change; those cover current or past incidents.
- Candidates check the organization profile or Message center feed when sign-in is blocked; both need a successful sign-in first.