I'm trying to control whether or not Power Apps can be developed by creating a dedicated security role.
I thought that it could be achieved by turning off the "canvas app table" creation permission of the security role.
However, it seems that PowerAutomate/PowerApps cannot be developed with "copied security roles" or "security roles created from scratch".
Copy Security Role | Environment Maker vs Copy of Environment Maker
I would be grateful if you could give me an answer or advice to the following questions.
Sorry for the late reply.
I set the authority as advised, but it did not work as expected.
On the other hand, when I made an inquiry to a Microsoft engineer in parallel, it seems that it was a specification.
It behaves strangely.
Conclusion
- A security role that duplicates Environment Maker cannot develop "Power Automate" and "Power Apps".
- Creating a new security role with the same settings as Environment Maker cannot develop "Power Automate" and "Power Apps".
Your comments and advice have helped me. thank you.
If my reply helped you, please give a 👍 If it solved your issue, please give a 👍 & accept it as the Solution to help other community members find it more.
Visit my Blog: www.powerplatformplace.com
Visit my YouTube Channel: https://www.youtube.com/@powerplatformplace/videos
@h_takagai, you are using the modern view, use the classic view. Go to make.powerapps.com and then:
Find the security Role you copied and go to the customization tab and do what I have mentioned in my replies above.
If my reply helped you, please give a 👍 If it solved your issue, please give a 👍 & accept it as the Solution to help other community members find it more.
Visit my Blog: www.powerplatformplace.com
Visit my YouTube Channel: https://www.youtube.com/@powerplatformplace/videos
@h_takagai, can you share a screenshot of your custom security role (customization tab) that was copied from the Environment Maker system role?
hi @AhmedSalih
What I want to do is create a security role that cannot develop PowerApps but can run shared apps.
On the other hand, a security role created by copying Environment Maker cannot perform the following actions even if custom permissions allow canvas apps and workflows.
- Development app
- Running shared apps
- Development flow
- Running shared flows
As a result, we can't create the desired security role.
Hello, @h_takagai, when creating a custom security role for your use case, make sure that configure the customization permissions:
Note, if I want my users to only be able to use MDAs or Canvas apps only and not be able to create apps, flows, or even see the tables and other environment's objects, I made sure that all options in the customization tab are unselected. Except, if I have Business Rules for the DV tables forms, in that case you need to give access for the Process table.
If my reply helped you, please give a 👍 If it solved your issue, please give a 👍 & accept it as the Solution to help other community members find it more.
Visit my Blog: www.powerplatformplace.com
Visit my YouTube Channel: https://www.youtube.com/@powerplatformplace/videos
Hi @h_takagai ,
Please see details here on approach to control access to creating Power Apps in an environment.
stampcoin
17
ankit_singhal
11
Super User 2025 Season 1
mmbr1606
9
Super User 2025 Season 1