How to “Disable” GitHub Copilot Harness Agents in Copilot Studio
Copilot Studio governance How to “Disable” GitHub Copilot Harness Agents in Copilot Studio One policy is not enough. Copilot Credits contain consumption. A Dataverse plug-in can reject the final save into the environment - but it cannot stop earlier harness authoring and testing. Together, both layers form a practical control. Author Lukáš Oplt 12 min read September 2026 Two layers for governing GitHub Copilot harness agents Power Platform capacity controls contain consumption while a Dataverse PreValidation plug-in prevents the agent from being saved to the environment. COPILOT STUDIO GOVERNANCE There is no single off switch. Control consumption and persistence as separate decisions. 01 · CONTAIN CONSUMPTION Copilot Credits Environment allocation · no tenant pool Covers authoring, testing and runtime 02 · BLOCK THE SAVE Dataverse plug-in Synchronous bot Create · PreValidation Does not intercept earlier harness activity BLOCKING THE SAVE DOES NOT REFUND THE BUILD. The GitHub...