Where Copilot issues are tracked: Service health for incidents and Message center for changes.
From Ultra Transcenders AB-650 by Tony Rough (coming November 2026)
Copilot depends on many cloud services, so when something fails an administrator first checks whether Microsoft already knows. Learn’s Copilot controls articles do not describe a separate Copilot health console. Copilot service issues are tracked, like other Microsoft 365 issues, in Service health, with change announcements in Message center.
Open Health > Service health in the Microsoft 365 admin center (or use the card on the home page).
| Item | What it shows |
|---|---|
| Overview tab | Every service with its health state and active incidents or advisories |
| Issues for your organization to act on | Problems found in your environment that need your action; hidden when there are none |
| Active issues Microsoft is working on | Open incidents and advisories |
| Issue history | Resolved issues from the last 7 or 30 days |
| Reported issues | Issues your tenant reported with Report an issue, with their status |
An incident is critical: the service or a major function is unavailable. An advisory is a lesser problem that affects some users while the service stays available, often with a workaround. Issue detail pages show ID, last updated time, estimated start, affected services, issue type, origin (Microsoft or your environment), status, user impact and a feed of updates.
Configure notifications under Customize:
Planned maintenance does not appear in Service health. Follow the Message center, filtered to Plan for change messages. Graph’s service communications API exposes the same data programmatically.
Roles: Service Support Administrator and Helpdesk Administrator can view service health. The AI Administrator can read and configure Azure and Microsoft 365 service health dashboards, along with usage reports and support tickets, and so can manage most Copilot monitoring without Global Administrator.
When Copilot features are missing for a user, rule out licensing before you suspect an outage. The Copilot service plan diagnostic tool (Support > Help and support, enter copilot missing, needs the AI Administrator role) lists the Copilot service plans assigned to a user. A user missing a service plan can lack a feature even while Service health is green. Where a problem affects Copilot Dashboard metrics, Learn directs admins to check the Service health dashboard for the latest updates.
Common trap: Planned maintenance for Copilot services appears on the Service health dashboard - planned maintenance is not shown there; track it in Message center under Plan for change.
Common trap: A green Service health page means a user’s missing Copilot feature is a user problem to ignore - a missing service plan on the user’s licence can remove functionality; check it with the Copilot service plan diagnostic tool.
This note is one section of Ultra Transcenders AB-650: Administering Microsoft 365 and AI Services, an independent study guide that explains every topic the exam covers by technology, with comparison tables, diagrams and the common traps, plus a glossary linked to Microsoft Learn.
Due on Amazon in November 2026, in Kindle and paperback editions.
About the book · AB-650 terms in the glossary · All AB-650 study notes
Which groups can carry licences, who can assign them and how membership drives access.
How administrative units scope roles to a subset of users, groups and devices.
How built-in and custom authentication strengths define which method combinations satisfy a policy.
How a Conditional Access policy combines assignments, conditions and access controls.
What the harmless phishing simulations are, and the licence and permissions needed to run them.
What the Copilot policy location is, which template offers it and the controls it provides.
How SharePoint data access governance reports and Purview data risk assessments help to find oversharing.
The three audience options for when tenant users receive new features, and where Frontier fits.