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?
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.
Here is the link to the uservoice suggestion
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.
BTW - the magic PowerApps cmdlet in PowerShell is...
Set-AdminPowerAppApisToBypassConsent -AppName put-the-PowerApps-GUID-here -ApiVersion 2017-05-01
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.
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.
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?
Check out these cool Power Apps & vote on your favorite!
Let's talk about the solution provided by Microsoft for Robotic Process Automation (RPA)
Check out whats happening in Power Apps
FIll out a quick form to claim your community user group member badge today!