Credits usage for Copilot Studio Workflow with agents

I build Vaze. For a recurring workflow using the GitHub Copilot harness, Microsoft's documented billing unit is the environment and agent, not the individual maker or end user. I'd check the environment's prepaid allocation, tenant-pool draw and linked pay-as-you-go plan rather than the creator's personal credits.

Workflows consume Copilot Studio capacity for the actions they execute. Agent usage can also consume credits for model tokens, tools and the harness. So I wouldn't budget this as one fixed-price agent call: the work performed inside the run matters.

Microsoft's cost-management and workflow documentation:

https://learn.microsoft.com/en-us/power-platform/admin/manage-usage-github-copilot-harness

https://learn.microsoft.com/en-us/microsoft-copilot-studio/workflows-experience/flows-overview

Check the harness before applying this to your setup. A standard-harness agent flow or a Power Automate cloud flow can have different licensing rules. For the GitHub Copilot harness case, a small test run with non-sensitive JSON, followed by the environment and agent consumption reports, should help establish the actual cost before scheduling it regularly.