A housing authority wants to grant Copilot to library staff using group-based licensing concepts. Which approach is sound?

A housing authority granting Copilot to library staff should assign Copilot licenses through group-based licensing to the library staff group rather than relying only on one-off exceptions. Group-based licensing ties entitlement to membership so joiner/mover/leaver processes stay consistent, audits are clearer, and scale does not depend on remembering individual exceptions.

Assigning Copilot licenses through group-based licensing to the library staff distribution list for automated entitlement fails because distribution lists are not valid group-based licensing targets, and automated entitlement requires a Microsoft 365 or security group containing users. Assigning Copilot licenses through group-based licensing to the library staff device group containing device objects fails because device-based groups don't satisfy user-based Copilot licensing, and Copilot entitlement follows people, not devices. Assigning Copilot licenses through Entra administrative units containing library staff for automatic license inheritance fails because administrative units delegate administrative scope and do not inherit or assign Copilot licenses by themselves.

Exam caveat: Group-based licensing requires sound group hygiene (who owns the group, nested groups, and sync from HR). Fundamentals items test the pattern, not every Azure AD group quirk.

Operational check: Place library staff in a dedicated M365 or security group, enable group-based Copilot licensing to that group, add a test user, wait for assignment propagation, and confirm Copilot availability for staff rather than the library staff distribution list.