MC1446644: Microsoft Copilot Studio Makes GitHub Copilot Harness Generally Available for Building Agents and Workflows

5 minutes
MWPRO IMPACT SCORE
OPERATIONAL IMPACT
53
0 25 50 75 100
HIGH IMPACT • REVIEW RECOMMENDED
Recommended Action:
Review the update and plan any required actions before rollout.
▶ What is MWPro Impact Score? Watch our 60‑second explainer

Primary Audience

Microsoft 365 AdminsPower Platform AdminsIT ManagersService OwnersDevelopers
Why this score?
AI Confidence
HIGH
Enough detail is available to trust this assessment.
Assessment Reasoning
This is the general availability of a new GitHub Copilot harness in Copilot Studio, adding autonomous agent and workflow capabilities. Admin impact is significant due to new authoring options, governance, cost management controls and usage-based billing. User impact is limited because existing agents remain unchanged, although makers will see new options. Urgency is moderate as GA starts today and billing begins immediately for new harness use, with a grace period for pre-GA creations. Implementation effort includes reviewing licensing, updating governance, managing credits and possibly training makers.
65
🛡️ Admin Impact
HIGH
25
👥 User Impact
MEDIUM
55
⚡ Urgency
HIGH
50
🔧 Effort
HIGH
ℹ️ WHAT YOU NEED TO KNOW
📌

AT A GLANCE

GitHub Copilot harness in Copilot Studio is now generally available. It adds advanced reasoning, workflow orchestration, and usage-based billing with Copilot Credits.
👥

END USERS

No major end-user change expected.
🛡️

IT ADMINS

Review new billing model, manage Copilot Credits in PPAC, and update governance and training before adoption.
📅

ROLLOUT TIMELINE

Start:
August 2026

📢 Official Microsoft Message Center Announcement

Microsoft Copilot Studio: GitHub Copilot harness now generally available for building autonomous agents and workflows
Message ID: MC1446644

[What and why]

We’re announcing the general availability (GA) of the GitHub Copilot harness in Microsoft Copilot Studio, previously available in Public Preview as the new Copilot Studio experience. Beginning August 3, 2026, organizations will be able to build and run agents and workflows powered by the GitHub Copilot harness directly within Copilot Studio.

With this release, Copilot Studio evolves into a multi-harness platform, allowing makers to choose the harness best suited to their scenario. A harness provides the underlying reasoning, planning, and tool orchestration framework that determines how an agent operates.

Available harnesses in Copilot Studio include:

  • GitHub Copilot harness, which supports autonomous business processes, workflow orchestration, and agentic scenarios
  • Standard harness, which is used by most agents in Copilot Studio today and supports conversational agents with rules-based topics
  • Copilot Chat harness, which uses the same harness as Microsoft 365 Copilot Chat and is designed for customizing Copilot Chat experiences

Existing Copilot Studio agents and deployments will continue to function as they do today. No existing agents will be modified or migrated to a different harness as part of this rollout.

[Rollout schedule]

  • General Availability (Worldwide): Beginning on August 3, 2026

[Impact on your organization]

Who is affected

  • Copilot Studio makers and administrators
  • Organizations building custom agents and workflows in Copilot Studio
  • Microsoft 365 Copilot customers evaluating advanced agentic scenarios

Platforms and services

  • Microsoft Copilot Studio
  • Microsoft 365 Copilot
  • Power Platform admin center (PPAC)

What will happen

Beginning August 3, 2026:

  • The Copilot Studio home experience will be updated to include the GitHub Copilot harness as a new authoring option for agents and workflows.
  • Makers can create agents and workflows using visual workflow orchestration, planning capabilities, and reasoning experiences powered by the GitHub Copilot harness.
  • The GitHub Copilot harness introduces a usage-based billing model that uses Copilot Credits. Charges may apply for both maker creation activities and runtime execution. For licensing details, review the Copilot Credits licensing guide (PDF).
  • Existing Copilot Chat harness and Standard harness agents will continue to function without change and remain accessible from ‘Other ways to build’.
  • The Copilot Chat harness and Standard harness will maintain their current licensing and billing models. There are no changes to the Microsoft 365 Copilot entitlement for Copilot Chat harness agents or Standard harness agents.
  • Billing for all Copilot Studio harnesses (including GitHub Copilot) will be available through Power Platform admin center (PPAC).

Grace period for existing agents and workflows created using the GitHub Copilot harness:

  • Agents and workflows created before August 3, 2026, will begin consuming Copilot Credits under the GitHub Copilot harness usage-based billing model on September 1, 2026. Makers will receive in-product notifications indicating that the agent or workflow is in a grace period before billing enforcement begins.
  • Agents and workflows created on or after August 3, 2026, will begin consuming Copilot Credits under the GitHub Copilot harness usage-based billing model on August 3, 2026.

[Action required and recommendations]

No action is required for existing Copilot Studio deployments.

We recommend that administrators:

  • Review current Copilot Studio deployments and identify scenarios that could benefit from advanced reasoning and workflow orchestration capabilities.
  • Familiarize makers and administrators with the GitHub Copilot harness usage-based billing model.
  • Review cost management capabilities available through Power Platform admin center (PPAC). Learn more: Manage Copilot Studio credits and capacity
  • Review expected Copilot Credits consumption before deploying GitHub Copilot harness agents in production.
  • Update internal governance, training, and adoption materials to reflect the new multi-harness experience.

Learn more

[Compliance considerations]

IssueExplanation
Generative AI capabilityThe GitHub Copilot harness introduces advanced AI-powered agent creation, reasoning, planning, and workflow execution capabilities. Organizations may want to review internal AI governance requirements prior to adoption.
New billing and consumption modelGitHub Copilot harness workloads use usage-based billing through Copilot Credits. Organizations should review budget and cost-management processes.
Admin controlsCost management controls are available through Power Platform admin center.
User accessAccess is governed through existing Copilot Studio permissions. The launch does not introduce a separate per-user enablement or disablement control for selecting the GitHub Copilot harness.

Source: Microsoft Message Center • Analysed by MWPro

Share This Update
Tags: