This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Caldova's pilot users are covered by two spending policies for Copilot Cowork. The pilot policy has a 500-credit per-user limit. The default policy has no per-user limit and an overall monthly limit of 400 credits. Which policy applies to these users?
The default policy, because it covers the whole organization.
The pilot policy, because its 500-credit per-user limit is higher than the default policy's 400-credit overall limit used for comparison.
Both policies, combined into one effective limit.
An admin holds only the AI Administrator role. Can they create a spending policy for a new pilot group?
Yes, AI Administrators can create and edit spending policies.
No, creating a spending policy requires the Global Administrator or Billing Administrator role.
No, they must also hold the License Administrator role.
A user's Copilot Cowork task is running when the user reaches their monthly credit limit. What happens?
The task stops immediately until additional capacity is approved.
The task finishes, but the user can't start another task until the limit resets or an admin grants more capacity.
The task finishes, and the user can start more tasks because the limit only triggers an alert.
What's the main purpose of the Agent 365 agent registry?
To replace Cost Management as the place to set spending policies.
To provide admins with a unified inventory of agents, including ownership, lifecycle actions, and status, across Microsoft and non-Microsoft agents.
To estimate how many Copilot Credits a new pilot will consume.
To set per-user credit caps for Copilot Cowork.
You must answer all questions before checking your work.
Was this page helpful?
Need help with this topic?
Want to try using Ask Learn to clarify or guide you through this topic?