API for user-level Copilot Credit consumption

(0) Share

Report

Posted on by PD-04080642-0

Hi Microsoft Team,

We are building a custom integration with Microsoft Copilot Studio where the Copilot agent is embedded in our own member portal.

We need to enforce a per-user Copilot Credit/usage limit from our custom application.

Could you please clarify:

Is there any API, Power Platform API, Dataverse table, or other supported method to retrieve Copilot Credit consumption at the individual user level?
Can we get details such as:
- User ID / email
- Copilot Credits consumed by that user
- Agent used
- Date/time of consumption
- Remaining/available credits or usage
Is the new usage-based billing user-level consumption data available programmatically through an API?
If there is no API, is there any recommended Microsoft-supported approach to retrieve this information so that our custom backend can track usage and enforce a limit per user?
Can the session data shown under Copilot Studio Analytics → Sessions be correlated with Copilot Credit consumption for a specific user?

Our requirement is to identify the user from our custom portal and prevent or restrict further chatbot usage once that user's configured usage limit is reached.

We are not looking only for admin-level/agent-level total consumption; we specifically need user-level consumption that can be accessed programmatically.

Any guidance on the supported API, Dataverse tables, or recommended architecture would be greatly appreciated.

Thanks!

Categories:

Bot analytics

All responses (3)

Answers (0)

Sort by

Suggested answer

Daniyal Khaleel 31 on at

Like
a
(0)

Report
Copy link

Link copied!

Yes. Based on the current Microsoft documentation (2026), the answer is:
Short answer
Microsoft does not currently provide a supported public API/Dataverse table that gives you the actual Copilot Studio Credit consumption per individual end user in real time.
Copilot Studio exposes billing consumption primarily at the agent/environment/tenant capacity level, while conversation/session information can be associated with users separately. Microsoft explicitly states that Copilot Studio Analytics provides billed Copilot Credits for an agent, and the data can take several hours to update.
So your requirement:
"User A has consumed 73 credits, User B has consumed 21 credits, and block User A when they reach 100"
is not currently something you can reliably implement using Microsoft's Copilot Credit meter directly.
Microsoft has introduced more detailed usage-based billing reporting. The Microsoft 365 admin center now has a Consumption view that can show users, credit limits, credit usage, last activity, session count, and usage against limits for certain Microsoft 365 Copilot usage-based billing scenarios.
However, don't confuse that with Copilot Studio's Copilot Credit meter.
Suggested answer

Sayali-MSFT Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

Hello PD-04080642-0,

At present, Microsoft does not provide a supported public API or Dataverse table that exposes Copilot Studio Copilot Credit consumption at the individual end-user level with details such as user, agent, timestamp, and credits consumed. Copilot Studio billing analytics are primarily available at the agent and tenant level and may be delayed by several hours. While session analytics can identify user interactions, they cannot be directly correlated to exact Copilot Credit consumption per session or user. For scenarios requiring per-user usage limits, the recommended approach is to implement custom tracking in the application layer by recording user requests and enforcing quotas before sending requests to Copilot Studio.
Reference Document:
1. View agent's billing consumption - Microsoft Copilot Studio | Microsoft Learn
2. Billing rates and management - Microsoft Copilot Studio | Microsoft Learn
Suggested answer

11manish 4,802 Super User 2026 Season 2 on at

Like
a
(0)

Report
Copy link

Link copied!

There is currently no documented Microsoft API that I would recommend for real-time, per-user Copilot Credit enforcement in a custom application.

Microsoft's newer Usage-Based Billing experience does provide user-level consumption reporting, which is useful for administration and cost analysis, but your

custom portal should not depend on that data for real-time quota enforcement.

For your requirement, the most robust architecture is:

Custom portal identity → your own per-user quota service → Copilot Studio

with Microsoft's Usage-Based Billing / Copilot Studio analytics used separately for reconciliation and reporting.

And I would treat the v0.1-alpha licensing endpoint you found as an unsupported/internal API, not as a production integration contract.

Refer:
https://learn.microsoft.com/ka-ge/microsoft-copilot-studio/requirements-messages-management