Power Platform Community Forum Thread Details

As an enterprise administrator, I would like Microsoft to introduce governance, visibility, and cost-management controls for GitHub Copilot Harness in Copilot Studio.

GitHub Copilot Harness can consume Copilot Credits during authoring, testing, previewing, evaluations, and runtime. Microsoft also confirmed that Microsoft 365 Copilot licensing does not automatically cover GitHub Copilot Harness consumption and that there are currently no documented tenant-level, environment-level, PowerShell, or DLP controls to restrict its usage.

Requested Enhancements

1. Administrative Governance

Provide the ability to:

Disable GitHub Copilot Harness at the tenant level.
Enable or disable GitHub Copilot Harness per environment.
Hide GitHub Copilot Harness from the agent creation experience.
Restrict harness selection using DLP policies.
Define which harness types are permitted within an environment.

2. Environment Defaults

Provide the ability to:

Set a default harness for an environment (for example, Standard Harness).
Prevent makers from changing the default harness.
Automatically apply governance settings to newly created agents.
Automatically apply default consumption limits to new agents.

3. Cost Protection

Provide the ability to:

Automatically block GitHub Copilot Harness when no Copilot Credits are allocated.
Prevent accidental credit consumption during agent creation and testing.
Define environment-level credit policies and thresholds.

4. Reporting & Visibility

Provide the ability to:

Identify which harness type each agent is using.
Report on harness usage across the tenant.
Expose harness information through Admin Center reporting, APIs, and PowerShell.
Track Copilot Credit consumption by harness type.

Why This Is Important

Today, organizations can govern makers, environments, and Copilot Credits, but they cannot directly govern GitHub Copilot Harness itself. This creates a gap where users can select a credit-consuming harness without administrators having equivalent controls to restrict, monitor, or standardize its use.

For enterprise deployments, governance should be preventative rather than reactive. Organizations need the ability to control harness selection, enforce standards, apply default limits, and gain visibility into adoption before credit consumption occurs.
These capabilities would significantly improve enterprise readiness, cost governance, and operational management of Copilot Studio at scale.

Categories:

General topics

Hi,

Great suggestion. As enterprise adoption grows, governance for harness selection should be as robust as governance for environments, connectors, and agent publishing. Today, administrators can manage capacity and maker access, but there is limited visibility and control over which harnesses are used and how they consume credits.

Tenant-level and environment-level controls, default harness settings, DLP integration, consumption guardrails, and detailed reporting would help organizations standardize deployments and avoid unexpected credit usage. The ability to identify harness types across agents and track consumption by harness would also improve operational oversight and cost management.

This would be a valuable enhancement for organizations deploying Copilot Studio at scale, especially those with strict governance, compliance, and budget requirements.

Thanks & Regards,

Manoj Annavajjala