A city attorney's office wants Copilot in Teams meetings available first only for department leadership. How should that intent be framed at fundamentals depth?
Select an answer to reveal the explanation.
Short Explanation
Want leadership first for Teams meeting Copilot? That's feature enablement plus sensible access scoping — transcription and recording policies, sensitivity labels, and eDiscovery holds won't roll it out for you. Roll it out controlled, then expand.
Full Explanation
City attorney leadership-first rollout for Copilot in Teams meetings should be framed as Copilot feature enablement plus access scoping so meeting Copilot experiences reach leadership before broader staff. That fundamentals pattern lets the office pilot meeting summarization and related capabilities with a controlled cohort, gather governance feedback, then expand—without treating “everyone or no one” as the only options.
Using Teams meeting transcription and recording policies so meeting Copilot experiences roll out to leadership before broader staff confuses a prerequisite with enablement: those policies control whether transcription or recording is allowed, not whether the Copilot meeting experience itself is enabled and scoped to leadership first. Applying sensitivity labels to leadership Teams meetings so meeting Copilot experiences roll out to leadership before broader staff mistakes protection for enablement: labels control protection and sharing of meeting content, not the enablement and scoping of the Copilot meeting feature itself for leadership first. Configuring eDiscovery retention holds for leadership meetings so meeting Copilot experiences roll out to leadership before broader staff is a preservation action for discovery and retention, not a way to enable and scope Copilot meeting experiences to leadership first.
Exam caveat: AB-900 emphasizes that Copilot features can be enabled or disabled and rolled out thoughtfully; deep meeting-policy SKUs and every admin-center path are out of fundamentals depth. Transcript and recording retention still follow existing Teams and records policies even when Copilot is scoped.
Operational check: Enable the relevant Teams meeting Copilot experience for a leadership pilot group only, have a leadership user and a non-pilot staff user join a test meeting, and confirm the Copilot meeting experience appears only for the scoped cohort before any citywide enablement.
Prefer to study offline? Printable PDF study book + test engine ($7.50, unofficial). These questions stay free here.