Adopting the GitHub Copilot Harness: Cost Control and Governance
Diesen Beitrag auf Deutsch lesen
How to find GitHub Copilot harness agents in a tenant and cap their Copilot Credit consumption at the environment and agent level.
TL;DR
GitHub Copilot harness agents draw from the same Copilot Credit pool as regular agents but are easy to miss in an audit — find them via the isCLIAgent property in Power Platform inventory, then split maker-development environments from funded production ones. Environment-level controls (Admin Center > Copilot Studio > Manage Copilot Credits) set allocation, tenant-pool access and pay-as-you-go; agent-level limits can cap an individual agent at, for example, 1,000 credits with an 80% alert.
Original by Lewis Baybutt, on The Custom Engine. Read the original
This is our own summary, not a republication or full translation.
Governance takeaway
- Admins/CoE: run the isCLIAgent inventory check now — harness agents draw from the same credit pool as regular agents but don’t surface in a normal agent audit.
- Security/Compliance: treat that audit gap as the finding itself — a cost review that doesn’t separately query for isCLIAgent misses these agents entirely, not just undercounts them.
- Leadership/Business: fund a notification path to agent owners, not just admins, since the built-in 80% alert reaching only admins means a production agent can quietly run past its own limit while the environment keeps paying.