This chapter covers the Microsoft 365 Service Health Dashboard (SHD), a critical tool for monitoring the operational status of Microsoft 365 services. For the MS-900 exam, understanding the SHD is essential because it appears in questions about service continuity, incident communication, and administrator responsibilities. Approximately 5-10% of exam questions touch on service health monitoring, often asking where to find status information or how to interpret advisories. You will learn the dashboard's purpose, how it works, key components, and how to use it effectively in enterprise scenarios.
Jump to a section
Imagine a major international airport with hundreds of flights daily. The air traffic control (ATC) tower monitors every flight's status: on-time, delayed, diverted, or cancelled. The ATC system aggregates data from radar, weather stations, and pilot reports to provide a real-time overview. For each flight, it shows the current status, estimated time of arrival, and any known issues. When a storm causes delays, the ATC updates the board, and airlines adjust schedules accordingly. Similarly, the Microsoft 365 Service Health Dashboard (SHD) is the central monitoring system for all Microsoft 365 services. It collects health signals from millions of servers and network paths worldwide, aggregates them, and displays the current status of each service (e.g., Exchange Online, SharePoint, Teams). When an incident occurs, the dashboard shows a service health advisory with details like cause, scope, and estimated time to resolution. Just as ATC provides actionable information to pilots and ground crew, the SHD gives IT administrators the data they need to communicate with users and plan workarounds. The analogy breaks down if you think ATC controls the flights; in reality, ATC monitors and coordinates, just as the SHD monitors but does not control the underlying services. The SHD is a read-only view of Microsoft's internal monitoring, not a tool to fix issues directly.
What is the Microsoft 365 Service Health Dashboard?
The Service Health Dashboard (SHD) is a centralized, real-time monitoring interface within the Microsoft 365 admin center (https://admin.microsoft.com/Adminportal/Home#/servicehealth) that displays the current health status of all Microsoft 365 services. It is the official source for service incidents, advisories, and planned maintenance. The SHD is part of Microsoft's commitment to transparency and operational excellence, governed by the Microsoft Online Services Terms and the Service Level Agreement (SLA).
Why Does It Exist?
Microsoft 365 is a distributed, multi-tenant cloud platform with hundreds of services running across global datacenters. Despite robust design, outages and degradations can occur due to software bugs, network failures, configuration errors, or external factors like DDoS attacks. The SHD provides a single pane of glass for administrators to:
Verify if an issue is caused by Microsoft or is environment-specific.
Get official communication during incidents, including root cause and estimated resolution time.
Plan maintenance windows by reviewing upcoming changes.
Meet compliance requirements by documenting service availability.
How It Works Internally
The SHD aggregates data from Microsoft's internal monitoring systems, which include: - Proactive monitoring: Synthetic transactions that simulate user actions (e.g., sending an email, joining a Teams meeting) from multiple geographic locations every few minutes. - Telemetry: Aggregated error logs and performance metrics from millions of devices and servers. - User reports: Issues reported through the Microsoft 365 admin center or support channels.
When a threshold is breached (e.g., login failure rate > 5% for 10 minutes), an incident is automatically created. Microsoft's Site Reliability Engineers (SREs) triage, investigate, and update the incident record. The SHD reflects these updates with a latency of approximately 5-15 minutes.
Key Components
- Service Health Dashboard Page: Shows a list of all services (e.g., Exchange Online, SharePoint Online, Microsoft Teams, Microsoft 365 suite). Each service has a status icon: green (healthy), yellow (advisory), red (incident), or blue (maintenance). - Incidents: Active service interruptions. Each incident has: - Title: Brief description. - Status: Investigating, restoring service, extended recovery, or post-incident report. - User Impact: Description of what users experience. - Scope: Tenant-specific or broader (e.g., all tenants in a region). - Start Time: When the issue began. - Estimated Time to Resolution: Microsoft's best guess. - History: Chronological updates. - Advisories: Non-critical issues like performance degradation or feature unavailability. May not affect all users. - Message Center: Separate from SHD, but related. Used for planned changes, feature updates, and deprecations. Not for incidents. - Health History: Archived incidents and advisories for the past 30 days (accessible via download). - RSS Feed: Subscribe to service health updates for specific services. - Service Health API: Programmatic access for integrating with external monitoring tools.
Configuration and Verification
To access the SHD: 1. Sign in to https://admin.microsoft.com with a Global Admin, Service Support Admin, or Helpdesk Admin role. 2. Navigate to Health > Service health. 3. Optionally, filter by service or message type.
To verify the current status of a specific service, you can use the Microsoft 365 admin center mobile app or the Microsoft 365 Service Health Status page (https://status.office365.com/), which is publicly accessible without authentication but shows only high-level status (no tenant-specific details).
How It Interacts with Related Technologies
Azure Service Health: For Azure services, not Microsoft 365. However, some Microsoft 365 services depend on Azure (e.g., Azure AD for authentication). The SHD may reference Azure Service Health for underlying infrastructure issues.
Microsoft 365 Admin Center: The SHD is embedded within the admin center. The admin center also provides a unified view of incidents across Microsoft 365 and Azure for hybrid scenarios.
Microsoft 365 Defender: Provides security-related health, but not service availability.
Microsoft Graph API: The Service Health API (part of Microsoft Graph) allows programmatic retrieval of service health data. Endpoint: https://graph.microsoft.com/v1.0/admin/serviceAnnouncement/healthOverviews.
Specific Values and Defaults
Data retention: Incident history is retained for 30 days. Archived data can be downloaded as CSV.
Update frequency: The dashboard refreshes every 5 minutes automatically. Manual refresh is available.
Role requirements: To view the SHD, a user must have at least one of these roles: Global Administrator, Service Support Administrator, Helpdesk Administrator, or a custom role with the ServiceHealth.Read permission.
RSS feed URL: https://admin.microsoft.com/feed/servicestatus?culture=en-US (replace culture for localized feeds).
SLA commitment: Microsoft provides a 99.9% uptime SLA for most services, but the SHD does not calculate SLA compliance — that is tracked separately in the Microsoft 365 admin center under Billing > Licenses > SLA Summary.
Common Exam Traps
Trap 1: Confusing the Service Health Dashboard with the Message Center. The Message Center is for planned changes and new features, not incidents. The exam may ask where to find information about a current outage — answer is SHD, not Message Center.
Trap 2: Thinking that the SHD shows tenant-specific issues only. While it does show tenant-specific incidents, it also shows broader incidents affecting multiple tenants. The scope is indicated in the incident details.
Trap 3: Assuming that the SHD can be used to report an issue. The SHD is read-only; to report an issue, use the Support > New service request in the admin center.
Trap 4: Believing that the SHD updates in real-time. There is a 5-15 minute delay from detection to dashboard update.
Trap 5: Thinking that the public status page (status.office365.com) shows the same detail as the admin center SHD. The public page shows only high-level status and does not include tenant-specific incidents or detailed user impact.
Access the Service Health Dashboard
Sign in to the Microsoft 365 admin center (https://admin.microsoft.com) with an account that has the Global Administrator, Service Support Administrator, or Helpdesk Administrator role. Navigate to Health > Service health. The dashboard loads a list of all services with their current status. Each service is represented by a row with a colored icon: green for healthy, yellow for advisory, red for incident, and blue for planned maintenance. The page automatically refreshes every 5 minutes, but you can click the Refresh button to force an update.
Identify Active Incidents or Advisories
On the SHD page, look for services with yellow or red icons. Click on a service name to expand its details. Under the 'Active issues' tab, you will see a list of incidents and advisories. Each item shows the title, status (e.g., Investigating, Restoring service), user impact, start time, and estimated time to resolution. For advisories, the impact is typically lower and may affect only a subset of users. Note the incident ID (e.g., MO123456) for reference when communicating with Microsoft Support.
Review Incident Details
Click on an incident title to open the detailed view. This page includes a timeline of updates from Microsoft's engineering team. Each update includes a timestamp, a description of actions taken, and the current status. The 'User impact' section explains what users are experiencing (e.g., 'Users may be unable to send email'). The 'Scope' indicates whether the issue is tenant-specific or broader. If the incident is resolved, a 'Final update' is posted, and a post-incident report (PIR) may be available within 5 business days.
Subscribe to Notifications
To receive proactive notifications, you can configure email alerts for service health changes. In the SHD, click on 'Preferences' (gear icon) and select 'Email notifications'. Choose the services you want to monitor and the notification frequency (e.g., send a daily digest or send alerts as they occur). You can also add a webhook URL to receive notifications via Microsoft Teams or other messaging platforms. Additionally, you can subscribe to the RSS feed for specific services to integrate with your own monitoring tools.
Use the Service Health API for Automation
For enterprise environments that require custom monitoring dashboards or integration with SIEM systems, use the Microsoft Graph API. The endpoint is `https://graph.microsoft.com/v1.0/admin/serviceAnnouncement/healthOverviews`. You can retrieve current health status for all services or a specific service. For incidents, use `https://graph.microsoft.com/v1.0/admin/serviceAnnouncement/issues`. The API supports OAuth 2.0 authentication with the `ServiceHealth.Read` permission. This allows programmatic access to the same data as the SHD, enabling automated alerting and reporting.
Enterprise Scenario 1: Global Company with 50,000 Users
A multinational corporation relies on Microsoft 365 for email, Teams, and SharePoint. When users report that they cannot access Exchange Online, the IT helpdesk first checks the SHD. They see an incident titled 'Users unable to access Exchange Online' with status 'Restoring service' and an estimated resolution time of 2 hours. The IT team posts a message on the company's internal portal informing users of the known issue and that Microsoft is working on it. They also set up email notifications for the incident so they receive updates automatically. Without the SHD, the helpdesk would waste hours troubleshooting the environment before realizing it is a Microsoft-side issue. The SHD saves time and provides official communication to users.
Enterprise Scenario 2: Healthcare Organization with Compliance Requirements
A hospital uses Microsoft 365 for secure communications. They must document any service outages for compliance with HIPAA. The IT compliance officer regularly exports the service health history from the SHD (available as CSV download for the last 30 days). When an incident occurs, they save the incident details including start time, impact, and resolution time. This documentation is used to verify that Microsoft met the SLA. If the SLA was breached, the organization may be eligible for service credits. The SHD's historical data is crucial for this process. Misconfiguration: If the organization relies solely on the public status page, they miss tenant-specific details and cannot prove SLA breaches.
Scenario 3: MSP Managing Multiple Tenants
A managed service provider (MSP) manages Microsoft 365 for dozens of small businesses. They use the Service Health API to aggregate health status across all tenants into a single dashboard. They set up webhook notifications to receive real-time alerts. When an incident affects multiple tenants, they quickly communicate with all affected clients. They also use the API to automate ticket creation in their PSA system. Performance consideration: The API has throttling limits — 10,000 requests per tenant per hour. The MSP must design their polling frequency to stay within limits. If they poll too frequently, they get throttled and miss updates. A common mistake is polling every minute; instead, they poll every 5 minutes and rely on webhooks for critical updates.
MS-900 Objective Coverage
The Service Health Dashboard falls under objective 4.3: 'Describe the service health and availability monitoring tools in Microsoft 365.' Specifically, the exam tests: - Identify the correct tool for monitoring service health: The SHD is the primary tool. The exam may present scenarios and ask where to find information about an outage. - Distinguish between SHD and Message Center: The Message Center is for planned changes, not incidents. This is a frequent distinction. - Understand role requirements: Only certain admin roles (Global Admin, Service Support Admin, Helpdesk Admin) can view the SHD. A user with no admin roles cannot see tenant-specific incidents. - Interpret status icons: Green (healthy), yellow (advisory), red (incident), blue (maintenance). - Know the public status page: status.office365.com shows high-level status without authentication.
Common Wrong Answers
'Use the Message Center to check for outages.' — Wrong because Message Center is for planned changes, not incidents. Candidates confuse the two because both are in the admin center under Health.
'The SHD shows real-time data with no delay.' — Wrong; there is a 5-15 minute delay. The exam may state 'immediate' as a distractor.
'Any user can view the SHD.' — Wrong; only users with specific admin roles. The exam may say 'all users' or 'global admin only' — the correct answer includes Service Support Admin and Helpdesk Admin.
'The SHD can be used to report an issue.' — Wrong; it is read-only. Reporting is done via New service request in Support.
Specific Numbers and Terms
Data retention: 30 days for incident history.
Roles: Global Administrator, Service Support Administrator, Helpdesk Administrator.
Refresh interval: Every 5 minutes.
Public status URL: status.office365.com.
API endpoint: /v1.0/admin/serviceAnnouncement/healthOverviews.
Edge Cases
Hybrid deployments: If an on-premises server is down, the SHD does not show that. The exam may ask what to use for on-premises health — answer is System Center or other monitoring tools.
Third-party dependencies: If a third-party app integrated with Microsoft 365 is down, the SHD does not reflect that. The exam may test that the SHD only covers Microsoft-owned services.
Multiple tenants: A user with admin roles in one tenant can only see that tenant's SHD. They cannot see another tenant's incidents unless they have delegated access.
How to Eliminate Wrong Answers
If the question mentions 'planned maintenance' or 'new features', the answer is Message Center, not SHD.
If the question asks about 'real-time', look for 'near real-time' or '5-15 minute delay' — any option saying 'immediate' is wrong.
If the question involves reporting an issue, the answer is 'New service request', not SHD.
If the question involves SLA credits, the answer is to check the SLA summary in Billing, not the SHD.
The Service Health Dashboard is the primary tool for monitoring Microsoft 365 service health and incidents.
Only Global Administrators, Service Support Administrators, and Helpdesk Administrators can view the full SHD.
The SHD has a 5-15 minute delay from incident detection to dashboard display.
The public status page (status.office365.com) shows only high-level status, not tenant-specific details.
The Message Center is for planned changes, not incidents.
Incident history is retained for 30 days and can be downloaded as CSV.
The Service Health API (Microsoft Graph) allows programmatic access to health data.
To report an issue, use the New service request in the admin center, not the SHD.
These come up on the exam all the time. Here's how to tell them apart.
Service Health Dashboard (SHD)
Displays current health status and active incidents/advisories.
Shows unplanned outages and service degradations.
Updates every 5 minutes; has a 5-15 minute detection delay.
Accessible only to users with specific admin roles.
Used for real-time monitoring and incident communication.
Message Center
Displays planned changes, new features, and deprecations.
Shows upcoming maintenance and feature rollouts.
Updates when Microsoft posts a new message; no automatic refresh.
Accessible to all admin roles (including non-global admins).
Used for planning and change management.
Mistake
The Service Health Dashboard updates in real-time with no delay.
Correct
There is a 5-15 minute delay from Microsoft's detection to the dashboard update. The dashboard refreshes every 5 minutes automatically, but the underlying monitoring data has latency.
Mistake
Any user can view the Service Health Dashboard.
Correct
Only users with the Global Administrator, Service Support Administrator, or Helpdesk Administrator role can view the full SHD. Regular users see a limited public status page (status.office365.com) that shows only high-level status.
Mistake
The Message Center and Service Health Dashboard are interchangeable for incident information.
Correct
The Message Center is for planned changes, feature updates, and deprecations. The SHD is for unplanned incidents and advisories. They serve different purposes and are located in separate sections of the admin center.
Mistake
The Service Health Dashboard can be used to report a new issue to Microsoft.
Correct
The SHD is a read-only view. To report an issue, you must create a new service request via Support > New service request in the admin center. The SHD only displays existing incidents.
Mistake
The public status page (status.office365.com) shows the same level of detail as the admin center SHD.
Correct
The public page shows only high-level status (e.g., 'Exchange Online - Healthy') and does not include tenant-specific incidents, detailed user impact, or estimated resolution times. It is a summary, not a replacement for the admin center SHD.
Reveal each answer, then mark whether you got it right. Score 60%+ to unlock the next chapter.
Sign in to the Microsoft 365 admin center (https://admin.microsoft.com) with an account that has the Global Administrator, Service Support Administrator, or Helpdesk Administrator role. Navigate to Health > Service health. If you do not have the required role, you will see a message indicating you do not have permissions. Alternatively, you can view the public status page at status.office365.com, but it shows less detail.
The Service Health Dashboard shows current service health, including active incidents (unplanned outages) and advisories (non-critical issues). The Message Center shows planned changes, such as new features, updates, and deprecations. Both are under the Health section in the admin center, but they serve different purposes. For exam questions, if the scenario involves an ongoing outage, the answer is the SHD; if it involves a planned update, the answer is the Message Center.
Yes. In the SHD, click on Preferences (gear icon) and select Email notifications. You can choose to receive a daily digest or immediate alerts for specific services. You can also set up a webhook to send notifications to Microsoft Teams or other platforms. Additionally, you can subscribe to the RSS feed for the SHD to integrate with other monitoring tools.
Incident and advisory history is retained for 30 days. You can download the history as a CSV file from the SHD by clicking 'Download health history'. This is useful for compliance and SLA tracking. For older history, you may need to use the Service Health API or contact support.
The required roles are: Global Administrator, Service Support Administrator, and Helpdesk Administrator. Custom roles with the ServiceHealth.Read permission also work. Other admin roles (e.g., Billing Admin) cannot view the SHD. The exam may ask which role is least privileged to view the SHD — the answer is Helpdesk Administrator.
No. The SHD only shows health status for Microsoft 365 cloud services. On-premises infrastructure (e.g., Exchange Server, Active Directory) is not monitored. For on-premises monitoring, you would use tools like System Center Operations Manager or third-party solutions.
Use the Microsoft Graph API endpoint: GET https://graph.microsoft.com/v1.0/admin/serviceAnnouncement/healthOverviews. You need an access token with the ServiceHealth.Read permission. The response includes current status, incidents, and advisories for each service. For detailed incidents, use: GET https://graph.microsoft.com/v1.0/admin/serviceAnnouncement/issues. This allows integration with custom dashboards or SIEM systems.
You've just covered Microsoft 365 Service Health Dashboard — now see how well it sticks with free MS-900 practice questions. Full explanations included, no account needed.
Done with this chapter?