Summary
- Billing for existing Copilot Studio agents and workflows built with the GitHub Copilot harness will begin consuming Copilot Credits under the usage-based billing model.
- The change applies only to GitHub Copilot harness agents and workflows created before the cutoff, including those in Dev or Trial environments.
- Maker AI authoring activity and runtime execution will both count toward credit consumption.
- Standard harness and Copilot Chat harness agents are not affected.
- Administrators should review historical usage and identify active GitHub Copilot harness assets so they can manage credit consumption and spending.
Microsoft 365 Message Center ID: MC1461678
Primary Service: Power Platform
Admin Impact: Medium
User Impact: Low
Release Start: 01 Sept 2026
Release End: 01 Sept 2026
Last Modified: August 26, 2026
Category: Stay informed
Tags: New feature, Admin impact
Status: Launched
Products & Platforms: Microsoft Copilot (Power Platform)
History
8/25/2026 Item Added to Message Center
Microsoft Message
Beginning September 1, 2026, the grace period for existing agents and workflows built using the GitHub Copilot harness in Copilot Studio will end. These agents and workflows will begin consuming Copilot Credits under the usage-based billing model.
This applies to GitHub Copilot harness agents and workflows created before August 3, 2026, including those created in Dev or Trial environments. Both maker AI authoring activities and runtime execution will consume Copilot Credits. Standard harness and Copilot Chat harness agents are not affected.
How does this affect me?
Starting September 1, 2026, GitHub Copilot harness agents and workflows in your environment will consume Copilot Credits. Consumption information will be available through existing Power Platform admin center (PPAC) reporting and capacity management experiences.
Historical non-billed Copilot Credits data is available in the Power Platform admin center to help you understand current usage patterns. In PPAC, go to Licensing > Copilot Studio > Manage Agents. This information is directional only and should not be interpreted as a billing estimate or future cost.
What action do I need to take?
This message is for awareness, and no action is required.
Optionally, we recommend:
- Administrators review historical Copilot Credits consumption and identify active GitHub Copilot harness agents and workflows before billing begins.
- Administrators manage GitHub Copilot harness consumption by allocating credits to environments, controlling access to the shared tenant credit pool, monitoring usage in PPAC, and using Azure budgets and alerts for pay-as-you-go spending.
Learn More:
- Manage costs for agents powered by the GitHub Copilot harness
- Manage Copilot Credits and capacity for Copilot Studio
- Manage Copilot Credits allocations programmatically
- Identify all GitHub Copilot harness agents that have been created in your organization
- Power Platform admin center Environment Group rules – Cost controls – Draw from tenant credit pool