web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Copilot Studio / Insufficient Copilot C...
Copilot Studio
Suggested Answer

Insufficient Copilot Credits error in spite of having a Copilot Studio Pay-as-you-go license

(0) ShareShare
ReportReport
Posted on by 40
Hi, 
 
We have a Copilot Studio Pay-as-you-go license in our tenant. I am facing a warning for an 'agent flow', that says that the environment does not have sufficient credits. I am facing this issue for flows that have manual triggers like 'http', 'Manually trigger a flow' etc. It works for the 'agent calls a flow' trigger. 

Confirmations: 
1. The flow plan is changed to Copilot Studio
2. The flow contains AI prompts
3. Pay-as-you go license is active
 
 
Reference:
 

Error in Postman: 

{

    "error": {

        "code": "InsufficientMcsCredits",

        "message": "The environment 'env id' does not have sufficient Copilot Credits to run workflows.",

        "messageTemplate": "InsufficientMcsCredits"

    }

}

Categories:
I have the same question (0)
  • Suggested answer
    Beyond The Platforms Profile Picture
    219 on at
    This is expected behavior and not a licensing issue.
     
    Copilot Studio credits are only consumed when flows are executed within the Copilot runtime (e.g. using the “Agent calls a flow” trigger).
     
    When you use triggers like HTTP or manually trigger a flow, the flow is executed as a standard Power Automate flow, outside of the Copilot context. In this case, Copilot credits are not applied, and the system returns the "InsufficientMcsCredits" error.
     
    That’s why it works correctly with “Agent calls a flow” but not with other triggers.
     
    ✅ Recommended approach:
    Use “Agent calls a flow” for any flow that relies on AI prompts or generative capabilities.
     
    ✅ Alternative:
    Split your architecture:
    - One flow for external triggers (HTTP/manual)
    - One Copilot-triggered flow for AI processing
     
    This ensures that AI execution happens within the Copilot runtime where credits are available.
    Hope this helps!
    Paolo


    Did this solve your issue? → Accept as Solution
    👍 Partially helpful? → Click "Yes" on "Was this reply helpful?" or drop a Like!


    Want more tips on Power Platform & AI? Follow me here:

    🔗 LinkedIn: https://www.linkedin.com/in/paoloasnaghi/
    ▶️ YouTube: https://www.youtube.com/@BeyondThePlatforms
    📸 Instagram: https://www.instagram.com/beyond_the_platforms/
    🌐 Website: https://www.beyondtheplatforms.com/


     
  • CU20090407-0 Profile Picture
    40 on at
     
    Thank you for responding. 
     
    Could you recheck the same once as I have changed the flow plan to 'Copilot Studio' and the same was working since last few months with the same approach. This is a new issue. 
     
    If the prompts can only be used with 'Agent calls a flow' trigger; what is the alternative to use them for flows with other triggers. Which credits will be used for consumption in this scenario if not from the Copilot Studio license? 
  • Suggested answer
    Beyond The Platforms Profile Picture
    219 on at
    Thanks for the follow-up — a couple of clarifications that usually explain what you’re seeing.
     
    1) “It worked for months, now it doesn’t” (why it can look like a new issue)
    In Copilot Studio / Power Platform, AI capabilities (including prompts / AI tools) are tied to specific runtime/billing surfaces. If you recently changed the flow plan to “Copilot Studio”, the way AI usage is metered and/or the eligibility rules for certain AI features can change as the product evolves (especially for preview features). Copilot Studio and AI tools are billed/managed through Copilot Credits, and the platform has been actively updating these rules since the shift to Copilot Credits. See Copilot Studio licensing and billing details. 
     
    2) If prompts can only be used with “When an agent calls the flow”, what’s the alternative for other triggers?
    If your scenario starts from other triggers (SharePoint/Dataverse/Recurrence/etc.), the recommended alternative is:
    - Keep your flow with the required trigger (SharePoint/Dataverse/Recurrence).
    - Use AI via AI tools in Power Automate (prompt/model actions) where supported, OR
    - Call a Copilot Studio agent from the flow (so the agent does the reasoning and returns structured output), then continue the automation.
     
    Separately, Copilot Studio also supports event-triggered agent execution (agents acting autonomously on external events), which is designed for “non user-typed” triggers.
     
    So you typically have two robust patterns:
    A) Flow trigger → AI tool/prompt action in the flow (if available in your environment/region)
    B) Flow trigger → “execute/call agent” → agent uses prompts/knowledge/tools → flow continues with the agent result
     
    3) Which credits are used in these scenarios (if not from the Copilot Studio license)?
    Microsoft’s current model is:
    - AI tools / prompts in Copilot Studio agents and agent flows consume Copilot Credits. 
    - In Power Automate / Power Apps, prompt and model capabilities consume Copilot Credits when AI Builder credits aren’t available (or when AI Builder capacity is exceeded). 
    - For Copilot Studio agents, interactive employee-facing usage by users licensed with Microsoft 365 Copilot is “no charge” from the tenant Copilot Credits pool for the covered agent features (subject to Microsoft’s fair-use limits and the specific scenario).
     
    Practical takeaway:
    - If the flow/prompt runs outside an interactive “M365 Copilot licensed user” context (for example, a scheduled flow or a background trigger), it will typically draw from your organization’s Copilot Credits capacity (prepaid or pay-as-you-go), rather than being covered as “no charge” interactive usage. 
     
    Hope this helps!
    Paolo


    Did this solve your issue? → Accept as Solution
    👍 Partially helpful? → Click "Yes" on "Was this reply helpful?" or drop a Like!


    Want more tips on Power Platform & AI? Follow me here:

    🔗 LinkedIn: https://www.linkedin.com/in/paoloasnaghi/
    ▶️ YouTube: https://www.youtube.com/@BeyondThePlatforms
    📸 Instagram: https://www.instagram.com/beyond_the_platforms/
    🌐 Website: https://www.beyondtheplatforms.com/


     
  • WeiS Profile Picture
    2 on at
    @Beyond The Platforms Thanks for detailed explanation. I am having a similar situation. Attached screenshot is a Flow within Copilot Studio. We have Copilot payasyougo disabled, only paid M365 Copilot users can access copilot studio. The flow was working a few weeks ago. Today I noticed the same error @CU20090407-0 got (insufficient copilot credit). Do I understand correctly that this is because the flow is not technically trigger by a user, so must use copilot credit? (also wondering why it was working a month ago). Thanks.

  • Suggested answer
    Beyond The Platforms Profile Picture
    219 on at
    Yes, your understanding is correct.
     
    In your screenshot, the flow is triggered by “When an item is created” (SharePoint), which means it is a background/automated execution and not an interactive user-triggered Copilot session.
     
    Even though the flow is inside Copilot Studio and you are using “Execute Agent and wait”, the execution context still matters:
    - The flow is started by a system event (SharePoint trigger)
    - It is not directly initiated by a Microsoft 365 Copilot licensed user interaction
    - Therefore, the run is not considered a “no charge” interactive M365 Copilot scenario
     
    In this case, Copilot Studio requires Copilot Credits to be available at the environment level. Since Pay-as-you-go is disabled and no Copilot Credits capacity is assigned, the Flow checker reports “insufficient Copilot Credits”.
     
    So nothing is “broken” in your flow — it’s a change in enforcement and clarity of the execution model rather than a regression in functionality.

    Key takeaway:
    - Interactive agent runs initiated by an M365 Copilot licensed user can be “no charge”
    - Background or event-driven flows (like SharePoint-triggered flows calling an agent) require Copilot Credits capacity in the environment
    - To avoid the warning, you either need Copilot Credits (or PAYG) enabled for the environment, or redesign the scenario so the agent is invoked directly from an interactive user session
     
    This behavior is expected and by design.
     
    Hope this helps!
    Paolo


    Did this solve your issue? → Accept as Solution
    👍 Partially helpful? → Click "Yes" on "Was this reply helpful?" or drop a Like!


    Want more tips on Power Platform & AI? Follow me here:

    🔗 LinkedIn: https://www.linkedin.com/in/paoloasnaghi/
    ▶️ YouTube: https://www.youtube.com/@BeyondThePlatforms
    📸 Instagram: https://www.instagram.com/beyond_the_platforms/
    🌐 Website: https://www.beyondtheplatforms.com/


     
  • CU20090407-0 Profile Picture
    40 on at
     
    In the interaction with @WeiS, you've mentioned "Since Pay-as-you-go is disabled and no Copilot Credits capacity is assigned, the Flow checker reports “insufficient Copilot Credits” . But in my case, the Pay-as-you-go license is enabled and active. Still the same error seems to be showing up. I am not able to get a clear picture of the justification for this. Could you elaborate more on what the underlying issue is. 

    Points to address:
    - Why the error when Pay-as-you-go enabled?
    - Is this related to AI Builder credits ?
    - Is there any setting to be checked / limits set etc?

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Users!

Kudos to our 2025 Community Spotlight Honorees

Congratulations to our 2025 community superstars!

Congratulations to the April Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Copilot Studio

#1
Valantis Profile Picture

Valantis 455

#2
Vish WR Profile Picture

Vish WR 273

#3
Romain The Low-Code Bearded Bear Profile Picture

Romain The Low-Code... 202 Super User 2026 Season 1

Last 30 days Overall leaderboard