web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Copilot Studio / Copilot Studio - Agent...
Copilot Studio
Suggested Answer

Copilot Studio - Agent Deployment Experience

(1) ShareShare
ReportReport
Posted on by 2

Hi all,

I'm very new to Copilot Studio / Power Platform / Dataverse and have spent the last couple of days trying to put some governance around Copilot agent development and deployment within our tenant. I wanted to sense-check whether what I experienced is expected behaviour, or whether I have misunderstood something fundamental.

Originally, I created a Copilot Studio agent in the Default environment and everything worked as expected. I was able to publish the agent, share it with users and they could install and interact with it successfully.

I then decided to create a more governed deployment model:

  • Created a dedicated Power Platform environment: "AI & Automation"

  • Enabled Dataverse

  • Assigned an Entra ID security group to restrict access

  • Created a Publisher

  • Created a Solution

  • Rebuilt the agent inside the Solution

  • Added SharePoint knowledge sources

  • Published to M365 Copilot / Teams

The idea was to move away from building everything in Default and instead create a controlled deployment environment for future AI and automation solutions.

However, after moving to the new environment, test users experienced very strange behaviour:

  • Users could see/install the agent (sometimes)

  • Updated prompts and agent changes propagated successfully

  • Users could not query SharePoint-grounded knowledge

  • Users did not appear in Copilot Studio Activity logs

  • Agent execution appeared to partially fail

  • I (creator/owner) could query successfully

Initially I assumed this was SharePoint permissions, knowledge indexing, propagation, Teams caching, etc.

After a lot of testing, what eventually got things working was:

  1. Assign M365 Copilot licence

  2. Add user to environment security group

  3. Manually add/confirm user as an enabled Dataverse user within the environment

  4. Assign Basic User role

  5. Confirm access to SharePoint knowledge sources

  6. Share agent

  7. Wait for propagation

Once I did this, the user could successfully install and query the agent and sessions began appearing correctly.

My confusion is this:

I had assumed agent consumers simply needed the agent shared with them and permissions to the underlying knowledge source. I wasn't expecting users consuming an agent from a custom environment to require environment membership and Dataverse provisioning.

Is this normal/expected behaviour for Copilot Studio agents deployed from custom environments and Solutions, or have I configured something incorrectly? I appreciate I'm still very early in my understanding of Power Platform/Dataverse architecture, so I may well have made incorrect assumptions.

Thanks in advance.

 

I have the same question (0)
  • Romain The Low-Code Bearded Bear Profile Picture
    2,665 Super User 2026 Season 1 on at
    hello, 
     
    You did well ok, agent with copilot studio are inside environnement. They are like application, and people need access to the environnement wich store the applicaiton. So they need access to the environnement. For governance perspective it's very important , imagine you create a HR environnement, you want to be sure that only HR people will use the app / agent from this environnement. Same for finance. executive etc. that the main reason. it allow to isolated data and apps for security and governance purpose :)
     
    so you did well :) 
     
    Hope it answer the question, if yes, please click on mark the answer as verified, it's very important :)
  • Suggested answer
    Romain The Low-Code Bearded Bear Profile Picture
    2,665 Super User 2026 Season 1 on at
    hello, 
     
    You did well ok, agent with copilot studio are inside environnement. They are like application, and people need access to the environnement wich store the applicaiton. So they need access to the environnement. For governance perspective it's very important , imagine you create a HR environnement, you want to be sure that only HR people will use the app / agent from this environnement. Same for finance. executive etc. that the main reason. it allow to isolated data and apps for security and governance purpose :)
     
    so you did well :) 
     
    Hope it answer the question, if yes, please click on mark the answer as verified, it's very important :)

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.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Users!

Kudos to our 2025 Community Spotlight Honorees

Congratulations to our 2025 community superstars!

Congratulations to the April Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Copilot Studio

#1
Valantis Profile Picture

Valantis 813

#2
Vish WR Profile Picture

Vish WR 313

#3
Haque Profile Picture

Haque 271

Last 30 days Overall leaderboard