A glowing cloud-security graphic shows protected servers and a verified software deployment pipeline.
Windows node pools on Azure Kubernetes Service (AKS) can now use Trusted Launch, and the feature is in public preview. Microsoft's Azure Updates entry is dated November 17, 2026. It says Windows Server 2025 nodes get Secure Boot and vTPM-backed measured boot, so the node VMs can check signed boot components and report boot-integrity signals. The same day, a Microsoft AKS roadmap item on GitHub moved to "Public Preview." Its comment lists the requirements, and Microsoft's Learn documentation covers the same ground. Here is what that means for Windows operators on AKS, with the preview caveats up front.

A glowing cloud-security graphic shows protected servers and a verified software deployment pipeline. What changed​

Trusted Launch was previously supported only for Linux node pools in AKS. A GitHub feature request for Windows support had been open for a long time. The new preview closes that gap for one specific case: Windows Server 2025 node pools.

Trusted Launch combines two controls for Generation 2 VMs:

  • Secure Boot sits in the platform firmware. Per Microsoft Learn, every OS boot component (boot loader, kernel, kernel drivers) must be signed by a trusted publisher. If Secure Boot can't authenticate an image, the VM isn't allowed to boot.
  • vTPM is a virtual TPM 2.0 that measures the whole boot chain: UEFI, OS, system components and drivers. The cloud uses those measurements for remote attestation and health checks. If a check fails, Microsoft Defender for Cloud raises integrity alerts that say which components failed.

The announcement frames the goal as a more trusted Windows host baseline. That means less exposure to bootkits, rootkits and low-level malware without leaving the AKS node pool model. Treat that as risk reduction, not immunity. Boot-chain protection doesn't secure your container images, your cluster RBAC or your application code.

Preview requirements​

Microsoft's Learn page and the AKS roadmap comment give the same list. A Windows node pool with Trusted Launch needs all of these:

  • The WindowsTrustedLaunchPreview feature flag registered on your subscription.
  • Kubernetes 1.32 or later.
  • osType: Windows and osSKU: Windows2025.
  • Virtual Machine Scale Sets. Availability sets aren't supported.
  • An x64 VM size that supports Generation 2 and Trusted Launch.
  • FIPS enabled when you create the node pool. Learn notes that Windows Server 2025 enables FIPS by default, and the CLI flow uses --enable-fips-image.

Some older documentation and search snippets still say Windows Server node pools aren't supported. That text predates this preview. The current Learn page has a dedicated Windows section.

How to try it​

The Learn page describes this flow for a non-production test cluster. Check the live page for exact commands before you run anything.

  • Start with an existing cluster that is configured for Windows node pools, including a Windows profile and Azure CNI networking.
  • Register the WindowsTrustedLaunchPreview feature flag on the subscription, and refresh the Microsoft.ContainerService provider registration.
  • Use Azure CLI 2.87.0 or later for the Windows Server 2025 procedure. For the Bicep example, Learn lists Bicep CLI 0.42.1 or later.
  • Add the node pool with az aks nodepool add. Set the Windows OS type and Windows2025 SKU, enable vTPM and Secure Boot, and enable the FIPS image. Pick a Generation 2 VM size that supports Trusted Launch and is available in your region.
  • Alternatively, use an ARM template or Bicep file. Learn's Bicep example targets API version 2026-08-01. During preview, Bicep may show warning BCP081 because its type catalog lacks that API version. Learn says this only stops validation and doesn't block compiling or deploying.
  • Verify the result with az aks nodepool show and confirm that FIPS, Secure Boot and vTPM all read true.
  • Clean up by deleting only the test node pool. Don't delete node pools that host workloads you need.

Tooling limits​

Learn says the Azure portal and the AzureRM Terraform provider don't support Trusted Launch node pool settings. Use the CLI, ARM or Bicep. If your Windows node pools are managed through Terraform, expect some friction.

Preview caveats​

  • Not for production. Microsoft's AKS preview terms say previews are provided "as is" and "as available." They're excluded from SLAs and get best-effort support. Azure Updates also defines "In preview" as for non-production use and testing.
  • Windows Server 2025 only. Windows Server 2022 and earlier aren't covered. Separately, Learn's Node Auto-Provisioning documentation says the Windows2022 image family doesn't support FIPS or Trusted Launch.
  • FIPS is mandatory. Check that your Windows workloads work on FIPS-enabled nodes before you assume a clean migration. This is the most likely compatibility snag, and I'd test it first. That is my own inference, not a Microsoft finding.
  • Secure Boot failures. Learn's Linux guidance warns that nodes may not start if boot components aren't signed. The announcement doesn't say whether Windows nodes need similar troubleshooting, so test drivers and custom node images early.
  • Unpublished details. The announcement doesn't give a regional availability list, a general availability date or a retirement schedule.

Why it matters​

Windows containers on AKS are often the lift-and-shift path for .NET Framework and legacy apps. Many of those apps sit in regulated environments. Until now, security teams could harden Linux nodes with Trusted Launch but not Windows ones. Closing that gap simplifies compliance conversations. It also makes Defender for Cloud integrity alerts a possible signal across mixed-OS clusters.

Two related facts add context. AKS release notes say Windows Server 2025 is now generally available for node pools, with no feature flag needed. They also say Trusted Launch can be enabled and disabled on existing Linux node pools. Windows Trusted Launch is currently creation-time only in the Learn documentation, since the enable-on-existing-pool section covers Linux.

What to do now​

  • If you run Windows on AKS, put Windows Server 2025 with Trusted Launch on your test plan. Start with a throwaway node pool.
  • Check your Windows Server 2022 retirement timeline. Learn lists its retirement as June 30, 2028, so a move to 2025 is coming anyway. Trusted Launch is one more reason to rehearse it.
  • Don't plan production rollouts until Microsoft announces general availability and publishes the support matrix.

In short, this is a real and useful security step for Windows Kubernetes hosts. For now it's a test-bench feature with a clear recipe and a few sharp edges.


Correction (November 17, 2026): An earlier version of this article said Microsoft Learn lists the Windows Server 2022 retirement on AKS as March 15, 2027. That date is outdated: Learn now lists June 30, 2028, with Windows Server 2022 unsupported in Kubernetes 1.37 and later. The article now says so.

 

References

  1. (In preview) Public Preview: Windows Trusted Launch Azure Updates 2026-11-17T20:00:32Z
  2. (Feature) Windows Trusted Launch · Issue #5903 · Azure/AKS · GitHub github.com
  3. (Feature) Trusted Launch for Windows node pools · Issue #4369 · Azure/AKS · GitHub github.com