VM Scale Set should use managed identity
High
Azure
General
virtualmachinescalesets-managed-identity
Applies to
Microsoft.Compute/virtualMachineScaleSets
What CGPulse checks
A resource passes this rule when identity.type must be one of ["SystemAssigned","UserAssigned","SystemAssigned,UserAssigned"]. Anything else is reported as a finding with the evaluated property value attached as evidence.
How to fix it
Enable managed identity to eliminate stored credentials and improve security. In Azure Portal: VMSS > Identity > enable System-assigned managed identity. See: https://learn.microsoft.com/en-us/entra/identity/managed-identities-azure-resources/qs-configure-portal-windows-vmss
CLI
az vmss identity assign --ids "{id}"Terraform
resource "azurerm_linux_virtual_machine_scale_set" "{name}" {
name = "{name}"
resource_group_name = "{rg}"
location = var.location
sku = "Standard_DS1_v2"
instances = 2
admin_username = "adminuser"
identity {
type = "SystemAssigned"
}
source_image_reference {
publisher = "Canonical"
offer = "0001-com-ubuntu-server-jammy"
sku = "22_04-lts"
version = "latest"
}
os_disk {
caching = "ReadWrite"
storage_account_type = "Standard_LRS"
}
network_interface {
name = "{name}-nic"
primary = true
ip_configuration {
name = "internal"
primary = true
subnet_id = azurerm_subnet.{name}.id
}
}
}
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