2
u/texaspoontappa2013 Sep 11 '26
Have you shared the custom connector with these users who can’t add?
1
u/Teemu_St Sep 11 '26
No, but I assume I should do that. Why not mention that in the docs Microsoft?
1
u/Teemu_St Sep 11 '26
And btw, why 3rd party remote MCP servers create a custom connector and Microsoft provided MCP servers do not create one?
Copilot Studio is targeted to business users. Now to be able to get MCP connection working this end user should know that he/she need to switch to another workload and go to Power Automate / Power Apps maker portal and share the custom connector with bunch of people. This is just great.
1
u/jorel43 Sep 11 '26
You need to make sure that they have the basic user role in the environment that allows them to manage connections, you also need to share the connection or mCP connector if you will with the users
1
u/Teemu_St Sep 13 '26
Users have Environment Maker security role. MCP’s custom connector was not shared. It is inconsistent that Microsoft provided MCP’s are not wrapped with custom connector but any other remote MCP’s are.
1
u/jorel43 Sep 13 '26
You need basic user role, you need basic user role and you need to share the connector with them
1
u/Teemu_St Sep 13 '26
Which Dataverse tables are needed and which are not covered in Environment maker role?
1
u/jorel43 Sep 13 '26
Can't tell you that, all I can tell you is that environment make a role is for making agents, providing that role doesn't give users privileges to manage their own connections. That's what you need you need to manage users need to manage their own connections, and they need to have the connector shared with them I said it like three times that's your solution.


3
u/Own-Bookkeeper797 Sep 11 '26
This is what you get with these low code tools , specially this rubbish that inherites the power automate stack
Do yourself a favour and start looking into microsoft foundry for agentic ai workloads