LowCodeStacks™
Sign in

Copilot Studio GitHub Copilot harness: stop the credit drain

The Copilot Studio GitHub Copilot harness bills credits while makers build, and new app environments draw on the tenant pool. What's on by default and how to cap it.

Governance & adminFix a problem8 min read

Checked against Microsoft Learn · 11 sourcesPosted by the Maker DeskHow we write guides

If your Copilot Credits are going faster than your agents' traffic explains, look at how agents and apps are now built. In Copilot Studio, agents and workflows started from the home page run on the GitHub Copilot harness. That harness bills by the credit, starting as soon as a maker begins building. Apps built in Copilot Studio run on the same harness, and each maker who builds one gets a personal developer environment that no setting can stop. Put those together with one more default, and a tenant's shared credits can drain while nothing is published.

This guide explains each part, what you can and can't turn off, and the order to close the gaps.

What the GitHub Copilot harness is

A harness is the engine between the model and your agent: it decides what to send the model, which tools to call and what to do with the results. Copilot Studio has four. The GitHub Copilot harness is the one built for long, multi-step work. The standard harness is the classic topic-based engine.

The name doesn't mean your data goes to GitHub. Microsoft says it's a Copilot Studio framework that shares technology with GitHub Copilot, and that customer data isn't sent to the GitHub Copilot service.

You choose the harness when you create an agent, and you can't move an agent between harnesses afterwards. To build on the standard harness, select Other ways to build on the Copilot Studio home page, or open the … menu at the bottom of the side bar and select Open classic experience.

It bills while makers are still building

With the standard harness, a Microsoft 365 Copilot licence covers a lot: standard agents used in Microsoft 365 channels by licensed people, plus the agent flows, workflows and prompts those agents run. The GitHub Copilot harness is different. Microsoft's cost table says harness agents are "billed for all usage", and that creation and runtime use credits "regardless of the user's license".

That includes the work before anything is live:

  • describing the agent in natural language,
  • chatting with it in the Preview tab,
  • generating and running evaluations,
  • upgrading a standard agent to the harness, which copies it and uses credits too.

Microsoft doesn't publish a price per action for the harness. It gives ranges by task complexity and an estimator, so plan from your own consumption report rather than a rate card. Developer and trial environments lost their free preview period on 1 September 2026.

Credits are charged to the environment the agent is in, not to the maker. That's why the environment settings below matter more than who has a licence.

Apps create developer environments you can't switch off

Copilot Studio can also build apps from a description (App (Preview) on the home page). Microsoft's documentation says app creation is on by default, runs on the GitHub Copilot harness, and bills building, previewing and testing in Copilot Credits.

How a new app ends up spending shared credits
  1. Step 3The new environment has no credit allocation
  2. Step 4Building draws on the tenant's shared credits

Each app goes into the maker's own personal developer environment. If they don't have one, it's created for them by environment routing for Copilot Managed Runtime, the service that hosts these apps. Microsoft is clear about the limits:

  • This routing is switched on in every tenant, and you can't change that.
  • Once it has started, its routing rule for Everyone can't be deleted or changed.
  • The tenant setting that blocks manual creation of developer environments doesn't stop it.
  • The environments start without Dataverse and are managed environments.

What you can turn off is the path that triggers it: app creation in Copilot Studio. Turning it off doesn't delete environments that already exist, and it doesn't turn the routing off.

New environments draw from the tenant pool

Copilot Credits you buy as prepaid packs sit in one tenant pool. In the Power Platform admin center, an environment can have its own allocation, and a setting called Draw from the available capacity in my tenant. For a Copilot Studio environment with no allocation, that setting is selected by default. Microsoft's own governance guidance warns that new environments "can appear with tenant-capacity draw turned on".

Microsoft doesn't describe the whole chain on one page. But read the two defaults together: a brand-new personal developer environment has no allocation, so building in it can spend the shared pool until you change the setting. The same pool also pays for Microsoft 365 experiences such as Cowork, so credits used in Copilot Studio leave less for them.

Stop the drain in this order

Read this first: environment capacity settings apply to every Copilot Studio workload in that environment, including standard agents, agent flows and prompts. A hard cap on a shared environment can stop production agents, so classify environments before you change them.

  1. See what's spending. In the Power Platform admin center, go to Licensing > Copilot Studio. Review consumption by environment and by agent, and download the consumption report. Sort by Billed credits and group by agent and Product / AI feature.
  2. Find the harness agents. Go to Manage > Copilot Studio and filter the Harness column to GitHub Copilot. Only those agents use consumption billing for everything.
  3. Find the app environments. Go to Manage > Inventory, set Item type to Copilot Managed Runtime, and add the Environment and Environment Group columns. Don't delete an environment just because you didn't expect it: check its owner, apps and dependencies first.
  4. Decide on app creation. In the Microsoft 365 admin center, go to Apps > Overview > Set up app creation spaces to turn Copilot Studio app creation off or limit it to Microsoft Entra security groups. You need the Global Administrator or Power Platform Administrator role. Open Copilot Studio tabs can keep the old setting for up to 15 minutes.
  5. Close the tenant pool. Go to Licensing > Copilot Studio > Manage Copilot Credits, select the environment, enter an allocation, clear Draw from the available capacity in my tenant under Capacity overages, and select Save. An environment with no allocation and the draw cleared can't use prepaid credits at all.
  6. Make it stick for a group. In Manage > Environment groups, open the group's Rules and use Cost controls - Draw from tenant credit pool, then publish the rules. A published rule makes the environment setting read-only, so it can't drift back.
  7. Check pay-as-you-go. Clearing the tenant draw doesn't stop spending through a linked pay-as-you-go billing plan. Unlink plans from exploration environments. Azure budgets only send alerts; they don't stop usage.
  8. Cap each agent. Go to Licensing > Copilot Studio > Manage Agents, select the agent and Set limit. Enter a monthly limit and a notification threshold, and turn on Stop usage. There's no tenant-wide default limit, so new agents need a regular check.

Do

Give exploration environments a small fixed allocation, with the tenant draw off and no pay-as-you-go link. Makers can still try the harness, and the worst case is known in advance.

Don't

Don't put a hard cap on a shared production environment without checking every agent and flow in it first. When an environment runs out of credits, makers lose natural-language authoring, preview and evaluations, and agents can stop answering.

Tell your makers

Most of this spending starts with someone exploring, not with a live agent. Tell makers three things: building on the GitHub Copilot harness costs credits from the first prompt; Other ways to build uses the standard harness, which their Microsoft 365 Copilot licence covers in Microsoft 365 channels; and who to ask when they need more capacity. Microsoft recommends pairing tight limits with a clear request path, so caps don't simply block good work.

For what a credit pays for across Microsoft 365 and Copilot Studio, see Copilot Credits explained.

Sources

Did this fix it?

Comments

No comments yet. Share what worked for you.

Sign in to comment. Comments show under a display name you choose, never your email.