End Users receive pop-up asking for permission when launching Power Apps

[Anonymous]

Hi Team ,

I have created a Power Apps form to submit data to a SharePoint list. This form is shared with the whole organisation providing them with 'User' access on it. 

Problem Statement : When any of the end user opens the form for the first time , they have to 'Allow' access as seen below. This is not user friendly and can be confusing for most non-technical users. Is there a way to allow this by default so that every user does not require to go through the pop-up. We have alreay given them the required access on the form and the list it connects to. We have SSO(Single sign on) enabled on the enviroment.

Your early response will be appreciated as we are planning to go live soon.

Thanks & Regards ,

Neha

[Ptodd]

I have a Service Account which we assumed would be included and configured in the connector - Obviously we can't pass out credentials... Has anyone found a workaround?

...

[cchambers]

I have a bit of a workaround that I use, it's not great but it works for certain situations. What I've noticed is that if you create a PowerApp as a Sharepoint list form and then have the flow act when the list item is created, there are no permissions prompts for the end-user. This means I can at least capture the username, use the flow to pull information from the database, and then put this information either in another list or simply email it to the relevant parties. This is only one-way information flow however, I cannot return information to the PowerApp. I really hope this is resolved, there are several workflows that would be dramatically simplified if this happens.

[cchambers]

I wish we could get some more clarification on whether Microsoft plans to address this.

There are very many processes we would love to automate with our current toolset, but we are limited to only pushing data and not pulling into the PowerApp.

[Anonymous]

Please post link to your idea-post so we can easily find and upvote it. ...this UX is a deal-breaker for use of PowerApps

[dluzzi]

Here is the link to the uservoice suggestion

https://powerusers.microsoft.com/t5/PowerApps-Ideas/Delegate-to-Administrator-Allow-access-window-wh...

[Anonymous]

Thanks, I've upvoted the idea, and expanded on it to suggest a toggle-on-off control from PowerApps Admin Center.

In the mean time I've found a PowerShell solution but it is extremely cumbersome. PowerShell Cmdlets for PowerApps are here: https://powerapps.microsoft.com/en-us/blog/gdpr-admin-powershell-cmdlets/

What makes the PowerShell solution frustrating is this:

 - To activate "PowerApps Connection Direct Consent Bypass" the PowerShell cmdlets must be run EVERY the first-time the PowerApps form is published.

 - To successfully execute the PowerApps cmdlets the user must be an o365 Global Admin, the PowerApp Owner/Publisher, and the local machine Admin,

 - When executing PowerShell (as Admin) command "Set-ExecutionPolicy" must be run multiple times to defeat Global policies. The "Process" ExecutionPolicy must be reset each time the PowerShell instance is re-opened.

 - PowerShell ISE freezes shortly after running any of the PowerApps commandlets.  (this maybe a local issue for me)

 - The cmdlet authenticating into PowerApps throws an error when running in a Server 2012 environment. Win10 appears to be the only environment where authentication is possible.

Good luck

[Anonymous · Accepted solution]

BTW - the magic PowerApps cmdlet in PowerShell is... 

Set-AdminPowerAppApisToBypassConsent -AppName put-the-PowerApps-GUID-here -ApiVersion 2017-05-01

[Jake_Li]

I'm runnuing into the same situation where users are required to allow the app created with PowerApps to use SharePoint as data source. Our Office 365 Tenant Admin did run the cmdlet as follows, but failed to get the result of bypassing the user consent (to use SharePoint as data source) as expected.

Set-AdminPowerAppApisToBypassConsent -AppName d96d466b-ee1b-43a1-bbe4-xxxxxxxxxxxx

My app had been published for many times before the cmdlet was called and we did get an Ok message after running the cmdlet.

I'm struggling to get rid of this deal breaker in hitting my deadline to delilver the app.

Appreciate it if anybody can shed some light.

Fingers crossed.

Regards, Jake

[Anonymous]

Looking back at my notes, I was successful executing the PowerApps cmdlet using a role that was both the PowerApp  publisher and o365 Global Admin.  If your command execution result is "code: 200. description: OK" and your users are still  receiving the consent-prompt I recommend double checking the GUID to confirm you are executing against your most recently published version (GUID can change) then I'd ask your o365 admin to temporarily provide the publishing account with "Global Administrator" rights, he can revoke those priv's after successful execution.

Good luck.

[Jake_Li]

Hi Neville,

Many thanks for your prompt reply. 

I did check the GUID of the app and could not find any difference.

Per your suggestion, I'd talk to my o365 Admin in providing the publishing account with "Global Administrator" rights. Prior to doing that, may I know if this process, if it works, is needed just once and for all for the same app or an exercise required every time the app has been publilshed?

Jake