A public library system sees Copilot unavailable for some clerks and wonders whether to blame feature toggles first. What should admins verify early?

When Copilot is unavailable for some public-library clerks, administrators should verify Copilot license assignment for the affected clerks early—before blaming only feature enablement. Missing licenses are a common root cause that looks like “Copilot is broken” or “features are off” when the account simply was never entitled. Checking assignment first narrows troubleshooting and avoids unnecessary feature-policy churn.

Whether Copilot for Sales seats are enabled for affected clerks before blaming only feature enablement is a sales-specific entitlement, not the core Copilot license check for library clerk availability. Whether Copilot Studio maker rights are granted to affected clerks before blaming only feature enablement is a builder permission for creating custom copilots, not a licensing prerequisite for using Copilot. Whether admin consent for Copilot apps is granted to affected clerks before blaming only feature enablement is an app deployment permission step that comes after entitlement and does not prove the clerk was licensed.

Exam caveat: After licenses check out, then inspect feature toggles, app deployment, and service health. AB-900 expects conceptual license-assignment awareness in Domain 3 troubleshooting narratives.

Operational check: For each affected clerk, confirm Copilot license state in admin center or PowerShell/Graph licensing views, assign if missing, have the clerk sign out/in, and only then evaluate feature enablement if Copilot remains unavailable.