Blog Post

Microsoft Security Community Blog
4 MIN READ

Secure by default: Trusted Launch as Default is now Generally Available

EllaHassan_MSFT's avatar
Aug 03, 2026

We are excited to announce that Trusted Launch as Default (TLaD) is now Generally Available for new Azure Generation 2 (Gen2) virtual machines (VMs) and virtual machine scale sets. With this milestone, new Gen2 deployments come up with Secure Boot and a virtual Trusted Platform Module (vTPM) enabled out of the box—raising the security baseline of your fleet automatically, and at no extra cost. TLaD is the default already for Portal, Powershell and CLI and now requires one-time registration to enable it by default for deployment scripts or tooling like ARM templates, Bicep, Terraform, or SDKs. 

What is Trusted Launch? 

Trusted Launch is a set of coordinated, foundational security technologies for Gen2 Azure VMs that protect against advanced, persistent threats—bootkits, rootkits, and kernel-level malware. Its core building blocks are: 

  1. Secure Boot – ensures only signed, trusted OS boot components (boot loader, kernel, drivers) can run, establishing a root of trust for your VM.
  2. vTPM – a dedicated, isolated TPM 2.0 instance that safeguards keys, certificates, and secrets, and enables remote attestation of your VM's boot integrity.
  3. Boot integrity monitoring with Microsoft Defender for Cloud – continuous attestation, health assessments, and alerting when a VM's boot state deviates from a trusted baseline. 

Trusted Launch is supported on both x64 and Arm64 Gen2 sizes, across all public, Azure Government, and Azure China regions. 

What is Trusted Launch as Default (TLaD)? 

It is a fast, light weight way to improve the security posture of your new deployments without changing how you deploy. 

Two important guarantees: 

  1. TLaD only affects new deployments. Existing VMs and scale sets already running in your environment are untouched.
  2. TLaD never overrides your inputs. If your template or script explicitly sets a securityProfile, that value is always honored. 

What's new at General Availability 

TLaD is now fully supported for production use. Here's how the default applies across the tools you already use: 

Deployment surface 

Behavior at GA 

Azure portal, Azure CLI, Azure PowerShell 

New Gen2 VMs and scale sets default to Trusted Launch automatically—no registration required. 

ARM templates, Bicep, Terraform, Azure SDK 

New Gen2 VMs and scale sets default to Trusted Launch once you register your subscription for the feature. 

In short: interactive tooling is secure by default today, and you can extend the same default to your infrastructure-as-code and SDK-based pipelines with a one-time subscription registration. 

How to enable TLaD for ARM, Bicep, Terraform, and the SDK 

To make Trusted Launch the default for deployments created through ARM templates, Bicep, Terraform, or the Azure SDK, register the TrustedLaunchByDefaultPreview feature under the Microsoft.Compute namespace on your subscription. 

For more information, see Set up preview features in an Azure subscription. 

💡 Note: Azure portal, CLI, and PowerShell deployments default to Trusted Launch regardless of whether the feature is registered. Registration is what extends the default to ARM/Bicep/Terraform/SDK deployments. 

How the default behaves 

Once your subscription is registered, run your existing deployment scripts and templates as-is. When you use Microsoft.Compute API version 2025-11-01 or higher, the absence of a securityProfile element in your deployment enables Trusted Launch by default for a new VM or scale set—provided all of the following are true: 

  • The source Marketplace OS image supports Trusted Launch. 
  • The source Azure Compute Gallery (ACG) image supports and is validated for Trusted Launch. 
  • The source disk supports Trusted Launch. 
  • The VM size supports Trusted Launch. 

If one or more of these conditions isn't met, the deployment completes successfully as a Gen2 VM or scale set without Trusted Launch. 

Need to opt out a specific workload? 

We strongly recommend keeping Trusted Launch enabled—it's foundational compute security at no extra cost. If a specific workload has a dependency that isn't compatible (for example, an unsupported VM size, an unsupported feature such as managed images or Linux hibernation, or an OS that doesn't support Trusted Launch), you can explicitly opt out that deployment out by setting the securityType parameter to Standard. 

Things to know 

  • No additional cost. Trusted Launch doesn't increase your VM pricing. 
  • Your existing resources are safe. TLaD applies only to new deployments; running VMs and scale sets aren't changed. 
  • Your code wins. An explicit securityProfile in your deployment always takes precedence over the default. 
  • Broad coverage. Available across all public, Azure Government, and Azure China regions, on both x64 and Arm64 Gen2 sizes. 
  • To turn the default off for ARM/Bicep/Terraform/SDK deployments, unregister the TrustedLaunchByDefaultPreview feature under Microsoft.Compute. (Portal, CLI, and PowerShell continue to default to Trusted Launch regardless.) 

Get started 

We want your feedback 

Every new Gen2 VM you deploy now starts from a stronger security posture—automatically. That's secure by default, and it's here today. 

Have a question for the community? Drop a comment below—we're reading. 

Updated Jul 31, 2026
Version 1.0
No CommentsBe the first to comment