Bypass the Power Apps Permissions Prompt for a Frictionless Start
Eliminate the first-run consent pop-up that perplexes many users. This guide shows you how to disable the permissions form using a simple PowerShell cmdlet.
When a new user opens a canvas app in Power Apps, a permissions dialog often appears, requesting approval to create connections to the data sources the app depends on. While this is intended to ensure the user is aware of the connections being made, it frequently leads to confusion and support calls. In many internal business scenarios, the connectors are well-known and the data is not sensitive, making this additional step a barrier rather than a safeguard. This article explains how administrators can pre‑approve the required connections so that the consent pop-up is never shown.
Consider the case of the “Asset Checkout” app used by the facilities team at Contoso. Every new hire is greeted by the “Almost there…” screen and must click “Allow” before they can even see the dashboard. Several employees have flagged this as suspicious, and the helpdesk receives a steady stream of questions about it. The IT admin can eliminate this friction with a single PowerShell command.
Understanding the Consent Dialog
The consent form appears because Power Apps treats each user’s first launch as a new session. The platform does not automatically trust the connection requests made by the app — instead, it asks the user to explicitly approve each connector. The dialog lists the resources the app wants to access, such as a SharePoint site or a SQL database. After approval, the connection is stored for that user and future launches skip the prompt.
For administrators, the goal is to tell the Power Apps environment that a specific app is trusted, and that all current and future connectors used by that app are pre‑approved. This is accomplished with the Set-AdminPowerAppApisToBypassConsent cmdlet from the Power Apps Administration PowerShell module.
Preparing the Required Identifiers
Before you can run the bypass command, you need two pieces of information: the environment identifier (a GUID) and the app identifier (a GUID). Both are easily found in the maker portal.
Locating the Environment Identifier
- Open make.powerapps.com and ensure you are in the correct environment.
- Click the Settings gear icon (top‑right) and select Developer resources.
- In the Environment section, look for the Environment ID field. Copy the entire string — it often starts with
Default-followed by a GUID. - Save this value in a text file for later use.
Retrieving the App Identifier
- Navigate to the Apps list in the same environment.
- Find the canvas app you want to modify, click its ellipsis (three dots), and choose Details.
- In the Details panel, locate the App ID field. This is a plain GUID.
- Copy this GUID alongside the environment identifier.
Running the Bypass Command
With the two GUIDs in hand, you are ready to execute the bypass. These steps assume you have administrative rights (Environment Admin or Power Platform Admin) in the target environment.
Installing the Administration Module
If you have never used the Power Apps admin cmdlets, you need to install the module. Open Windows PowerShell as an administrator (search for “PowerShell” and choose Run as administrator). Then run:
Install-Module -Name Microsoft.PowerApps.Administration.PowerShell -Force Install-Module -Name Microsoft.PowerApps.PowerShell -AllowClobber -Force
If you are prompted to trust the repository, answer Yes or Yes to All.
Authenticating to the Power Platform
After installation, sign in with a work or school account that has administrative permissions:
Add-PowerAppsAccount
A browser window will open — complete the login process.
Executing the Cmdlet
Now that you are authenticated, use the Set-AdminPowerAppApisToBypassConsent cmdlet, replacing the placeholders with your actual environment and app identifiers:
Set-AdminPowerAppApisToBypassConsent -EnvironmentName 'Default-f1b8b509-50a4-4a5c-8e48-bf3d3e7c10ed' -AppName '9a6d22d6-79a2-4d32-8abd-747a1d8ebcb0'
If the command succeeds, you will see no error message — the console simply returns to the prompt.
Verifying the Change
To confirm that the consent dialog has been disabled:
- Ask a user who has never opened the app before to launch it. Alternatively, use a private/incognito browser session if you have a different test account.
- Observe whether the “Almost there…” pop-up appears. If it does not, the bypass is working.
When to Bypass Consent – and When Not To
Bypassing the permissions form is a convenient shortcut, but it should not be used indiscriminately.
Appropriate uses:
- Internal business applications where the connectors are well-known and the data is of low sensitivity.
- Apps that are used by a large number of users, where the support burden of the consent dialog outweighs the security benefit.
- Testing or development environments where repetitive consent prompts hinder productivity.
Cautionary notes:
- Once bypassed, any connector added to the app will automatically be pre‑approved. If a connector is later changed to access a different data source, users will not be prompted.
- For apps that access highly confidential data, retaining the consent dialog ensures that users explicitly approve each connection every session (or until they revoke consent).
- The bypass applies only to the app at the environment level; it does not affect other apps or environments.
Troubleshooting Common Issues
| Problem | Likely Cause | Solution |
|---|---|---|
| Cmdlet throws “Access Denied” | User does not have administrative rights | Run the cmdlet with an Environment Admin or Power Platform Admin account. |
| “The term ‘Set-AdminPowerAppApisToBypassConsent’ is not recognized” | Module not installed or not imported | Run Install-Module and then Import-Module as shown above. |
| Environment ID is incorrect | Copying only the GUID without the “Default-” prefix | Use the exact string from the Developer Resources page, including the “Default-” prefix if present. |
| App ID is incorrect | Grabbing the wrong app’s ID | Double-check the app details in the same environment. |
Key Takeaways
- The default permissions pop-up can be disabled per canvas app using the
Set-AdminPowerAppApisToBypassConsentcmdlet. - The cmdlet requires the environment ID and app ID, both of which are available in the maker portal.
- Bypassing consent streamlines the launch experience but reduces user visibility into the connections the app creates.
- Always evaluate the sensitivity of the data accessed by the app before removing the consent prompt.
References
- Original article: Matthew Devaney, Disable The Power Apps Permissions Pop-Up (Bypass Consent Form), https://www.matthewdevaney.com/disable-the-power-apps-permissions-pop-up-bypass-consent-form/
- Microsoft documentation:
Set-AdminPowerAppApisToBypassConsent(Power Apps Administration PowerShell) – [placeholder for official Microsoft Learn URL] - PowerShell module:
Microsoft.PowerApps.Administration.PowerShell– [placeholder for Microsoft Learn module reference]
Learn how small coding practices—like using descriptive names, flattening conditions, and simplifying logic—can make your apps easier to update and less error-prone.
Move past the gallery and discover the hidden patterns for validation, navigation, and smart submission handling in your data entry forms.
PowerShell unlocks admin capabilities that the Power Platform admin center simply doesn’t offer—from recovering deleted apps to blocking trial licenses. Here’s how to wield them safely.