Multiple users at Meridian Consulting are reporting that Microsoft 365 Copilot in Teams stopped generating responses approximately 45 minutes ago. The Microsoft 365 administrator needs to quickly determine whether this is an organization-wide service degradation, a configuration issue, or a subset of affected users, before escalating to Microsoft Support. What is the best first step?
Select an answer to reveal the explanation.
Short Explanation and Infographic
The Copilot Control System is your first stop for Copilot health issues — it combines service health with Copilot-specific context so you can see at a glance whether there's an active incident, which workloads it affects, and how widespread it is. Think of it as the Copilot-specific version of the service health dashboard.
Full explanation below image
Full Explanation
The Copilot Control System provides Copilot-specific service health monitoring that combines service health alerts, incident tracking, and adoption data in a single pane of glass. It allows administrators to quickly identify whether reported issues correspond to an active Microsoft-side incident (which would appear as an advisory or incident notification), isolate the scope (all users vs. subset), and determine whether the issue is service-wide or configuration-related — all before engaging Microsoft Support.
Option A is partially correct — the Microsoft 365 service health dashboard does surface service incidents including Copilot-related ones. However, the Copilot Control System is the MORE SPECIFIC and recommended answer because it provides Copilot-specific health context integrated with adoption and usage data, allowing for more nuanced diagnosis. If the exam offers the Copilot Control System as an option over the general service health dashboard for a Copilot-specific scenario, prefer the Copilot Control System.
Option C is incorrect because Test-CsTeamsMeetingPolicy is a Skype for Business/Teams meeting policy diagnostic cmdlet that validates Teams meeting feature policy assignment. It has no relevance to Microsoft 365 Copilot response generation issues. Copilot's Teams integration is not governed by Teams meeting policies.
Option D is incorrect because opening a Support ticket should be done AFTER the administrator has gathered diagnostic information and confirmed that the issue is not a known active incident already being worked by Microsoft. Opening a ticket without checking service health first wastes time and misses the possibility that Microsoft is already aware and working the issue. Diagnosis should always precede escalation.
Exam tip: The exam will test that the Copilot Control System includes service health monitoring (not just adoption metrics). The flow is: symptom reports → check Copilot Control System / service health → if active incident, monitor Microsoft's ETA; if no incident, investigate tenant configuration → escalate to support if needed. Know the sequence.