Hello Daphne Vaia Sioka ,
Testing an unpublished Copilot Studio agent can consume credits because credit usage is based on the actions the agent performs—such as generating responses, calling connectors, sending emails, or running workflows—rather than its publication status. Once the agent is published, direct user-initiated interactions inside Microsoft 365 (for example, in Teams) by users with a Microsoft 365 Copilot license are generally included and do not consume additional credits, even when actions or connectors are involved.
In contrast, autonomous or unattended executions—such as scheduled runs, Power Automate triggers, or background tasks—always consume credits regardless of licensing. The key distinction is that interactive, user-driven usage is included, while agent-driven, autonomous usage is metered.
Q1 — Does testing an unpublished agent consume credits?
Yes. Testing actions (including connector calls and sending emails) can consume Copilot Credits, because usage is measured by actions performed, not publication status.
https://microsoft.github.io/agent-academy/recruit/12-understanding-licensing/
Q2 — After publication, do user‑initiated interactions inside M365 consume credits?
If the user has a Microsoft 365 Copilot license → No, these actions are included.
If users do not have M365 Copilot licenses, credit consumption follows the regular Copilot Studio model.
Q3 — Are credits only consumed for autonomous runs?
No. Interactive usage may consume credits depending on user licensing:
- M365 Copilot users → interactive usage is included
- Non‑Copilot users → interactive usage consumes credits
- Autonomous runs → always consume credits