Control E3 Agent Creation in Copilot Studio
Diesen Beitrag auf Deutsch lesen
E3 and E5 can include classic Copilot Studio agent creation through Power Virtual Agents for Office 365. Disable that service plan per user or by group.
TL;DR
Microsoft 365 E3 and E5 can include classic agent creation through the Power Virtual Agents for Office 365 service plan. Disabling that plan per user or through Microsoft Entra ID group-based licensing blocks creating and editing classic agents, but does not delete existing agents or Dataverse for Teams environments.
Original by Em D'Arcy, on The Custom Engine. Read the original
This is our own summary, not a republication or full translation.
Governance takeaway
- Admins/CoE: Disable Power Virtual Agents for Office 365 per user or through group-based licensing to control classic agent creation consistently.
- Admins/CoE: Audit existing Dataverse for Teams environments before tightening access because disabling the plan does not remove existing agents or environments.
- Security/Compliance: Apply Managed Environments and DLP policies after the access change so permitted makers remain within governance guardrails.
Frequently asked questions
How can admins stop E3 users creating classic agents in Copilot Studio?
Disable the Power Virtual Agents for Office 365 service plan per user or through group-based licensing in Microsoft Entra ID.
What does Power Virtual Agents for Office 365 enable for Microsoft 365 E3 users?
It enables classic agent creation in Dataverse for Teams environments and publishing to Teams, without granting generative orchestration or premium connectors.
Does disabling the service plan delete existing Copilot Studio agents or environments?
No. Disabling it blocks creating and editing for affected users, but does not delete existing agents or clean up provisioned Dataverse for Teams environments.