City council support staff see low Copilot adoption in public works after licenses were assigned. What should they do next?

When city council support staff see low Copilot adoption in public works after licenses were assigned, they should use adoption insights to plan targeted enablement help rather than assuming licenses alone create usage. Fundamentals treat assignment as necessary but not sufficient: low adoption is a signal to coach, train, share vetted prompts, and remove friction for that municipal department. Enablement guided by insights preserves the investment while addressing the real barrier—people not yet working Copilot into daily public works tasks.

Reassigning available Copilot licenses within public works to broaden coverage and support adoption across support teams fails by concept: moving seats around does not create usage, and broadening coverage without targeted enablement spreads licenses thinner rather than improving actual adoption. Reviewing license assignment status in the Microsoft 365 admin center to verify public works Copilot provisioning completed fails as the next step because licenses are already assigned; the issue is usage after assignment, not missing entitlements, so auditing provisioning does not close the adoption gap. Organizing Copilot prompt training sessions for public works teams to build skills aligned to assumed daily workflows fails because it skips adoption insights; training on assumed workflows is not targeted enablement for public works, low adoption in one department calls for insight-guided coaching on validated use cases, not prompt sessions built on assumptions.

Exam caveat: AB-900 Domain 3 frames adoption insights as input to improve usage, not as a trigger for license reassignment or assumed-workflow training. Do not confuse “low adoption” with “reassign available licenses to broaden coverage,” and do not “fix” it with prompt training on assumed workflows instead of targeted public works enablement.

Operational check: Confirm public works licenses are assigned to the right roles, review Copilot adoption insights for that department, interview a few supervisors about blockers (training, device, policy fear, unclear use cases), run a short targeted enablement sprint with approved prompts for common public works documents, then recheck adoption metrics before any license-rightsizing discussion with council support leadership.