Ownership Change and Modifying the Quota Limit

(2) Share

Report

Posted on by Sidhant_22

Hi folks,
I had a MCP server that I had worked on which I wanted to make it accessible to the wider audience (within my organization) so then I created a custom connector (Power Apps connector) registered it and created the respective connection and then in Co-Pilot studio create a new agent and added the custom tool (established the connection). In the test mode it work as intended and then the agent was published so that it can be easily accessed. After the gent was published I noticed few issues:

1: A message (from the agent): This agent is currently unavailable. It has reached its usage limit. Please try again later
(Right now it seems the agent is published in default environment of our org).

2: The next question was how can I transfer the ownership of the agent to some other individual, right now since I have created the agent I am the owner. I wanted to transfer the ownership to an individual who already is been added as an 'Editor' (shared the agent) and since he has the publishing access (the right to publish the agent), I am thinking of transferring the control. To add to this now if we want to keep a track of the usage and the quota been assigned to the agent and to avoid running into any issues like Usage limit reached how to approach this.

At the moment to over come the usage limit issue (the first issue) what I am doing is I simply one query at a time (i.e. fire a prompt then get a response, then wait for 5-6 min and then run another query get a response) this isn't ideal .So if anyone can share their inputs for the same it will help.

Note: I also tried to check the licensing under Power platform admin center but since I do not have the appropriate permission was not able to access them

Categories:

Building Copilot Studio chatbots in Microsoft Teams

I have the same question (0)

All responses (3)

Answers (0)

Suggested answer

Sunil Kumar Pashikanti 1,353 Moderator on at

Like (1)

Report
Copy link

Link copied!

Hi @Sidhant_22,

This is expected Copilot Studio behavior, not an agent or connector issue.

The message “This agent is currently unavailable. It has reached its usage limit” means the Dataverse environment hosting the agent has hit Copilot Studio quotas (very common in default/trial environments). Quotas are enforced per environment, not per agent.

Ownership cannot be transferred by an editor, only a Power Platform/Tenant admin can reassign agent ownership.

To fix:

Move/recreate the agent in a sandbox or production environment
Enable Pay‑As‑You‑Go or prepaid Copilot capacity
Monitor usage in Power Platform Admin Center

Waiting between prompts works because of throttling, but it isn’t a real solution.

This is not a defect, but a licensing and capacity governance issue.

Copilot Studio agent hits usage limit after 1 request in new environment

✅ If this answer helped resolve your issue, please mark it as Accepted so it can help others with the same problem.
👍 Feel free to Like the post if you found it useful.

Was this reply helpful? Yes No
Sidhant_22 36 on at

Like (0)

Report
Copy link

Link copied!

Hi @Sunil Kumar Pashikanti,
Thanks for the response and sharing the relevant thread which demonstrated the high level steps to set the capacity. I had quick follow up questions:
Does the ownership has any role with the quota part. Assume the user who is the editor in my agent has the privileges to publish the agent (and may have a premium workspace) so if they end up creating the agent and the end users start using will this quota limit (agent unavailable at the moment) be resolved (even if its deployed in default environment) or the ownership of the agent has nothing to do with this, it dependent on the environment wherein the agent is published.

Regards,
Sidhant

Was this reply helpful? Yes No
Sunil Kumar Pashikanti 1,353 Moderator on at

Like (1)

Report
Copy link

Link copied!

Hi @Sidhant_22,

Ownership, editor privileges, or having a premium workspace do NOT affect Copilot Studio usage quotas.
The quota is entirely determined by the Dataverse environment where the agent is published.

Quotas are:

Enforced per environment
Shared across all Copilot agents in that environment

That’s why the error says: “This agent is currently unavailable. It has reached its usage limit.”

It’s not the agent, it’s the environment.

So even if:

The agent creator/editor has premium licenses
The agent owner has full publish rights
The agent works perfectly during authoring/testing

If the agent is published in the Default environment (or a trial enviromnent) without sufficient Copilot Studio capacity, end users will still hit the “agent unavailable / usage limit reached” error.

1) Does the ownership has any role with the quota part?

No, Agent ownership only controls:

Who can edit
Who can publish
Who can manage the agent

It does not control:

Runtime message limits
Session limits
Throughput
Availability to end users

Once published, the agent draws usage from the environment’s capacity, not the owner’s license.

2) Assume the user who is the editor in my agent has the privileges to publish the agent (and may have a premium workspace) so if they end up creating the agent and the end users start using will this quota limit (agent unavailable at the moment) be resolved (even if its deployed in default environment) or the ownership of the agent has nothing to do with this, it dependent on the environment wherein the agent is published?

No, not for end-user usage.
Premium licenses (for the maker/editor):

Allow agent creation
Unlock features
Allow publishing

But:

End-user runtime consumption ignores the editor’s license
Quotas are not pooled across user licenses

Think of it like this:

Licenses let you build the agent.
Capacity lets users talk to it.

Finally for your scenario:
If a user who is an editor creates and publishes the agent in the Default environment, will usage limits be resolved because of their privileges?

Answer is No.
If the agent is:

Published in the Default environment
And no Copilot Studio capacity is assigned

Then:

End users will still hit quota limits
Regardless of who owns or created the agent

✅ If this answer helped resolve your issue, please mark it as Accepted so it can help others with the same problem.
👍 Feel free to Like the post if you found it useful.

Was this reply helpful? Yes No