Hello Team,
We’ve noticed that users in our team are creating agents through Teams, M365 Copilot, and SharePoint using the “Create your own agent” option. Each time a new agent is created, it creates a new environment in the Power Platform with the team name and users are not aware they are creating new enviornments.
I would like to design a rule or configuration that redirects these agent creations to a specific, predefined environment instead of generating new ones.
Could someone please assist with this?
Thank you.
Hi, The behaviour you're observing—where each new agent created via Teams, Microsoft 365 Copilot, or SharePoint results in a new Power Platform environment—is expected when users use the “Create your own agent” feature. By default, this process provisions a new **Microsoft Dataverse for Teams environment** tied to the team or context in which the agent was created. --- ### 🎯 Objective: Redirect Agent Creation to a Predefined Environment Unfortunately, **there is currently no native setting to force or redirect agent creation to a specific environment** when users initiate it from Teams or SharePoint. However, here are some strategies to manage and guide this behaviour: --- ### ✅ Recommended Approaches 1. **User Education and Governance** - Educate users to **create agents directly in Copilot Studio** (https://copilotstudio.microsoft.com) and select the appropriate environment manually. - Provide internal documentation or training that explains the implications of creating agents from Teams or SharePoint. 2. **Restrict Environment Creation** - In the **Power Platform Admin Center**, you can limit who can create new environments: - Go to **Admin Center > Power Platform > Settings > Policies > Tenant settings**. - Under **Environment Creation**, restrict creation to specific security groups. - This prevents uncontrolled environment sprawl and ensures agents are created only in approved environments. 3. **Use Managed Environments** - Consider enabling **Managed Environments** for your organisation. This allows you to: - Set **Data Loss Prevention (DLP)** policies. - Monitor usage and capacity. - Apply **custom environment routing rules** (currently limited but evolving). - Learn more: https://learn.microsoft.com/en-us/power-platform/admin/managed-environments-overview 4. **Environment Routing via PowerShell or API** - While not officially supported for Copilot Studio agents yet, you can explore **Power Platform CLI or PowerShell** to automate environment governance and potentially intercept or reassign resources post-creation. --- ### 📌 Summary While you cannot currently redirect agent creation to a predefined environment automatically, combining **environment creation restrictions**, **user guidance**, and **managed environments** can help you maintain control and consistency. Thanks and best regards, Daniele Note: This response was prepared with support from Copilot to ensure clarity and completeness.
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
As AI tools become more common, we’re introducing a Responsible AI Use…
We are honored to recognize Tom Macfarlan as our Community Spotlight for October…
These are the community rock stars!
Stay up to date on forum activity by subscribing.
Romain The Low-Code... 523 Super User 2025 Season 2
Michael E. Gernaey 378 Super User 2025 Season 2
DAnny3211 132
