Forum Discussion
Copilot Chat. Disable Agent Creation, Allow Agent use
- Mar 27, 2025
Thanks again jillybean. I have added a feedback record explaining the necessity for this granular control. Everyone, please go there and upvote!
https://feedbackportal.microsoft.com/feedback/idea/d72808b3-280b-f011-a4dd-7c1e52ead3c1
Manage agents for Microsoft 365 Copilot in Integrated Apps - Microsoft 365 admin | Microsoft Learn
Admins can enable or disable Copilot extensibility for their org by using a setting on the Integrated apps page in the Microsoft 365 admin center. This setting lets admins control who can access agents in their organization.
To do this, follow these steps:
- Go to Integrated apps in the Microsoft 365 admin center.
- Select Available apps, and then the settings icon.
- Find Allow the following users access to Copilot agents and choose your preferred setting.
The setting has three options:
- All Users This is the default option and it means that all users in the organization can access agents, subject to the existing app policies and user assignments.
- No Users This option means that no users in the organization can access agents, and the third party agents are disabled in the agents flyout. This option also hides agents from the list of Available and Deployed apps on the Integrated apps page.
- Specific Users This option lets you select specific users or groups in your organization to have access to agents. So while all or specific users in your organization may have permissions to install and use apps from the Available apps and Deployed apps lists, only the users or groups you select in this setting can use agents.
Hi Jillybean,
Thank you for taking the time to reply.
I am familiar with the Copilot availability settings, but they are not granular enough for my needs. I would like all users to be able to access and use Agents, while keeping Agent Creation as a centralized function.
This approach will ensure that no personal data is used as knowledge and will enable control over the Pay-as-you-go license. I don't think this is a strange or unique use case.
Do you have any ideas on how I can achieve this?
Many thanks,
Rem
- WardWMar 26, 2025Copper Contributor
Sharing the exact same opinion.
How can an enterprise customer make a decent roll-out plan without this granularity in the policy?
With the current policy, it's either block all declarative agents in BizChat or open all gates from day 1.
- jillybeanMar 25, 2025
Microsoft
Hi remojsy79.
Currently the Agent Builder and access to Agents are controlled together. In addition to your support ticket, please consider providing feedback to Microsoft to request enhancement to this feature.Learn about how to provide feedback to Microsoft - Microsoft 365 admin | Microsoft Learn
- remojsy79Mar 27, 2025Brass Contributor
Thanks again jillybean. I have added a feedback record explaining the necessity for this granular control. Everyone, please go there and upvote!
https://feedbackportal.microsoft.com/feedback/idea/d72808b3-280b-f011-a4dd-7c1e52ead3c1
- Dan79Mar 23, 2025Copper Contributor
Hi,
did you ever manage to resolve this as I’m facing the same problem?!
- remojsy79Mar 24, 2025Brass Contributor
Not yet, have a ticket open with Microsoft. Will share here if/when resolved.
- WardWMar 26, 2025Copper Contributor
We have a ticket open as well, let's hope we can put enough pressure to make 2 policies of the current policy.
- Users who can "use" agents.
- Users who can "create" agents.