I have followed the directions here - http://powerappspros.com/2018/07/bypass-consent/
But when I try to bypass consent I get this error:
PS C:\PS> Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Force PS C:\PS> dir . | Unblock-File PS C:\PS> Import-Module .\Microsoft.PowerApps.Administration.PowerShell.psm1 -Force PS C:\PS> Import-Module .\Microsoft.PowerApps.PowerShell.psm1 -Force WARNING: The names of some imported commands from the module 'Microsoft.PowerApps.PowerShell' include unapproved verbs that might make them less discoverable. To find the commands with unapproved verbs, run the Import-Module command again with the Verbose parameter. For a list of approved verbs, type Get-Verb. PS C:\PS> Add-PowerAppsAccount PS C:\PS> set-AdminAppApisToBypassConsent -AppName d0d4e1bc-3134-463d-8aa8-68a6f2af3d5e -ApiVersion 2017-05-01 set-AdminAppApisToBypassConsent : The term 'set-AdminAppApisToBypassConsent' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. At line:1 char:1 + set-AdminAppApisToBypassConsent -AppName d0d4e1bc-3134-463d-8aa8-68a6 ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : ObjectNotFound: (set-AdminAppApisToBypassConsent:String) [], CommandNotFoundException + FullyQualifiedErrorId : CommandNotFoundException
I'm not sure what I'm doing wrong? 😕
You can watch my updated video to resolve your issue.
Also request you to please subscribe this channel
Watch this video to resolve your issue
Hi I tried this script but still users are prompted with consent screen. Any suggestions?
@v-xida-msft wrote:Hi @JamesM,
I agree with @jo's thought almost. The Set-AdminPowerAppApisToBypassConsent is added in PowerApps cmdlet 3.0 (PowerShell cmdlet for PowerApps).
Please take a try to type the following cmdlet within your PowerShell Command box:
Set-AdminPowerAppApisToBypassConsent –AppName ‘d0d4e1bc-3134-463d-8aa8-68a6f2af3d5e’ -ApiVersion 2017-05-01then check if the issue is solved.
More details about the PowerApps cmdlets, please check the following article:
https://docs.microsoft.com/en-us/powerapps/administrator/powerapps-powershell
Best regards,
Kris
In the short-term you can sign-up for PowerApps P2 30d trial - https://web.powerapps.com/trial. Beyond 30d you will need to purchase a paid license to PowerApps P2.
I was getting ready to send these instructions to our administrator to run, but when I read the requirements here, it states that a PowerApps Plan 2 license is required. So how can Office 365 licensed account admins using the free PowerApps plan, or even PowerApps Plan 1 account owners make any of these changes?
Hi @JamesM,
I agree with @jo's thought almost. The Set-AdminPowerAppApisToBypassConsent is added in PowerApps cmdlet 3.0 (PowerShell cmdlet for PowerApps).
Please take a try to type the following cmdlet within your PowerShell Command box:
Set-AdminPowerAppApisToBypassConsent –AppName ‘d0d4e1bc-3134-463d-8aa8-68a6f2af3d5e’ -ApiVersion 2017-05-01
then check if the issue is solved.
More details about the PowerApps cmdlets, please check the following article:
https://docs.microsoft.com/en-us/powerapps/administrator/powerapps-powershell
Best regards,
Kris
You can use the following command to look-up the names of all cmdlets in the admin module:
Get-Command -Module Microsoft.PowerApps.Administration.PowerShell
The name of the cmdlet you need is Set-AdminPowerAppApisToBypassConsent.
Michael E. Gernaey
9
Super User 2025 Season 1
bscarlavai33
5
Super User 2025 Season 1
getsplash
2