404 Error from token exchange on Update from Logic App with Service Principal

Rob Joosen 86

Suddenly my logic apps give these problems:

{
"status": 404,
"source": "https://logic-apis-westeurope.token.azure-apim.net:443/tokens/logic-apis-westeurope/commondataservice/<<GUID>/exchange",
"message": "Error from token exchange: The connection (logic-apis-westeurope/commondataservice/<<GUID>>) is not found. Please create new connection and change your application to use the new connection."

Is have re-created the connection several times but this problem keeps popping up. The strange thing is taht it appears on the Dataverse Update Connector, but not on the Dataverse Trigger.

}

Any ideas?

MayankBargali-MSFT 70,536 Reputation points

2022-12-07T07:25:07.65+00:00

@Rob Joosen Thanks for reaching out. As per the error it looks like the stale/deleted connection is still getting picked up as you are getting 404 error for the commondataservice Guid ID connection. The issue should be automatically mitigated if the connection is reconfigured correctly and saved. Can you please confirm try one more time to recreate the connection again and confirm if you are still facing the issue?
In case if you are still facing the issue then I can connect with you offline to assist you further.
Rob Joosen 86 Reputation points

2022-12-07T09:00:59.387+00:00

Hi, thanks for your reply. I recreated the connection again several times, but the issue remains. I would apprceiate some help yes.
Joana Rebelo 0 Reputation points

2023-03-14T11:17:29.95+00:00

Hey, was this sissue resolved?
Joana Rebelo 0 Reputation points

2023-03-14T17:59:16.8+00:00

Ok so crazy as it sounds, I found out that there were 2 reasons for this step in the logic app to not work:

1st - the user on the API connection needs to have contributor access to the API connection

2nd - the trigger you are using might have been updating and causes malfunctioning on the last step of the logic app (for ex. I was using a sharepoint trigger for "When a file is created or modified in a folder" that got updated to "
When a file is created or modified (properties only)". So the logic app only stopped failing and giving "connection not found" error after changing the trigger)
Robin Klimonow 10 Reputation points

2023-03-22T14:07:50.62+00:00
Hi Joana,

I am experiencing a similar issue, although it seems to be a little bit different, because in my logic app I have a trigger (Service Bus: When a message is available on topic subscription (peek lock)), and a "Complete message in topic subscription" action. Both use the same service bus connection.

The trigger actually fires, so the connection should actually be fine. It's the "Complete message" action which then says 404: connection not found.

Since you seem to have resolved it, I just want to ask some questions as your response isn't quite clear to me.

the user on the API connection...
which user do you mean? Do you mean the service principal of the logic app? I already added an access policy, but this did not make the service principal of the logic app a contributor. Do you mean I need to make the service principal a Contributor directly as well?

What do you mean by "after changing the trigger"? What did you do exactly to make the error disappear?
Luc Bergeron 11 Reputation points

2023-05-16T18:39:16.4133333+00:00

If it can help anyone looking at this thread. We were facing this issue; creating a new connection or using another trigger did not solve it.

For an unknown reason, we discovered that the connectionRuntimeUrl in the Logic App Connection JSON View was not matching the API connection connectionRuntimeUrl.

I copied the connectionRuntimeURL from the API Connection, and updated the connectionRuntimeUrl in the Logic App Connections JSON View, saved it, and logic app started working.

We cannot explain how we get in this situation, but at least we've been able to solve it!
Sushant Sikare 0 Reputation points

2023-08-22T06:48:53.97+00:00

Thanks @Luc Bergeron

I am having same issue while deploying logic app standard to prod through ADO and faced same issue with azure tables API connection

did the same this you mentioned and it worked, would like to know what exactly happens behind the scene why this is necessery and why don't they mention these things in docs.
Alberto Matute Beltran 0 Reputation points

2023-12-06T18:11:19.9333333+00:00

I found out that even if you delete and create a new connection the connectionRuntimeUrl remains as it was for the old connection (as Luc Bergeron already mentioned), you need to check the properties of your api connection, copy the connectionRuntimeURL and paste it in the JSON View of the connections in the logic app under the affected connection, at least that is how I fixed it.

2 answers

Sonny Gillissen 3,351 Reputation points

2023-07-12T20:38:58.79+00:00

Hi Rob Joosen

Thank you for reaching out on Microsoft Q&A!

I’ve seen this behaviour before when something happened with the connection file, like redeployment or recreation. This is due to caching. Even though the Logic App has the same configuration file name, it doesn’t see it as being the same (so the old one isn’t automatically replaces with the new, even thought the name is the same).

To mitigate this issue it helped me to go into the Logic App, change a value so the save button lit up, then changed the value back to what it was before and save again. This wat the cache got flushed and the connection started working again.

Recreating the connecting isn’t helping, so “tricking” the Logic App is the way to “reconnect” them.

Please click “Accept answer” if you find this helpful. Feel free to drop additional queries in the comments below!

Kind regards,

Sonny
Please sign in to rate this answer.

2 people found this answer helpful.
Himanshu Punjabi 0 Reputation points

2023-10-04T18:51:51.2266667+00:00

The solution by Sonny Gillisen worked for me! Thank you so much.

Alessandro Pantano 0 Reputation points Microsoft Employee

2024-09-19T13:23:56.3533333+00:00

Had the same issue caused most probably by multiple ARM redeployment.
I resolved exactly as Sonny explained.
In my case I was using the File Adapter and simply toggled a trailing / char and then restored on the folder source parameter made my trigger working again.
Neither recreating the connection with a different name or removing all connections and logic app itself ever worked.
Many thanks!!
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Thomas Welén 0 Reputation points

2023-07-12T19:19:21.66+00:00

I had the same issue and the solution for me was to rename the API connection (deletion of old one and create a new one with another name, via terraform). I had a blob-connection with the same name present earlier in another resource group that was deleted before the new one was created, but this may have been the issue, some sort of caching perhaps
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

404 Error from token exchange on Update from Logic App with Service Principal

2 answers

Your answer