Microsoft Copilot Studio – Enhance governance with an admin control to block agents [MC1104083]

Message ID: MC1104083
We are announcing a new control for admins, allowing them to block agents created in Microsoft Copilot Studio. This feature provides a PowerShell command to block Copilot Studio agents by the admin. This feature will reach general availability on July 15, 2025.

How does this affect me?
There may be different reasons where an admin would want to put an agent in a quarantine state, either due to costs or due to a vulnerability that is related to security risk. Blocking an agent is now available as an action that an admin can perform via PowerShell.

Admins can quarantine an agent via REST API (Bots – REST API) or any of our available SDKs (Programmability and extensibility – What’s new or changed). To run the command, the admin needs to have one of the following roles from Microsoft Entra ID:

• Global administrator
• Power Platform administrator

As an admin, you will have two separate commands, one for blocking an agent and the other for un-blocking an agent. Once an agent is blocked by an admin its new status will be reflected as follows:

1. Maker experience: Makers will be able to edit the blocked agent but not test it. When trying to interact with the agent via the test pane in Microsoft Copilot Studio, the maker will receive an error message saying the agent is blocked by the admin.
2. End user experience: For end users, they will not be able to interact with a blocked agent and will receive an error message every time they try to interact with a blocked agent.

What action do I need to take?
This message is for awareness and no action is required.

Source: Microsoft

Latest Posts