I created my app woith a SQL server on Azure connection adn works just great, however, when I or someone I share the app browse the App URL it shows the error:
What could it be? I have tried deleting the connection and recreating it, the connection works on the app editor it is not an authentication issue.
Solved! Go to Solution.
Did you verify the App permissions is set-up correctly? Another thing to check is the shared permissions on the connector it self. The connector permissions should automatically be set when you set the app permissions but it never hurts to check when weird things are happening.
I have made a test on my side and don't have the issue that you mentioned. I agree with @Jeff_Thorpe's thought almost, if you have added a connection within your PowerApps app, when you play your app, the connector permission would be set automatically.
Please check if you have added a proper SQL Server connection within your PowerApps app. Please also check if the SQL Server connection within your PowerApps app is invalid, if yes, please update the connection.
If you have solved your problem, please click "Accept as Solution" so that this thread will be marked for other users to easily identify.
Hello - I'm having a similar problem, but issues aren't clearing even after I removed the SQL connection and the pages that had those connections configured. The prompt message is occuring to everyone. Also the [ALLOW] button is greyed out.
I am having the same issue for an app that previously did work. It blocks anyone who tries to use the app, including myself, even though I am the creator. I have tried un-adding and re-adding users to the connection and that did not work.
When I "edit" the app then run it, the app functions as usual, but I don't want to give this access to all users. Can anyone help please?
Were you able to fix this issue.
Please let me know, I'm also facing the same issue with my application.
Thanks in advance.
After giving the permissions in PowerApps -> Data -> Connections via the Share button, I had to do a CTRL-F5 on the browser or else it did not work even if I had relogged with the user after reopening the browser.
Now it says signed-in and works.
We're excited to announce our first cross-community 'Can You Solve These?' challenge!
Reopen responsibly, monitor intelligently, and protect continuously with solutions for a safer work environment.
We are excited for the next Super User season.
FIll out a quick form to claim your community user group member badge today!
Features releasing from October 2020 through March 2021