Answered

how to suppress user popup: Allow to access your data?

(0) Share

Report

Posted on by usarif

220

Folks, i am very new to apps, infact this my first.
I have a powerapps call Powerautomate to azure automation runbook.
In Powerautomate, I have 3 connectors.
AzureAutomation : connected with service principal, has Microsoft graph user.read api permission
Office 365 groups : service principal with Office E3 license
office 365 outlook : service principal with Office E3 license
I have created security group and added user into this SG. I haved added SG and share in powerapps.

In https://make.powerautomate.com/, I have created solutions and added imported my powerAutomate.

Issue: When user (in this SG) click on share url of powerapps, getting popup message
Allow fabric_groups to access your data?
To play this app, sign in or refresh connections, ensure the app is shared from a trusted source. and confirm permissions to access data.
it has all three connectors and in bottom showing Allow or Don't allow.
How can make sure user won't see this popup?

Categories:

Building Power Apps

I have the same question (0)

All responses (10)

Answers (1)

Sort by

Suggested answer

Pstork1 69,389 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

There is a PowerShell script that will auto accept the prompts and not display the dialogue. You can read about that here: Set-AdminPowerAppApisToBypassConsent (Microsoft.PowerApps.Administration.PowerShell) | Microsoft Learn In your particular case I don't think that will work for the Azure Automation. Although you've configured it to use a Service Principal its still going to require the user to login.

----------------------------------------------------------------------------------
If this Post helped you, please click "Does this answer your question" and give it a like to help others in the community find the answer too!

Paul Papanek Stork, MVP
Blog: https://www.dontpapanic.com/blog

Was this reply helpful? Yes No
usarif 220 on at

Like (0)

Report
Copy link

Link copied!

Thanks for your quick response @Pstork1, some reason it won't let me reply your thread.

Two questions, What are you recommendation user service accounts and principal.

2nd when do powershell set cmdlet, it asking authentication, is it service account connection service account or administrator account?

Was this reply helpful? Yes No
Pstork1 69,389 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

The PowerShell I showed you just suppresses the dialog. The connections still need to be created in the user context in Power Apps, but if you suppress the dialog they are created automatically. I'm not aware of any way to use a Service Principal directly in Power Apps. They can be created to be the owner of certain Power Automate flows. If the Azure Automation connection is showing up because you used that connector in a flow that is triggered from the app then it can run in the security context of the Service Principal if you set the Run Only user setting on the flow. To do that the flow and the app need to be in a Solution file. If you don't do that then the user will be prompted to create their own connection to Azure Automation when you start the app.

2) You need to be an Admin user to run that PowerShell command. So when its asking you to login its asking for an Admin login, not the Service Principal.

A service account really doesn't apply in this scenario. Service Accounts are just regular user accounts with licenses dedicated to running/owning an app or a flow. That way when a developer leaves the company the app/flow doesn't break because the owner no longer exists. But connections in a Power App almost always run in the security context of the user, even if you use a Service Account.

----------------------------------------------------------------------------------
If this Post helped you, please click "Does this answer your question" and give it a like to help others in the community find the answer too!

Paul Papanek Stork, MVP
Blog: https://www.dontpapanic.com/blog

Was this reply helpful? Yes No
usarif 220 on at

Like (0)

Report
Copy link

Link copied!

So, I have power automate in solutions.

After running powershell as mentioned below, now only one popups up where connected connected with azure automation with service principal.

Was this reply helpful? Yes No
Pstork1 69,389 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

Did you set the Run Only user setting on the flow for the Azure Connection to use the Service Principal instead of the one supplied by the user? Read more about that here: Share a cloud flow - Power Automate | Microsoft Learn

Without doing that it won't use the Service Principal connection it will prompt the user for a connection, which is what you are seeing. Since the user doesn't have one of those connections already created that part of the dialog will remain. Unless you specify that they don't need a connection with the Run only user setting.

----------------------------------------------------------------------------------
If this Post helped you, please click "Does this answer your question" and give it a like to help others in the community find the answer too!

Paul Papanek Stork, MVP
Blog: https://www.dontpapanic.com/blog

1 people found this reply helpful.

Was this reply helpful? Yes No
usarif 220 on at

Like (0)

Report
Copy link

Link copied!

Yes i Did

Was this reply helpful? Yes No
Pstork1 69,389 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

Is that screenshot before you set it or after? Right now its set to the default that the connection is provided by the user. There should be another option in the dropdown. Can you show me the way you have it set now?

Was this reply helpful? Yes No
usarif 220 on at

Like (0)

Report
Copy link

Link copied!

this is I setup now:

Drop down looks like this:

Was this reply helpful? Yes No
Pstork1 69,389 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

That should let you prevent the popup from showing. But it may be something about the Azure Automation connector or the fact that its running as a Service Principal that is prevent suppression of the dialog. It looks like everything is now setup correctly. If the dialog still shows then there is no way to turn it off.

----------------------------------------------------------------------------------
If this Post helped you, please click "Does this answer your question" and give it a like to help others in the community find the answer too!

Paul Papanek Stork, MVP
Blog: https://www.dontpapanic.com/blog

Was this reply helpful? Yes No
Verified answer

Pstork1 69,389 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

It is indeed the Azure Automation connector. One of the limitations of that connector when using a Service Principal is that it can't be shared. read here:

Azure Automation - Connectors | Microsoft Learn so the user is always going to be asked to create their own connection. Hence the dialog asking the user to login.

----------------------------------------------------------------------------------
If this Post helped you, please click "Does this answer your question" and give it a like to help others in the community find the answer too!

Paul Papanek Stork, MVP
Blog: https://www.dontpapanic.com/blog

Was this reply helpful? Yes No