![]() Starting now, when your end users are going to open the app, they will not see that prompt for permissions again.ĭisclaimer: before executing the Cmdlet I have republished the app using the Global Admin account. If all went fine, you should now see the “Code: 200” and “Description: OK”. Now copy, replace “APP-ID” with yours and execute the following Cmdlet, to bypass requesting for permissions: Set-AdminPowerAppApisToBypassConsent -AppName APP-ID -ApiVersion Correctly executed Cmdlet In case not, share the app with that account: Sharing PowerApps app with user as “Co-owner” Next open the details page of the PowerApps app you would like to “enhance” and copy its App ID: Obtaining PowerApps App IDīe sure, that the Global Admin account, if different to yours, also has “Co-owner” access to the app or is the “Owner” (and has PowerApps P2 license assigned). It is going to be valid for the next 8 hours: Add-PowerAppsAccount Prompt for credentials This call will open a prompt to collect the credentials (AAD account & password) that will be used by the commands. Next, import necessary modules: Import-Module. Next, as the Microsoft team is saying, that there is a known issue today that may also require to manually unblock the PowerShell, copy and paste the following command: dir. Type the below in PowerShell window: Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Force You need now to elevate/ change Execution Policy level of the scripts on your machine. Set the location path of your PowerShell console to the folder, where you unzipped the scripts (using the “cd” command).Open Windows PowerShell as an administrator.Important! You have to have administration account on your machine and be a Global Administrator of your Office 365 tenant, to follow the installation and execution steps! Source: I tried them, and it works! Below a step by step, so that you can get rid of these popups forever. Then I found this topic: and the solution described using PowerShell Cmdlets for PowerApps (described here: ). I found, that there is an idea already submitted: about allowing to make connections on behalf of a specific account. I was looking the internet for some of the solutions, information, how to impersonate such connection or elevate permissions for it, so that user is not asked to grant them on his own. This situation is usually a “no go” from business owners, who are asking “why is this showing” and claiming, that when a regular, end user sees it, he is not going to click anything because of the confusion. The message users were seeing was as following: Prompt for permissions ![]() Until last week I wasn’t aware, that when I use specific permissions to access data sources (SharePoint in that case) inside my app, the end user who is going to use that app will be asked for permissions, to be able to use that application. I’m a big fan of working with PowerApps and creating business solutions using that tool. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |