This warning is expected depending on *how* the flow is executed and how Copilot Credits capacity is allocated to the environment.
What the Flow checker warning means
“The environment has insufficient copilot credits” indicates that the environment where the flow runs does not currently have enough Copilot Studio credit capacity assigned/available to execute AI features (prompts/AI tools/agent flow actions). Copilot Credits are required for AI tools and agent flow scenarios, and capacity must be available (and allocated) at the environment level.
Why you see this even with an M365 Copilot license
The “No charge” entries in the Copilot Credits billing rates table apply only to specific “Microsoft 365 Copilot licensed user” scenarios (interactive usage in the covered context). In contrast, flows can run in contexts that are NOT considered “M365 Copilot licensed user interactive usage”, such as:
- background/automated triggers (recurrence, Dataverse trigger, HTTP trigger, etc.)
- runs under a service account / connection owner context
- runs initiated outside the Microsoft 365 Copilot licensed user context
In those cases, the platform still requires Copilot Credits capacity to be available in the environment, even if you personally have an M365 Copilot license. The Flow checker warning is essentially telling you: “if this flow runs outside the covered ‘no charge’ scenario, it will require environment Copilot Credits capacity.”
This also matches what the checker message states: runs from agents by M365 Copilot users and testing may not consume credits, but other executions can require Copilot Credits.
What changed / why it worked before
Copilot Credits and enforcement have been evolving since the switch from “messages” to “Copilot Credits” as the billing currency. Warnings may appear after licensing/capacity enforcement updates, environment changes, or if credit allocation/overage settings changed.
How to fix / what to check
1) Check Copilot Studio credit capacity allocation for the environment
In Power Platform admin center:
Licensing → Products → Copilot Studio → (Summary / Capacity) and verify that Copilot Credits are assigned to the environment where the flow runs, and that you have remaining capacity (or PAYG enabled).
2) Confirm the execution context of the flow
If the flow can be triggered in non-interactive ways (scheduled, event-based, HTTP), expect it to require Copilot Credits capacity. If you want “no charge” behavior, ensure the flow is executed from an agent interaction in the supported M365 Copilot licensed user context (and not as a background automation).
3) Enable a safety net (optional)
If you don’t want runs to fail when prepaid capacity is depleted, configure pay-as-you-go or adjust overage handling at the environment level.
Summary
- The warning is about environment Copilot Credits capacity availability (and allocation), not your personal M365 Copilot license.
- “No charge” applies only in specific licensed-user interactive scenarios; automated/background flow runs can still require Copilot Credits capacity in the environment.
- Fix is to ensure Copilot Credits capacity is assigned to that environment (or PAYG is enabled) and to validate how the flow is triggered/executed.
