Power Automate

Power Automate Flow picking up wrong Connection despite correct Connection Reference

(0) Share

Report

Posted on by CT-10121437-0

Hi all,

Context:

I have set up 2 'HTTP with Entra ID' connectors, each of them connecting to a different Azure Function. Thus, they're Base URL and App ID (i.e., the 2 parameters which need to be provided to set this connector up) are different.
I have created a solution with a connection reference for each of the above mentioned connectors.
In the same solution, I have a Power Automate Flow, configured to use one of these connection reference through a 'HTTP with Entra ID' action.
This Power Automate flow is built to trigger a function found under the connection's base URL.

Issue:

When triggering the Power Automate Flow, I get an error, stating that the URL of the function I want to trigger does not match with the base URL configured for this 'HTTP with Entra ID' action.
I see that the base URL referenced in the error message, is that of the OTHER 'HTTP with Entra ID' connection I created in the same environment.
In my solution's connection reference, I see that the correct connection is configured + In my Power Automate flow, I see that the right connection reference is used.

What I tried:

I assumed Power Automate is mixing up both connections, an assigning the wrong connection to my connection reference, as the two connections have the same name (only the connection reference name can be changed); so, I created both connections with different accounts (the connections are named after the account which created them). This did not change anything.

Any advice? Thanks!!!

Categories:

Building flows

I have the same question (0)

All responses (2)

Answers (0)

Suggested answer

SwatiSTW 796 Super User 2025 Season 2 on at

Like (0)

Report
Copy link

Link copied!
It's likely that the problem has to do with how Power Automate maps and caches link references within a solution. Try below steps for troubleshooting and possible solutions for this issue-

Open your solution in Power Automate.

Check the "Connection References" section and confirm each reference is linked to the correct connection.

In your flow, find the action using the "HTTP with Entra ID" connector.

Temporarily change the connection reference to another one, save the flow, then switch it back to the correct connection reference and save again.

Rename the connections in Power Automate or Azure Portal to make them unique (e.g., Function1_Connection and Function2_Connection).

Delete unused or duplicate connections in the Power Automate "Connections" section.

If the issue still happens, export your solution, import it into a new environment, and create fresh connection references linked to unique connections.

Test each connection separately in its own flow to confirm they work as expected.

Was this reply helpful? Yes No
THenchoz 9 on at

Like (0)

Report
Copy link

Link copied!

Hi,

I've met the same issue recently, and did figure something out. It seems that Power Automate recognize only one connection reference of any kind per flow. That means, doesn't matter if you add two different connection reference for two different action in the same flow, it will use only one of them (still can't figure out which one thought).

Work around : split your flow in two (or more) and use the "call a child flow" action (all flows must be in the same solution), and use a different connection reference for each flow. This is working fine.

I hope I was able to help

Best

Was this reply helpful? Yes No