User Assigned Identity should have a valid principal
Medium
Azure
General
userassignedidentities-user-assigned-identity-vali
Applies to
Microsoft.ManagedIdentity/userAssignedIdentities
What CGPulse checks
A resource passes this rule when principalId must be set true. Anything else is reported as a finding with the evaluated property value attached as evidence.
How to fix it
Verify the user-assigned identity has a valid service principal in Azure AD. In Azure Portal: Managed Identities > select identity > verify principal. See: https://learn.microsoft.com/en-us/entra/identity/managed-identities-azure-resources/overview
CLI
az identity show --ids "{id}" --query "principalId" -o tsvBicep
resource userIdentity 'Microsoft.ManagedIdentity/userAssignedIdentities@2023-01-31' = {{
name: '{name}'
location: resourceGroup().location
}}Terraform
resource "azurerm_user_assigned_identity" "{name}" {
name = "{name}"
resource_group_name = "{rg}"
location = var.location
}
Compliance frameworks
Is your environment compliant with this rule?
CGPulse checks it — and 621 others — against your Azure and AWS accounts with read-only access.
Related Azure rules
- Action Group should be enabled
- Activity Log Alert should be enabled
- AKS cluster logs should be sent to Log Analytics
- AKS cluster must enable RBAC
- AKS cluster must enable RBAC
- AKS cluster should be a private cluster
- AKS cluster should disable local accounts
- AKS cluster should enable Azure RBAC for Kubernetes