The Identity option is not displayed on the Container Instance page

Dev SS 120 Reputation points
2026-07-16T09:52:12.7466667+00:00

Hello,

For one of my Azure Container Instances, the Identity option is not displayed in the left-hand menu, as shown in the screenshot below.

For another container instance, the Identity option is displayed.

I access both container instances with the same Azure RBAC permissions, although they belong to different Microsoft Entra tenants.

Could you explain what conditions or configuration differences determine whether the Identity option is available?

Thank you.

User's image

User's image

Azure Container Instances
0 comments
Answer accepted by question author
Jose Benjamin Solis Nolasco 12,026 Reputation points Volunteer Moderator
2026-07-16T11:36:22.5633333+00:00

Welcome to Microsoft Q&A

Hello @Dev SS I hope you are doing well.

The Identity blade is only available for Azure Container Instances that support Managed Identities. If it is missing for one of your container instances, it is usually due to the resource configuration rather than your Azure RBAC permissions.

Please check the following:

API version and deployment date: Older Azure Container Instance deployments may have been created using an API version that did not include managed identity support. Recreating the container group with a newer API version may expose the Identity option.

Region support: Verify that the region where the container instance is deployed supports managed identities for Azure Container Instances.

Resource type: Ensure both resources are Azure Container Instances (Microsoft.ContainerInstance/containerGroups) and not different resource types with similar names.

Microsoft Entra tenant and Azure Policy: Since the two container instances are in different Microsoft Entra tenants, compare whether Azure Policies or governance controls are affecting the resource configuration or portal experience.

Azure Resource Provider: Confirm that the Microsoft.ContainerInstance resource provider is registered in the subscription.

You can also verify whether the resource has an identity configured by using Azure CLI:

az container show \

--resource-group <resource-group> \

--name <container-group-name> \

--query identity

  • If the command returns an identity object, the resource has a managed identity configured.

If it returns null, the container group was created without a managed identity.

If both container instances are running in supported regions and the Identity blade is only missing for one of them, please share:

The region of each container instance.

Whether they were created through the Azure portal, ARM/Bicep, Terraform, or Azure CLI.

The API version used (if known).

This will help determine whether the difference is due to the deployment configuration or a tenant-specific limitation.

References

Azure Container Instances managed identities:

https://learn.microsoft.com/azure/container-instances/container-instances-managed-identity

Azure Container Instances overview:

https://learn.microsoft.com/azure/container-instances/container-instances-overview

If my answer helped you, please consider marking it as accepted. This helps others in the community find similar solutions.

Was this answer helpful?

1 person found this answer helpful.
Answer accepted by question author
Marcin Policht 105.9K Reputation points MVP Volunteer Moderator
2026-07-16T11:17:58.7066667+00:00

Check the OS of the container. Managed identities (both System-Assigned and User-Assigned) are fully supported for Linux containers and the Identity option will be visible under the Settings group in the Azure Portal. Azure Container Instances does not support managed identities for Windows containers

If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.

hth

Marcin

Was this answer helpful?

1 person found this answer helpful.

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Saraswathi Devadula 16,040 Reputation points Microsoft External Staff Moderator
    2026-07-16T11:44:17.9333333+00:00

    Hello Dev SS

    According to Microsoft documentation, Azure Container Instances (ACI) support managed identities at the container group level, including both system-assigned and user-assigned managed identities.

    Windows Container Instances now support managed identity assignment. However, identity blade is disabled in portal and there are slight differences in features supported.

    The missing Identity blade is related to the ACI portal experience and not to a setting inside the Windows container or container host.
    https://learn.microsoft.com/en-us/azure/container-instances/container-instances-managed-identity

    This is an ongoing issue and the ETA for mitigation is end of July.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.