Answered

[PAYG] Power Automate Flow Costs in Copilot

(2) Share

Report

Posted on by FREDO7810

Hello everyone 👋

I’m posting here because I can’t seem to find clear information on Microsoft’s website regarding how Power Automate flows work inside a Copilot agent within a PAYG (Pay-As-You-Go) environment.

Here’s my situation:

I have both a Copilot license and a Power Automate Premium license.

However, I’m still seeing Power Automate consumption/billing, even when my flows are not using any premium connectors.

My understanding is that once an environment is configured as PAYG, flows become usage-based billed, and standard licenses no longer cover flow execution. However, I haven’t been able to find any truly clear documentation confirming this.

Would anyone happen to have:

official documentation clearly explaining the pricing/cost model;

details about which scenarios are billed vs. not billed;

or any real-world feedback regarding Power Automate costs when used within Copilot?

Any help or clarification would be greatly appreciated 🙏

Thanks in advance!

Categories:

Calling actions from Copilot Studio

Bot analytics

I have the same question (0)

All responses (4)

Answers (0)

Sort by

Suggested answer

Valantis 5,579 on at

Like (1)

Report
Copy link

Link copied!

Hi @FREDO7810,

Your understanding is correct and here's what Microsoft docs confirm.

When flows run inside a Copilot Studio agent (as Agent Flows), they consume Copilot Credits, not Power Automate license entitlements. This is separate from your Power Automate Premium license. Agent flow actions are billed per action executed regardless of connector type.

Your Power Automate Premium license covers standalone flows triggered outside of an agent. When that same flow runs as an agent flow (called from within a Copilot Studio agent), it switches to Copilot Credits billing.

What's billed vs not billed:
- Agent flows called from within a Copilot Studio agent: billed in Copilot Credits
- Test runs from the flow designer or agent test chat: not billed
- M365 Copilot licensed users: not affected by capacity blocks (Microsoft docs confirm this)
- Standard standalone flows with Power Automate Premium license: covered by your license, not billed additionally

In a PAYG environment, the Copilot Credits meter picks up any agent flow execution that exceeds your prepaid capacity, billing to your Azure subscription.

Official reference: https://learn.microsoft.com/en-us/microsoft-copilot-studio/requirements-messages-management

Agent flows billing: https://learn.microsoft.com/en-us/microsoft-copilot-studio/flows-overview

Best regards,

Valantis

✅ If this helped solve your issue, please Accept as Solution so others can find it quickly.

❤️ If it didn’t fully solve it but was still useful, please click “Yes” on “Was this reply helpful?” or leave a Like :).

🏷️ For follow-ups @Valantis.

📝 https://valantisond365.com/

💼 LinkedIn

▶️ YouTube

Was this reply helpful? Yes No
FREDO7810 12 on at

Like (1)

Report
Copy link

Link copied!

Hi Valantis,

Thank you for your reply and for taking the time to clarify this topic 🙏

I really appreciate your help!

Was this reply helpful? Yes No
Suggested answer

Haque 3,286 on at

Like (1)

Report
Copy link

Link copied!
Hi @FREDO7810,

As you have both a Copilot license and a Power Automate Premium license - let's first see the how copilot bills and then scenraio billed and not billed.

As copilot studio bills are credit based, let's first see an approximation: Here is a sample table illustrating approximate Copilot Credits consumption and billing for a user over a month, covering various scenarios discussed:

Total Estimated Credits Consumed: 64,500 credits

Notes:

This table assumes unified credit rates across GPT and Anthropic models.

Reasoning or premium AI tools add additional credit costs on top of base generative answer credits.

Actual consumption varies based on agent design, usage patterns, and tenant policies.

Bring-your-own-model usage is billed separately and not included here.

Details About Which Scenarios Are Billed vs. Not Billed:

References:

1. Billing rates and management

2. Power Automate introduces pay-as-you-go pricing

3. Pay-as-you-go plan

I am sure some clues I tried to give. If these clues help to resolve the issue brought you by here, please don't forget to check the box Does this answer your question? At the same time, I am pretty sure you have liked the response!

Was this reply helpful? Yes No
Suggested answer

11manish 2,467 on at

Like (0)

Report
Copy link

Link copied!

Based on what you've described, I would first confirm which specific meter is generating the Azure charges before assuming the Power Automate flow itself is

being billed.

In PAYG environments, costs can originate from Dataverse operations, Copilot usage, AI Builder consumption, or flow executions, and the billing reports do not

always make that distinction obvious at first glance.

If you can identify the exact meter/resource being charged in the Azure billing report, it becomes much easier to determine whether the behavior is expected

licensing behavior or an unexpected consumption pattern.

Was this reply helpful? Yes No