Unanswered

Connector "HTTP with Azure AD" asks credientals for end user

(1) Share

Report

Posted on by Community Power Pla...

Hello everybody!

I have an app where I want to use Flow which gets data from a REST API service secured by Azure AD. Everything worked flawlessly when I set everything up and tested myself. However, when I shared it with a new user, they were met with the following connection screen when launching the app:

Why is the end user asked for credentials to connect to the REST API behind Azure AD? The user is within the Azure AD and I filled in these credentials when adding this connector in edit mode.

Is there a way to make a connection with REST API behind Azure AD that won't ask end user for auth credentials?

Max.

Categories:

Building Power Apps

I have the same question (0)

All responses (9)

Answers (0)

v-monli-msft on at

Like (1)

Report

Hi @Anonymous ,

I have found multiple threads stating this issue:

https://powerusers.microsoft.com/t5/General-Power-Automate/Using-quot-Http-with-Azure-AD-quot-How-to-pre-populate-quot/m-p/246728

https://powerusers.microsoft.com/t5/Building-Power-Apps-Formerly/How-to-bypass-the-prompt-for-Base-Resource-URL-for-PowerApp/td-p/315234

If you want to improve this, please consider to add an idea in PowerApps idea forum here:
https://powerusers.microsoft.com/t5/PowerApps-Ideas/idb-p/PowerAppsIdeas

Regards,

Mona

Was this reply helpful? Yes No
Community Power Pla... on at

Like (0)

Report

Hi @v-monli-msft,

Thank you for looking into this a bit! Hopefully PowerApps would come eventually to a connector solution that doesn't ask end user technical parameters.

Max.

Was this reply helpful? Yes No
RP_NB 2 on at

Like (0)

Report

Is there any update on that issue? Has it been resolved yet?

Was this reply helpful? Yes No
Community Power Pla... on at

Like (0)

Report

Did anyone ever come up with a workaround?

Was this reply helpful? Yes No
cornelco 4 on at

Like (0)

Report

On the Flow details page in the bottom right there is a section for run only users. In there you can select run only users to use your connection to the HTTP with Azure AD connector.

In my testing this works to allow users to use the HTTP with Azure AD without them needing to create a new connection which requires entering that information.

Was this reply helpful? Yes No
chuck_stones 8 on at

Like (0)

Report

Sorry to somewhat Lazarus this thread, but @v-monli-msft & @cornelco do you have any more insight into this connector? I have a solution with 2 canvas apps (user, admin). The user app adds records to a Dataverse table which triggers a flow. The flow needs two HTTP Azure with AD actions which I moved to child flows and set the run only users to a connection reference which uses a service account. So far so good, except that when a user attempts to open the app, they are prompted to provide credentials to create a connection to the HTTP Azure with AD connector, but this connector is not included in the app. Any ideas why? This is impacting the go-live of a solution and I cannot find any reference materials to explain why this might be a problem, given our config.

Was this reply helpful? Yes No
cornelco 4 on at

Like (0)

Report

Is the Azure HTTP Connection that you set as the run only users shared with the users that are running the Power App?

Also, is your Flow triggered from the Power App? Or when an item is added to a Dataverse table?

You could also check the dependencies on your Power App to see if it is dependent on the HTTP with Azure AD connection.

Was this reply helpful? Yes No
yousefhamedi 2 on at

Like (0)

Report

if you are using PowerApps action to connect your flow to Power Apps, you will have this problem. When sharing the flow, you won't be able to add "run only" users if using PowerApps action. Make sure to use PowerApps(V2) instead. I spent quite a bit of time on this issue and this information was not available on Power documentation (not a surprise I guess!), so wanted to share and hopefully save time for others!

Was this reply helpful? Yes No
Jurbe48 18 on at

Like (0)

Report
Hi,

I came across this post as I was having the exact same issue. However it seems I managed to overcome it.

My case:

In a canvas app users needed to fetch client information

Client information was exposed via an on premise REST service

The rest service could be approached by a technical user account (which we cannot share with end-users) using basic authentication and the on premise data gateway

The issue & solution:

I first created a custom connector and used it in the canvas app directly => End-users got the prompt to create the connection and log on (NOK)

In my second attempt I created a Power Automate flow, the flow called the REST service via the HTTP with Entra Id action using the gateway. The flow responded back to the canvas app => End-users still received the prompt to create a connection, also when I configured the flow to use the run-only connection of the technical account (NOK)

In my last attempt I used a combination of the two above, I kept the flow but instead of using HTTP with Entra Id I used the custom connector in the flow. I configured the flow to use the connection of the technical account (run-only users) => When opening the app, users where not prompted anymore to authenticate to the REST service as it used the connection of the technical account, not the end-user

I'm not sure if this would work in all other scenario's. With trial and error this was my most valable solution.

Was this reply helpful? Yes No