We have created an additional environment (so this is not a default env.) and shared a Canvas App with use only option. Nevertheless, the user is able to create a Canvas App in that environment although he has no relevant roles (Environment Maker etc...) Has anyone else experienced this?
I understand this kind of behavior is in Default enviroment and we created a new environment just because of this, but we did not achieve the restriction for creating apps (Canvas). As per my understanding in order to create an App the user should have environment maker role?
Any suggestions?
thanks
Antonio
Thank you for a prompt reply!
Just one other thing, is there a specific priviledge that I can set or revoke on a security role which will enable/disable the ability to create an App? Or is it now by design (Creation is enabled as soon as you have a Powerapps role and there is no way to influence this? At least for now...)
BR,
Antonio
Hi @Antonio_V ,
Yeah, you are right. Previously, if one user wants to create a canvas app within a specific environment, the user must be a Environment Marker Role to that environment at least.
Since the updates released within PowerApps Admin Center, Security model has changed in PowerApps and is now managed in Dynamics 365 user management center.
Please check the following article for more details:
https://docs.microsoft.com/en-us/power-platform/admin/database-security
I have made a test, and the issue is confirmed on my side. It is a known issue that one user who have PowerApps license still have permission to create a canvas app in specific environment, even though, he is not Enviroment Marker role of that environment.
Please check the following blog for more details:
If you would like this feature to be improved, please submit an idea to PowerApps Ideas Fourm:
https://powerusers.microsoft.com/t5/PowerApps-Ideas/idb-p/PowerAppsIdeas
Best regards,
Michael E. Gernaey
9
Super User 2025 Season 1
bscarlavai33
5
Super User 2025 Season 1
getsplash
2