Hi Thea,
Thanks for your question on User-Assigned Managed Identities (UMIs) in Azure. Yes, it's technically possible for multiple UMIs to have the same name within a single tenant, as long as they are created in different resource groups—the name uniqueness is scoped to the resource group level, not the entire tenant or subscription. For example, you could have a UMI named "my-identity" in Resource Group A and another with the same name in Resource Group B.
To avoid duplicates and maintain clarity:
Use descriptive, unique names incorporating details like environment or purpose (e.g., "prod-app-identity-v1" instead of just "app-identity").
Organize UMIs into dedicated resource groups based on projects or teams to naturally prevent naming conflicts.
When creating via Azure CLI or PowerShell, check existing names in the target RG first with commands like az identity list --resource-group <group-name> to verify availability.
This approach leverages Azure's resource scoping while keeping things organized. If you're running into specific errors or need script examples for automation, feel free to share more details!
Best Regards,
Jerald Felix