Logic app fails to connect to Azure VM citing expired token, but the connection in Config is shown as OK

@Sergey Borovoy

Thanks for reaching out.

The error you're encountering — "ExpiredAuthenticationToken" — typically indicates that the access token used by the Logic App to connect to the VM has expired. While the connection shows as "Connected" in the portal, this status reflects the last successful authentication and does not necessarily indicate that the authentication token is still valid.

To resolve this, you can refresh the token by re-authenticating the connection :

• Go to the Logic App’s Connections.
• Click on the azurevm connection.
• Select Edit API Connection and sign in again.
• Save the connection.

This should update the token and allow the Logic App to run successfully.

@Sergey Borovoy

Just checking in to see if the issue with the Logic App connecting to the VM has been resolved, or if you're still experiencing the error.

Let me know if you need any further assistance—happy to help

Hello Sai Prabhu Naveen Parimi, and thanks a lot for your reply.

Yes, this was my initial idea but my problem was that the connection, as shown on the screenshot above, was not clickable.

But your reply gave me the idea to go to the Logic App -> Developer Tools -> API connection -> General, and there I finally saw that "Edit API connection". Thanks a lot!

Interestingly, there is this documentation article that says that Logic Apps are supposed to refresh the tokens automatically: https://learn.microsoft.com/en-us/power-apps/maker/canvas-apps/working-with-tokens?source=recommendations#refresh-tokens-in-power-apps-logic-apps-and-power-automate I am wondering why this did not happen in my case.

Do you perhaps know how to deal with this in the future? I think this token will expire again in 2 years and the VM will fail to start again without warning. Is there any way to make the connection inform me of approaching token expiration? I tried setting up an Alert but I do not see the right signal. The signals are just "log search" and "activity log", nothing about token expiration:

@Sergey Borovoy

Thanks for the update, and glad to hear that you found the workaround via the Developer Tools → API connection section — great call on digging into that!

Regarding the automatic token refresh: yes, I’ve seen that article as well, and it does mention that Logic Apps are supposed to handle token refresh internally. However, this behavior can vary depending on the type of connection and authentication method used. For example, with service principal–based connections, the token can expire silently without triggering a refresh.

To avoid this kind of issue going forward, I’d recommend using a Managed Identity for the Logic App to connect to the VM, if possible. Managed Identity doesn’t rely on long-lived tokens or secrets and is automatically handled by Azure, which eliminates the risk of token expiration like this.