Power Platform Community Forum Thread Details

Hey guys,

Is there any way to turn off Plans/Vibe in Power Apps?
Most of our users don't have a premium license. It's very frustrating for them when they create something with Plans that is based on Dataverse and then can't use it...

We have already tried the following:

Admincenter -> Tenant Settings -> Copilot in Power Apps (preview) to Off

By the way, it's exactly the same with model-driven apps. Our users create them because they don't know any better and then get annoyed because they can't use them, but there was no indication that this would be the case.

Greetings!

Categories:

Building Power Apps

Governance & administering

Experimental features

Yes, this is a common governance challenge in Microsoft Power Apps. Unfortunately, there is no single tenant setting today that completely disables Plans/Vibe or the ability to create certain app types for all users. However, you can control or minimize the issue using several governance options.

You cannot fully disable Plans/Vibe today, but you can reduce the problem by:

restricting Environment Maker roles
limiting Dataverse environments
using environment governance

Disable Copilot / AI Builder Features (Partially Done)

You already turned off:

Copilot in Power Apps (preview) in the Microsoft Power Platform Admin Center
This helps reduce AI-generated apps but does not stop users from creating model-driven apps or Dataverse-based apps manually.

The PowerShell command you provided is used to disable Copilot features at the tenant level within the Microsoft Power Platform and Dynamics 365 ecosystem

Set-TenantSettings -RequestBody @{
disableCopilotFeatures = $true
}

Disabling Copilot at the Environment Level
If you don't want to kill it for the entire company but want to stop the madness in specific environments (like the Default environment), do this:

Go to the Power Platform Admin Center.
Select Environments > [Your Environment Name] > Settings.
Expand Product > Features.
Find Copilot (preview) and set it to Off.

Critically: Also find the AI Builder settings here and ensure they are toggled off if you want to prevent users from trying to use AI models they can't pay for.

Stopping the "Model-Driven" Accidental Creation
The reason users keep making Model-Driven apps is that they have Environment Maker roles in an environment with a Dataverse database (usually the Default environment).

To fix this, you have to change your Environment Strategy:

Restrict the Default Environment: You cannot delete the Default environment, but you can change who has the "Environment Maker" role. If users only have "Basic User" rights, they can run apps but won't see the "Create" buttons that lead to Model-Driven setups.
Remove Dataverse from Default: (Extreme) If your organization doesn't use Dataverse at all in the Default environment, you can technically delete the database, though this usually breaks other things like Power Automate approvals.
Security Roles: Review the Environment Maker security role. You can create a custom version of this role that allows for "Canvas App" creation but removes permissions for "System Customizer" or "System Administrator" tasks, which are required for Model-Driven app design.