Others

How to Prevent Users from Creating Apps in Power Apps

Partner Editor Sep 30, 2026 869 views

Question details

The administrator wants to restrict employees so they can only use shared applications without having the ability to create new apps in Power Apps.

How to Prevent Users from Creating Apps in Power Apps

Product: Microsoft Power Apps
Device & OS: not provided
Scenario: Managing employee permissions and securing the app development environment.
Observed behavior: Employees are currently able to create new apps despite modifications to existing security settings.

Before you start

Ensure you are logged in with Power Platform Administrator or Global Administrator privileges before attempting to modify environment roles and security settings.

Solution 1Recommended

Remove the Environment Maker Role

The most effective way to prevent users from creating apps is by removing their Environment Maker role in the Power Platform Admin Center.

By default, all users in a Microsoft 365 tenant may have the Environment Maker role in the default environment. Removing this role prevents them from creating new canvas apps or flows.

Access Admin Center

Go to the Power Platform admin center (admin.powerplatform.microsoft.com) and log in with your administrator credentials.

Select the Environment

Navigate to the 'Environments' tab on the left sidebar and select the specific environment where you want to restrict app creation (often the Default environment).

Manage Security Roles

Click on 'Settings' at the top, expand the 'Users + permissions' section, and select 'Security roles'.

Remove Maker Privileges

Locate and click on the 'Environment Maker' role. Review the list of assigned users or groups, and remove the specific employees or the 'Everyone' group to revoke their app creation privileges.

Check Group Assignments: If a user is part of a Microsoft Entra ID (Azure AD) security group that has the Environment Maker role, they will still be able to create apps. Ensure you check group permissions as well.

Solution 2

Consult the Power Platform Community

If standard role removals do not resolve the issue, seeking advanced guidance from the official community is recommended.

Free Microsoft Office alternative

Looking for a Lightweight, Cost-Effective Office Suite?

Managing complex permissions in enterprise software can be a hassle, but managing your daily documents shouldn't be. WPS Office offers a free, lightweight, and highly compatible alternative for all your word processing, spreadsheet, and presentation needs.

1. Download the Installer: Visit the official WPS Office website and click the Free Download button.
2. Install the Software: Run the downloaded installation package and follow the quick on-screen instructions.
3. Open Your Files: Launch WPS Office and instantly open your existing Microsoft Office documents without any formatting loss.

Fully compatible with Microsoft Word, Excel, and PowerPoint file formats.Free and lightweight, requiring minimal system resources for smooth operation.Familiar tabbed user interface, ensuring zero learning curve for seamless employee migration.Built-in PDF editing toolkit and cloud collaboration features.

microsoft office alternative - wps office

Frequently Asked Questions

Why can users still create apps after I removed their security roles?

Users may still have app creation capabilities if they are part of a Microsoft Entra ID (formerly Azure AD) security group that has the Environment Maker role assigned, or if they have broader tenant-wide developer privileges.

Can I allow users to create apps in a developer environment but restrict them in the default environment?

Yes, permissions are managed on a per-environment basis. You can remove the Environment Maker role from users in your default environment while explicitly granting it to them in a dedicated sandbox or developer environment.

Are there PowerShell commands to disable app creation entirely?

Yes, Power Platform administrators can utilize the Power Apps PowerShell modules to configure tenant-level settings. These commands can restrict users from creating trial environments and control overall maker permissions across the tenant.

Office Quick Solutions