PAYG Billing Policy not triggering in new Environment Usage limit reached after one message

(4) Share

Report

Posted on by UL-09031305-0

Hey Community,

we are facing an issue with our PAYG billing policy in Copilot Studio and cannot figure out what is going wrong. Maybe someone has experienced the same or has a tip.

Situation:
We created a new Managed Environment and linked it to our existing PAYG Billing Policy. In another environment connected to the same Billing Policy everything works fine. The agent was created after the environment was set up and has been republished multiple times. The Teams channel was removed and re-added after the PAYG setup.

The problem:
Users without a Copilot license get the message "Usage limit reached" after sending just one message. In the Azure Portal, Cost Management shows 0 EUR in consumption, which means PAYG does not seem to be triggering at all.

What we have already checked:
- Billing Policy status is Active
- Both environments are listed in the same Billing Policy
- Azure Subscription is active, no spending limit set
- Agent has been republished
- Teams channel was removed and re-added
- Security roles have been reviewed

Has anyone experienced the same issue or has an idea what might be causing this? We already have an open support case but have not received a response yet.

Thank you!

Categories:

Bot administration

General topics

I have the same question (0)

All responses (2)

Answers (0)

Sort by

ZS-11030959-0 3 on at

Like
a
(0)

Report
Copy link

Link copied!

The situation is the same at our company as well.

Was this reply helpful? Yes No
Suggested answer

Valantis 6,735 on at

Like
a
(1)

Report
Copy link

Link copied!
Hi @UL-09031305-0,

What you’re seeing usually means the billing policy exists, but the Copilot service itself isn’t fully connected to it. In Microsoft’s docs, creating a PAYG billing policy is not enough on its own — it must also be connected to the Copilot service in Microsoft 365 admin center > Copilot > Billing & usage > Pay-as-you-go services. Please verify the policy is connected to the service your users are actually using. ()

Please also check whether the agent has a monthly consumption limit / hard stop configured. Microsoft states these limits apply even when the environment uses PAYG, so a very low agent cap can cause the “usage limit reached” message almost immediately.

Also, the 0 EUR in Azure Cost Management does not prove PAYG isn’t working. Microsoft says Azure cost data can take up to 24 hours to appear, and the Microsoft 365 spending view can take up to 4 hours. ()

One more point: agents created in standalone Copilot Studio and deployed to the Teams channel do consume Copilot Credits, so this should meter once the billing connection is correct. ()

So the main checks are:

Confirm the billing policy is connected under Copilot > Billing & usage > Pay-as-you-go services

Confirm the agent does not have a low monthly limit

Wait for billing visibility latency before using Azure cost as proof

If all of that is correct, open a case, because the next likely cause is a backend metering issue rather than a maker-side configuration problem.

Was this reply helpful? Yes No