The world of PowerApps can be new and exciting, not to
mention completely frustrating! A lot of my frustrations come from my lack of
knowledge of the product but there are times when it’s not that, but an issue
with the Office 365 platform itself.
This brings me to my issue I was having when embedding PowerApps onto an Office 365 modern SharePoint page. I had saved and published my form, and all seemed well. It displayed perfectly or me, all controls worked, etc. I had someone on my team test and suddenly, something was amiss.
My tester said that they were being asked for credentials.
But why? Why would I ever need to provide my login information again after I
have already logged in to 365? If you don’t know what I’m talking about or
haven’t been fortunate yet to see this screen, this is what it will look like:
This post mentions that if you receive the connection
permission sign in pop up, that it is possible to bypass it by running the following
PowerShell command bout having to run a PowerShell command:
Now, don’t do what I did and run this command expecting
everything to work all nice and stuff. There are a number of steps you need to
follow before you can even run this command. That being said…….. Let’s do
If you notice, there is a GUID used to identify the PowerApp. The easiest way to get the App ID (GUID) is to login to the PowerApps Admin Center. Once there, find the specific PowerApp that you are working with and click on it to see the details. At the bottom of the screen you should see the App ID. Copy the GUID next to that and place next to –AppName in your script.
You can also use this PowerShell command, Get-AdminPowerApp, but for me this is a slower process because I’m having to look through the many line items. I’ve always been more of a GUI type user, so really it’s just a preference.
Once run, you will see the following output on your screen: