Study guide

3.1 Monitoring Service Health & Notifications

Microsoft 365 Administrator Expert MS-102

Track your progress as you read

Finished sections get a check mark.

1 Introduction & Exam Overview

1.1 MS-102 Exam Facts & Blueprint 1.2 Registration, Retake & Renewal 1.3 Study Strategy & Using This Guide

2 Tenant Setup, Domains & Org Settings

2.1 Creating a Microsoft 365 Tenant 2.2 Implementing and Managing Domains 2.3 Configuring Org Settings: Security, Privacy & Profile

3 Service Health, Network & Software Updates

3.1 Monitoring Service Health & Notifications 3.2 Network Connectivity Insights 3.3 Configuring & Monitoring Software Updates

4 Adoption, Usage & Microsoft 365 Backup

4.1 Monitoring Adoption & Usage 4.2 Configuring & Managing Microsoft 365 Backup

5 Users, Contacts, Groups & Shared Mailboxes

5.1 Creating & Managing Users Including External Users 5.2 Creating & Managing Contacts 5.3 Managing Microsoft 365 Groups & Shared Mailboxes

6 Licensing & Bulk User Management

6.1 Managing & Monitoring Microsoft 365 Licenses 6.2 Bulk User Management with Graph & Entra PowerShell

7 Roles, Admin Units & Privileged Identity Management

7.1 Implementing & Managing Roles in M365 & Entra ID 7.2 Managing Permissions for Defender XDR, Purview & Workloads 7.3 Managing Delegation with Administrative Units 7.4 Managing Entra ID Roles in PIM

8 Identity Synchronization with Entra Connect

8.1 Preparing for Identity Synchronization & IdFix 8.2 Directory Sync with Entra Connect Sync & Cloud Sync 8.3 Monitoring Sync with Entra Connect Health 8.4 Troubleshooting Synchronization

9 Authentication, SSPR & Password Protection

9.1 Implementing & Managing Authentication Methods 9.2 Self-Service Password Reset (SSPR) 9.3 Microsoft Entra Password Protection 9.4 Investigating & Resolving Authentication Issues

10 Identity Protection, Conditional Access & MFA

10.1 Planning for Identity Protection 10.2 Implementing Entra Identity Protection 10.3 Planning & Implementing Conditional Access Policies 10.4 Managing MFA with Conditional Access

11 Defender XDR Posture, Incidents & Threat Intelligence

11.1 Security Exposure Management & Secure Score 11.2 Incidents, Alerts & Advanced Hunting 11.3 Reviewing Defender XDR Reports 11.4 Defender Threat Intelligence

12 Defender for Office 365: Policies, Alerts & Investigation

12.1 Threat Policies & Rules in Defender for Office 365 12.2 Configuring Alert Policies 12.3 Investigating & Responding to Email Threats

13 Attack Simulation & Restricted Entities

13.1 Managing Attack Simulations & Training 13.2 Managing Restricted Entities & Blocked Users

14 Defender for Endpoint

14.1 Onboarding Devices to Defender for Endpoint 14.2 Configuring Endpoint Settings 14.3 Defender Vulnerability Management Dashboard

15 Defender for Cloud Apps

15.1 Configuring the App Connector for Microsoft 365 15.2 Defender for Cloud Apps Policies & Alerts 15.3 Interpreting the Activity Log 15.4 Cloud App Discovery

16 Purview Information Protection & Data Lifecycle

16.1 Sensitive Information Types 16.2 Retention Labels & Policies 16.3 Sensitivity Labels & Policies 16.4 Monitoring Label Usage: Content & Activity Explorer

17 Purview Data Loss Prevention

17.1 DLP Policies for Microsoft 365 Workloads 17.2 Configuring Endpoint DLP 17.3 Reviewing & Responding to DLP Alerts, Events & Reports

18 Final Review & Exam Strategy

18.1 Exam-Day Strategy & Question Handling 18.2 Final Review Checklist & Next Steps

3.1 Monitoring Service Health & Notifications

Key Takeaways Explain This Topic AI

The Microsoft 365 Service Health dashboard in the admin center shows only incidents and advisories for services your tenant is licensed for — it is not a global status page for all of Microsoft

A service incident is an actively degrading issue with user impact; an advisory is a non-urgent notification about planned maintenance, minor degradation, or informational changes that do not typically interrupt service

Service Health notifications are configured under Settings → Org settings → Service health, where admins choose email, phone (SMS), or portal-only delivery and can target specific recipients or groups

The Service Communications API in Microsoft Graph exposes service health and message center posts programmatically, enabling NOC dashboards, ticketing integration, and custom alerting beyond the admin center UI

Service Health reflects current or recent service status, while the Message Center communicates planned changes, feature rollouts, and upcoming maintenance — the two are complementary, not redundant

Last updated: August 2026

Quick Answer: The Service Health dashboard in the Microsoft 365 admin center (Home → Health → Service health) shows active incidents, advisories, and resolved issues for the workloads your tenant is licensed for. Configure notifications under Settings → Org settings → Service health so the right admins get email, SMS, or portal alerts when Microsoft 365 degrades.

Microsoft 365 is a multi-tenant SaaS platform, and Microsoft operates the underlying infrastructure — but the administrator is still accountable for knowing when a service is degraded, communicating impact to users, and verifying restoration. The Service Health dashboard is the primary out-of-the-box tool for that situational awareness.

Where to Find It

In the Microsoft 365 admin center, navigate to Health → Service health . (Skilled admins can also reach it directly via admin.microsoft.com/AdminPortal/Home#/servicehealth .) The dashboard is scoped: it only displays entries for services your tenant has licensed. A tenant without Exchange Online, for example, will not see Exchange incidents even if a global Exchange outage is in progress.

What the Dashboard Shows

Each entry on the Service Health dashboard falls into one of three categories:

Service incident — an active or recently resolved event where the service is degraded or unavailable for some users. Each incident carries an IH (Incident) number (e.g., IH123456 ), a status (Investigating, Restoring service, Service restored, Post-incident report published), an issue type, a user impact statement, and an update history timeline.

Advisory — a non-urgent notification. Advisories cover planned maintenance that has no expected user impact, minor transient issues Microsoft is monitoring, or informational notes. Advisories do not generally interrupt service.

Resolved issue — an incident or advisory that has been closed, retained on the dashboard for a period so admins can review the post-incident report and timeline.

Status icons summarize each row: a green check indicates healthy, an orange triangle indicates an advisory, and a red diamond or exclamation icon indicates an active incident with user impact.

Reading an Incident's Details

Selecting an incident opens a detail pane with the headline issue, the affected workload, the scope of user impact (tenant-wide, a region, a feature subset), and a chronological update history . The IH number is the authoritative reference — quote it in support tickets and user communications so Microsoft Support can correlate your tenant with the broader incident. The update history is append-only: each new entry is timestamped (UTC) and shows the current status and any mitigation actions.

Admins on Targeted Release may see incidents affecting their users earlier than the general release population, because their tenant is in the first wave of a rollout. This is one of the operational reasons to put a small pilot group of IT staff on Targeted Release.

Configuring Notifications

Email, SMS, and portal notifications are configured under Settings → Org settings → Service health → Email notification settings . Available options include:

Recipients — specific admin email addresses, or a Microsoft 365 group / distribution list. Best practice is a dedicated m365-oncall group so on-call rotation changes do not require reconfiguring the alert.

Channels — email, phone (SMS text), and in-portal notifications. SMS is useful for critical incidents outside business hours.

Alert scope — choose to alert on incidents only , advisories only , or both . Most organizations alert on incidents only for SMS, and on incidents plus advisories for email, to limit noise.

Service filter — restrict alerts to specific workloads (e.g., Exchange Online, Microsoft Teams, SharePoint Online) so a Teams-only admin does not receive Exchange noise.

Notification delivery requires the recipient to be a Microsoft 365 administrator with Service Health read permissions. Global admins and Service Support admins can view and configure; custom roles with ServiceHealth.Read can view.

Service Health vs Message Center

A common MS-102 exam trap is conflating Service Health with the Message Center. They answer different operational questions.

  • Attribute Service Health Message Center
  • Question answered "Is the service broken right now?" "What is changing soon?"
  • Entry types Incidents, advisories, resolved issues Planned changes, feature rollouts, new docs
  • Time orientation Current and recent past Future and imminent
  • Typical action Inform users, verify restoration Plan change management, update training
  • Notification path Settings → Org settings → Service health Settings → Org settings → Message center
  • Programmatic access Service Communications API (Graph) Service Communications API (Graph)

The Message Center publishes posts about upcoming feature changes, retirements, and admin action items, often with a Act by date. Service Health posts about service degradation. Both flow through the same Service Communications API for programmatic consumption.

Programmatic Monitoring: Service Communications API

For organizations with a NOC, a ticketing system, or a custom status dashboard, the Service Communications API in Microsoft Graph exposes Service Health and Message Center data programmatically. The relevant endpoints live under https://graph.microsoft.com/v1.0/admin/serviceAnnouncement/ — healthOverviews for the per-service current status, issues for the incident/advisory list, and messageCenter for planned-change posts.

The API requires an access token with ServiceHealth.Read.All (delegated or application). Application permissions are useful for headless monitoring daemons that post to Teams channels or open PagerDuty incidents. This API is the same data source the admin center UI uses, so programmatic alerts and the portal are consistent.

Operational Best Practices

Maintain a dedicated m365-oncall group for notifications; rotate membership with the on-call schedule.

Document the escalation path when an incident is confirmed: who informs executives, who updates the status page, who drafts the user communication.

After any major incident, read the post-incident report (PIR) Microsoft publishes on the resolved entry — it explains root cause and remediation and is frequently referenced in MS-102 item stems.

Combine Service Health monitoring with Microsoft 365 usage analytics to correlate degradation with user-reported complaints.