A county assessor's office asks whether creating an agent is part of basic Copilot and agent administration. Which answer is correct?

Creating an agent for a municipal workload is a basic administrative or maker task within AB-900 scope. The county assessor’s office should treat agent creation as an expected Copilot and agent administration capability: makers or admins can create agents for municipal workloads under the product’s administration model rather than assuming that building a declarative agent for a municipal workload is configured in Azure OpenAI deployment settings. That recognition is the direct answer to whether creation is part of basic administration.

Claiming that building a declarative agent for a municipal workload is configured in Azure OpenAI deployment settings fails by concept—AB-900 covers real Microsoft 365 Copilot and agent administration where agent creation is a basic maker or admin task, not Azure OpenAI deployment configuration. Stating that creating an agent for a municipal workload is completed in Entra ID access reviews for owners fails because maker/admin agent creation is part of the fundamentals story; Entra ID access reviews for owners review existing access and do not create agents. Claiming that reviewing agent usage analytics for a municipal workload is done in Entra ID sign-in audit logs fails by location; agent usage analytics are reviewed in the admin center experiences, while Entra ID sign-in audit logs record authentication events and do not show agent usage.

Exam caveat: Know that “create an agent” sits inside AB-900 Domain 3 Copilot and agent administration. Do not treat Azure OpenAI deployment settings as the creation location, treat Entra ID access reviews for owners as the creation path, or mistake Entra ID sign-in audit logs for agent usage analytics review. Creation still sits alongside access configuration, grounding, and approval—creation alone is not uncontrolled production release.

Operational check: Confirm which assessor-office roles are allowed to create agents under municipal policy, have a maker create a non-production pilot agent for a bounded assessor workload, apply access and grounding controls, and route toward approval before staff or residents rely on it—proving creation is in-scope without skipping governance.