Credit Reporting AI Builder vs Copilot Credits

(1) Share

Report

Posted on by CU21081422-14

Is anyone else having a heck of a time trying to figure out where credits are burned throughout the Power Platform right now? I understand AI Builder credits are going away in November but there are some processes (flows with AI Prompts/Models) that are supposed to start consuming Copilot Credits when the AI Builder credits run out but that does not seem to be the case. Also, the AI Builder reports are sometimes 5-7 days behind. Everything seems very inconsistent

Categories:

Bot administration

I have the same question (0)

All responses (3)

Answers (0)

Sort by

Suggested answer

Robu1 1,709 Super User 2026 Season 2 on at

Like
a
(0)

Report
Copy link

Link copied!
Hi CU21081422-14,

Thank you for choosing Microsoft Community.

Thanks for raising this — you’re definitely not the only one seeing inconsistent behaviour right now. Microsoft is in the middle of shifting AI Builder metering over to Copilot Credits, and the transition isn’t fully complete across all tenants.

A few things we’re seeing broadly:

AI Builder usage reports are delayed (often 5–10 days) because they’re still running on the legacy metering pipeline.

Flows using AI Prompts/Models don’t always fall back to Copilot Credits when AI Builder credits hit zero — this fallback is only partially enabled in some regions.

Copilot Credit reporting is real‑time, but only for Copilot‑native features. AI Builder actions inside flows aren’t consistently mapped yet.

During this hybrid period, some usage simply doesn’t appear in either report, even though the runs are successful.

Microsoft has confirmed that a unified AI usage dashboard is rolling out between now and November, which should clean up the reporting gaps and fully align AI Builder → Copilot metering.

Resource: End of AI Builder credits | Microsoft Learn

I hope this helps resolve the issue! If you need more specific guidance, feel free to ask.

🏷️ Please tag me @Robu1 if you still have any queries related to the solution or issue persists.

✅ Please click Accept as solution if my post helped you solve your issue and help others who will face the similar issue in future. ❤️ Please consider giving it a Like, If the approach was useful in other ways.

Happy to help

Robu 1👩‍💻

Was this reply helpful? Yes No
Suggested answer

11manish 3,859 Super User 2026 Season 2 on at

Like
a
(0)

Report
Copy link

Link copied!
Yes — what you're seeing is not necessarily an inconsistency in your flows. Microsoft has explicitly documented some delays and a transitional licensing model that can make AI Builder/Copilot credit consumption look confusing.

For production environments, I would not use the AI Builder report as a real-time billing/consumption monitor.

Instead, establish a small governance process:

Identify every flow/app using AI Builder actions or AI prompts/models.

Record which environment each workload runs in.

Track AI Builder capacity allocated to each environment.

Monitor AI Builder consumption reports.

Monitor Copilot Credit consumption separately.

Plan the required Copilot Credits before November 1, 2026.

Don't assume that AI Builder credits will automatically convert to Copilot Credits — they don't.

So, yes, your frustration is understandable. The combination of the November 2026 licensing transition, two different credit currencies, environment allocation, and delayed consumption calculations makes this particularly difficult to troubleshoot during this transition period.

Refer:

https://learn.microsoft.com/en-us/ai-builder/endofaibcredits

Was this reply helpful? Yes No
Suggested answer

Dua Sadiq 4 on at

Like
a
(0)

Report
Copy link

Link copied!
The fallback to Copilot Credits only kicks in based on a computed consumption number, and that computation can lag 5+ days. So even when your AI Builder credits are gone, the system may still think you have some left and won't switch over yet.

Blocking/fallback triggers at 125% of your allocation, not 100% so there's a grace band where nothing seems to change.

Most important: the fallback only works if you actually have Copilot Credits allocated to that environment (or tenant). It's not auto-purchase. No Copilot Credits = nothing to fall back to, so it just blocks.

The 5–7 day report lag is expected enforcement and reporting both run off that same delayed computation.

If you allocate Copilot Credits to the environment now, the behavior gets a lot more predictable.

https://github.com/MicrosoftDocs/SupportArticles-docs/blob/main/support/power-platform/ai-builder/power-automate/all-ai-builder-credits-have-been-consumed.md

If this helped please mark it as verified!

Thank you in advance

Was this reply helpful? Yes No