Automation Job Failing on "Unauthorized" error (InvalidAuthenticationTokenTenant)

Question

I recently changed the password for my Azure account. Soon after, I started getting the error below. I updated the connection and manually changed the subscription, but no luck.

{ "error": { "code": "InvalidAuthenticationTokenTenant", "message": "The access token is from the wrong issuer 'https://sts.windows.net/f8xxxxxxxxxxxx/'. It must match the tenant 'https://sts.windows.net/25xxxxxxxxxxxx/' associated with this subscription. Please use the authority (URL) 'https://login.windows.net/254xxxxxxxxxxxx' to get the token. Note, if the subscription is transferred to another tenant there is no impact to the services, but information about new tenant could take time to propagate (up to an hour). If you just transferred your subscription and see this error message, please try back later." } }

Answer 1

Hi @Ron de Frates

Thank you for reaching out to Microsoft Q&A.

As discussed on Teams, we have configured Managed Identity for your Logic App and assigned it Virtual Machine Contributor role on the VM or Subscription level which fixed the connection issue.

If the resolution was helpful, kindly take a moment to click on and click on Yes for was this answer helpful. And, if you have any further query do let us know.

Answer 2

The error message you're encountering, "InvalidAuthenticationTokenTenant," indicates that the access token being used is associated with a different Azure Active Directory (AAD) tenant than the one linked to your subscription. This often occurs after a password change or if there have been modifications to your account or tenant configuration.

Here are some steps you can take to resolve this issue:

1. Re-authenticate: Since you changed your password, ensure that all connections and tokens are updated. You may need to re-authenticate your Azure Logic Apps or any other services that rely on this token.
2. Check Tenant Association: Verify that your subscription is still associated with the correct tenant. If your subscription was recently transferred to another tenant, it might take some time for the changes to propagate.
3. Use the Correct Authority URL: Make sure you are using the authority URL specified in the error message (https://login.windows.net/2548c809-a5be-4fd8-ae10-88e8bd6f8ffa) to obtain a new token.
4. Wait for Propagation: If you recently transferred your subscription, wait for up to an hour for the changes to take effect and then try again.

If the issue persists after following these steps, you may need to contact your Azure administrator for further assistance.

---

References:

• Troubleshoot broken connections in Microsoft Power Platform
• Troubleshoot broken connections in Microsoft Power Platform
• Resolve free/busy errors
• Troubleshoot error codes during runbook execution in Azure Automation
• Invalid credentials error when running desktop flows in Power Automate for desktop