# Azure Integrated HSM reaches GA on selected AMD v7 VMs > The same-node hardware cache and crypto offload is generally available for Windows Trusted Launch guests on selected AMD D- and E-series v7 VMs with at least 8 vCores. Canonical URL: https://www.devobs.io/news/news-azure-integrated-hsm-amd-v7-ga/ By: Amara Okafor Published: 2026-09-06T11:58:54.638Z Updated: 2026-09-06T11:58:54.638Z Event date: 2026-05-13 Section: Security Azure Integrated Hardware Security Module became generally available on May 13 for Windows guests using Trusted Launch on selected AMD D- and E-series v7 virtual machines with at least 8 vCores. Linux support was still described as coming soon. The [Compute announcement](https://techcommunity.microsoft.com/blog/azurecompute/announcing-the-general-availability-of-azure-integrated-hardware-security-module/4517103) describes Integrated HSM as an ephemeral hardware-backed cache and cryptographic offload. Microsoft embeds the HSM chip in the server and performs supported operations locally on the same node as the VM, while key material remains inside the hardware boundary rather than guest memory. ## A cache changes key-path engineering Putting an HSM-backed cache with the VM can reduce repeated remote key-service work for supported cryptographic operations. “Ephemeral” is the key design word: teams should assume cached state can disappear with lifecycle events and ensure authoritative key material and recovery procedures live in the supported management path. The feature's availability on AMD v7 families also couples adoption to VM choice, region, guest support, and the exact cryptographic integration. General availability means Microsoft supports the released capability; it does not make every library or key workflow compatible. ## Prove lifecycle behavior Begin with a documented key hierarchy and threat model. Verify the chosen AMD v7 size and region support Integrated HSM, then follow Microsoft’s enablement path in a nonproduction workload. Measure key-operation latency and application throughput with realistic concurrency instead of extrapolating from a microbenchmark. Exercise reboot, redeploy, scale-out, host repair, and disaster recovery. Confirm applications reacquire usable key state without manual copying and fail closed when attestation or initialization cannot complete. Audit who can enable the feature, assign its resources, and access the upstream key system. For regulated systems, obtain the applicable certification and service-scope evidence rather than treating a boundary label as blanket compliance. Deployment records should identify the VM series and feature configuration so reviewers can reproduce the security claim. ## Source references - -