Airport operations IT wants to see which municipal departments actually use Copilot after rollout. Which approach matches fundamentals guidance?

Airport operations IT should use Copilot Analytics concepts to review department-level usage patterns and target enablement. That approach matches fundamentals guidance because Microsoft 365 report concepts for tenant-level activity totals do not show department-level adoption across municipal departments. Analytics-driven visibility shows which teams actually use Copilot after rollout so training, champions, and change support can be aimed where usage is weak instead of assuming uniform success across the airport organization.

Using Microsoft 365 report concepts to review tenant-level activity totals fails by concept: tenant-level totals show aggregate activity, not department-level usage, and municipal departments differ in workflows, shift patterns, and readiness. Using Viva Insights concepts to review department-level collaboration habits fails because collaboration habits measure meetings and communication patterns, not actual Copilot usage after deployment, and low usage is an enablement signal that requires Copilot Analytics rather than Viva Insights data. Using Microsoft Purview audit concepts to review department-level prompt history fails because audit records track individual interactions for compliance and investigation, not adoption or usage trends, so they cannot show which departments actually use Copilot.

Exam caveat: AB-900 Domain 3 links Copilot Analytics to monitoring usage so organizations can improve adoption. The exam is not asking you to mistake collaboration habits for actual usage data or to treat audit prompt history as adoption analytics. Distinguish department-level reporting for enablement from using tenant-level totals, collaboration habits, or audit prompt history as usage metrics.

Operational check: Pull Copilot Analytics-style department usage for airport ops, identify low-adoption municipal groups, confirm licenses are still appropriate, plan targeted enablement (office hours, prompt galleries, role&A), remeasure after the enablement wave, and do not substitute Purview audit prompt history for Copilot Analytics while still reporting aggregate adoption to leadership.