Right now we globally allow all users access to all applications. What I want is to restrict users from creating Flows and PowerApps, but still allow them to use those features. Examples: If I publish a PowerApp and share it with all users, I want them to be able to use the published app. With Flows, this is where the new approval process is built, so a user needs to access their Approvals but not allowed anything else.
What is possible with this and what is not?
Solved! Go to Solution.
Has anyone found a solution or workaround to this issue?
It would be great to have a feature similar to the PowerShell command that can disable the capability for all users to create new environments.
Hi @eu11910, looks like there isn't a solution - this might help explain: https://powerusers.microsoft.com/t5/Power-Apps-Ideas/Restrict-users-from-creating-PowerApps-in-defau...
The solution to this problem is to create a business apps environment. In this environment all important apps (apps developed professionally for the whole organization) reside. You can share the app with any number of users or groups. Do not give them maker role. Use the default environment for personal productivity apps i.e. as a playground.
This "Personal Production" playground "solution" is not a solution. Users will simply create production apps in the default environment if there is no way to prevent them from doing so.
Microsoft should find a solution quickly for this issue.
I don't know how is it working by Microsoft, but the company I'm in, makes a difference between developers or makers and users.
A user should be able to use a Power App, but not create one.
Is it so difficult to implement? Many people have same problem and need a solution, so if you want more people to use Power Apps, make this possible.
Hi, is there any update on this from Microsoft. We really need a solution to lockdown users from creating Power Apps within the default environment. We are trying to roll out Power Apps applications to our users which then comes with the risk that once they have access to the Power Apps environment itself they are then able to create their own apps in the default environment. Surely a security group approach could be implemented for the default enviroment which currently exists for bespoke environments created by admins? Thanks.
Keep up to date with current events and community announcements in the Power Apps community.
Join us in Las Vegas to experience community, incredible learning opportunities, and connections that will help grow skills, know-how, and more.
Check out the latest Community Blog from the community!