Your virtual machines deserve the same scrutiny as your identity tenant.
A virtual machine can sign in through Microsoft Entra ID with Conditional Access and PIM governing every login, Trusted Launch with Secure Boot and vTPM guarding the boot process, encryption at host covering what disk-level encryption doesn't, no public IP exposing it directly to the internet, and a pinned availability zone protecting it from a single-datacenter failure. Or it can be running with none of that: a Linux VM still accepting SSH password logins instead of key-based authentication, a Generation 1 image that can never gain Trusted Launch, a public IP open to the internet, and no zone assignment at all. Both configurations are silent on the surface -- the VM runs the same either way. ID Posture checks which one you actually have, VM by VM, across every connected subscription.
Six findings, checked on every scan
Ask your ID Posture contact to enable VM Security for your tenant.
Why it matters
Entra ID sign-in means every login to the VM is governed by the same Conditional Access, MFA, and PIM controls as everything else in your tenant, instead of a local account that lives entirely outside them. A Linux VM still accepting SSH password logins is exposed to brute-force and credential-stuffing attacks in a way key-based authentication isn't. Trusted Launch with Secure Boot and vTPM is the only thing standing between the VM and a boot-level attack that runs before the OS, and before any of its own controls, even start. Encryption at host closes the gap disk-level encryption leaves open: temp disks and host caches that would otherwise sit unencrypted. A public IP address puts the VM directly in reach of internet scanning and attack traffic on every open port, not just the ones you meant to publish. And an availability zone assignment is the only thing protecting it from a single-datacenter failure in the region. ID Posture checks all six on every scan.
Part of ID Posture's broader Azure resource coverage. See the full product overview, or explore AKS Security and Networking.
It's optional, per tenant, off by default until you ask for it, and doesn't affect your identity score. Checking it needs your Azure subscription connected: Reader is recommended, or the narrower Compute-only custom role works too.