InvalidAuthenticationTokenTenant on 2 VMSS after creating container

Question

Hi,

I was trying to deploy a container instance and it failed the first time. Don't remember why. Later, I managed to create it. I also created a separate virtual network for it with a new subnet. I also created an Application Gateway for Containers to expose it outside and get a fully qualified domain name. I got the FQDN but it didn't work. I will figure that out. My current problem is this.

In the virtual network I created, I see now 2 devices for which I am not able to see any details. I see an error which says

Details

resource Id: /subscriptions/

Answer 1

Hi Amrudesh Santhanam,

Welcome to the Microsoft Q&A Platform! Thank you for asking your question here.

It seems you're encountering the "InvalidAuthenticationTokenTenant" error after creating a container and VMSS. This usually indicates an issue with the authentication token, either due to a mismatch between the token's tenant and the resource's tenant or expired tokens. Here's what you can try:

Make sure you're using the correct tenant ID for your subscription and re-authenticate with:

az login --tenant <Tenant-ID>

Check if the token has expired and generate a new one if necessary.

Verify that the service principal or managed identity has the required permissions (like Contributor or Owner) on the subscription.

Review your virtual network, subnet, and Application Gateway configuration to ensure everything is correctly set up.

For more details, refer to this documentation: Resolve authentication and authorization errors in Azure.

If you have any further queries, do let us know. If the comment is helpful, please click "Upvote".