Generated on: August 04, 2026 Target period: Within the last 24 hours Processing mode: Details Mode Number of updates: 2 items
Published: August 03, 2026 19:56:26 UTC Link: Generally Available: Trusted Launch as Default
Update ID: 568600 Data source: Azure Updates API
Categories: Launched, Compute, Virtual Machine Scale Sets, Virtual Machines, Features, Pricing & Offerings, Security
Summary:
What was updated
Trusted Launch as Default (TLaD) is now generally available for new Azure Generation 2 (Gen2) virtual machines (VMs) and virtual machine scale sets.
Key changes or new features
With this update, Trusted Launch is automatically enabled for all new supported Gen2 VMs and VM scale sets. This means Secure Boot and virtual Trusted Platform Module (vTPM) are activated by default, providing enhanced protection against bootkits, rootkits, and other advanced threats. Customers no longer need to manually configure these security features for new deployments.
Target audience affected
Developers, IT professionals, and cloud administrators who deploy or manage Azure Gen2 VMs and VM scale sets.
Important notes if any
Existing VMs are not affected; TLaD applies only to new deployments of supported Gen2 VMs and scale sets. Review your deployment templates and automation scripts to ensure compatibility with Trusted Launch defaults. For workloads requiring custom boot configurations or unsupported OS images, review Azure documentation for exceptions and opt-out options if necessary.
For more details, see the official update: https://azure.microsoft.com/updates?id=568600
Details:
Azure Update Technical Report: Trusted Launch as Default (TLaD) Generally Available
Background and Purpose of the Update:
The Trusted Launch as Default (TLaD) feature is now generally available for new Azure Generation 2 (Gen2) virtual machines (VMs) and virtual machine scale sets. The primary purpose of this update is to enhance the security posture of Azure VM deployments by automatically enabling advanced security features, specifically Secure Boot and virtual Trusted Platform Module (vTPM), for supported workloads. This update addresses the growing need for baseline security in cloud environments, reducing manual configuration steps and ensuring that new deployments are protected against common boot-level and firmware threats.
Specific Features and Detailed Changes:
With TLaD, Secure Boot and vTPM are now automatically enabled for all new Azure Gen2 VMs and VM scale sets where supported.
The update changes the default provisioning behavior for Gen2 VMs and VM scale sets, meaning customers no longer need to manually opt-in or configure these security features during deployment. This default setting applies only to new deployments; existing VMs are not retroactively affected.
Technical Mechanisms and Implementation Methods:
Trusted Launch leverages Azure’s hypervisor and underlying infrastructure to provide Secure Boot and vTPM support.
These mechanisms are integrated into the Azure Resource Manager (ARM) deployment process, ensuring consistency and reliability across supported regions and VM sizes.
Use Cases and Application Scenarios:
Important Considerations and Limitations:
Integration with Related Azure Services:
TLaD integrates seamlessly with Azure Security Center, Azure Policy, and Azure Management tools, enabling automated compliance checks and monitoring. Secure Boot and vTPM also enhance the effectiveness of Azure confidential computing and attestation services.
Summary:
Trusted Launch as Default is now generally available for new Azure Gen2 VMs and VM scale sets, automatically enabling Secure Boot and vTPM to provide a stronger security foundation for supported deployments.
Published: August 03, 2026 17:00:56 UTC Link: Generally Available: Immutability to the most recent seven days of backups on Azure SQL Database and Azure SQL Managed Instance
Update ID: 568339 Data source: Azure Updates API
Categories: Launched, Databases, Hybrid + multicloud, Azure SQL Database, Azure SQL Managed Instance, Feature
Summary:
What was updated
Azure SQL Database and Azure SQL Managed Instance now provide immutability for the most recent seven days of backups.
Key changes or new features
Immutability is automatically enforced on the latest seven days of backups for all databases, regardless of the configured point-in-time backup retention period. This means these backups cannot be modified or deleted, enhancing protection against accidental or malicious data loss (e.g., ransomware or insider threats). The feature is enabled by default and requires no manual configuration.
Target audience affected
Developers and IT professionals managing Azure SQL Database or Azure SQL Managed Instance environments, especially those with compliance, security, or data protection requirements.
Important notes if any
This immutability applies only to the most recent seven days of backups. It is automatically enabled and cannot be disabled or configured for a shorter period. Existing backup and restore operations are not impacted, but users should be aware that deletions or modifications to these backups within the seven-day window are not possible. For organizations with regulatory or compliance needs, this feature provides an additional layer of data protection by default.
Details:
Azure Update Technical Report
Title: Generally Available: Immutability to the most recent seven days of backups on Azure SQL Database and Azure SQL Managed Instance
Link: Azure Update
Background and Purpose of the Update
This update addresses the increasing need for enhanced backup protection in cloud database environments. Immutability is a critical feature for safeguarding backup data against accidental or malicious deletion, modification, or ransomware attacks. By making the most recent seven days of backups immutable, Azure aims to provide stronger data integrity and compliance with regulatory requirements for data retention and protection.
Specific Features and Detailed Changes
Azure SQL Database and Azure SQL Managed Instance now automatically enforce immutability on the most recent seven days of backups. This feature is enabled by default for all databases, irrespective of the configured point-in-time restore (PITR) settings. The immutability ensures that backup data cannot be altered or deleted during this seven-day window, providing a secure and reliable backup retention mechanism.
Technical Mechanisms and Implementation Methods
Immutability is implemented at the backup storage layer, leveraging Azure’s internal mechanisms to lock backup files for the specified period. Once a backup is created, it is marked as immutable for seven days, preventing any operations that could modify or delete the backup data. This is enforced automatically by Azure, requiring no manual configuration or intervention from users. The immutability applies to all backup types managed by Azure SQL Database and Azure SQL Managed Instance, including full, differential, and transaction log backups.
Use Cases and Application Scenarios
Important Considerations and Limitations
Integration with Related Azure Services
This update seamlessly integrates with existing Azure SQL Database and Azure SQL Managed Instance backup and restore workflows. It complements Azure’s built-in backup management, point-in-time restore, and long-term retention features. Immutability operates transparently alongside other Azure security and compliance offerings, such as Azure Backup, Azure Security Center, and Azure Policy, providing a holistic approach to data protection.
Summary Sentence:
Azure SQL Database and Azure SQL Managed Instance now automatically enforce immutability on the most recent seven days of backups, enhancing data protection by preventing modification or deletion during this period and supporting compliance, security, and reliable recovery scenarios.
This report was automatically generated - 2026-08-04 03:01:48 UTC