An emergency-management office must grant Copilot to the first cohort of permitting supervisors. What basic admin task applies?

Basic Copilot administration for emergency management’s first permitting-supervisor cohort is to assign Copilot licenses to those users or groups. License assignment is the fundamentals gate that turns Copilot from a tenant capability into an available experience for named staff; group assignment scales the cohort cleanly as more supervisors complete readiness.

Assigning Viva Insights licenses to the permitting-supervisor cohort of users or groups grants a different workload focused on insights and employee experience, not Copilot, so the supervisors would still lack Copilot access. Enabling Copilot self-service purchase for the permitting-supervisor user cohort only permits users to purchase on their own and does not constitute admin assignment of licenses to the first cohort. Assigning Copilot licenses to the permitting-supervisor cohort of devices and rooms targets the wrong object type, because Copilot is assigned to users or groups, so the supervisors themselves would not be licensed.

Exam caveat: Assignment alone is necessary but not always sufficient—feature enablement, app availability, and network access still matter. AB-900 Domain 3 includes assigning Copilot licenses to users and groups as a core admin task.

Operational check: Create or use a permitting-supervisors group, assign Copilot licenses via that group (or direct assignment for a tiny pilot), sign in as a cohort member and a non-member, and confirm Copilot appears only where licensed.