Protecting your data is important. Protecting your ability to recover it is just as critical.
Ransomware attacks are becoming increasingly sophisticated. Attackers no longer focus only on encrypting or stealing production data. They also target backups, knowing that eliminating an organization's recovery options can turn a security incident into a prolonged business disruption.
Imagine discovering that your database has been compromised, only to find that the backups you were counting on have also been deleted. Even with a comprehensive backup strategy, recovery becomes significantly more challenging when attackers can tamper with the very data needed to restore business operations.
That's why backup immutability matters.
We're continuing to strengthen data protection in Azure SQL Database and Azure SQL Managed Instance with a consistent set of backup immutability capabilities spanning both point-in-time restore (PITR) and long-term retention (LTR) backups.
Whether you're protecting recent transactions, maintaining historical backups for years, or preserving data for regulatory requirements, Azure SQL provides multiple layers of protection to help ensure your recovery points remain available when you need them most.
What makes immutable backups different?
Traditional backup retention policies define how long backups should be kept. But retention alone doesn't necessarily prevent someone with sufficient privileges from deleting backups before they expire.
Backup immutability adds another layer of defense.
With immutability, protected backups cannot be modified, overwritten, or deleted during their immutability period, even by administrators with elevated privileges.
This is particularly valuable when attackers gain access to privileged accounts. While compromised credentials may allow attackers to disrupt production environments, immutable backups help prevent them from destroying protected recovery points.
Think of it as adding a safety barrier around your backups, one that helps preserve your ability to recover even when other defenses have been compromised.
1. Built-in protection for your recent backups, automatically
One of the simplest ways to improve security is to make protection automatic.
Azure SQL Database and Azure SQL Managed Instance now provide immutable protection for up to the most recent seven days of PITR backups by default.
The best part? There's nothing you need to do to get started.
- No additional configuration.
- No separate storage accounts to manage.
- No immutability policies to create.
- No changes to existing backup and restore workflows.
- No additional charge for the default immutability protection.
This capability is integrated directly into the Azure SQL managed backup service.
For customers, that means an additional layer of protection is already working behind the scenes, helping safeguard recent recovery points against accidental deletion, malicious activity, and compromised administrative credentials.
Whether you're running a business-critical application or a smaller operational database, this built-in protection provides a stronger starting point for your recovery strategy.
2. Need longer protection? Lock immutability to your PITR retention period
Seven days of automatic protection is a great starting point, but every organization has different recovery requirements.
Some businesses need additional time to detect security incidents, investigate suspicious activity, and determine when their data was last known to be healthy.
For these scenarios, Azure SQL offers the option to extend immutable protection across the entire configured PITR backup retention period, up to 35 days where supported.
For example, if your database is configured to retain 35 days of PITR backups, you can lock immutability to that retention period, protecting those recovery points against deletion or modification.
Once enabled, the lock is permanent. The configured retention period can be increased, but it cannot be shortened.
This provides an important safeguard against attempts to weaken backup protection, including those made using compromised administrative credentials.
With this capability, organizations can align their backup protection with their recovery requirements, rather than relying solely on the default protection window.
The experience is consistent across Azure SQL Database and Azure SQL Managed Instance, making it easier to establish a common data protection strategy across your Azure SQL environment.
3. Protect your long-term backups for years, not just days
Recovering from a recent incident is only one part of a comprehensive data protection strategy.
Many organizations also need to preserve historical backups for business continuity, regulatory compliance, internal governance, or audit requirements.
Azure SQL long-term retention (LTR) supports retaining backups for up to 10 years.
With LTR backup immutability, customers can go beyond simply retaining those backups and protect them against unauthorized modification or deletion.
Time-based immutability allows organizations to specify how long backups must remain protected.
Once immutability is enabled and locked, affected backups cannot be deleted until their retention period expires, even if an administrator later changes or removes the retention policy.
Consider a financial services organization that needs to preserve database backups for seven years. By configuring locked time-based immutability, the organization can help ensure those backups remain protected throughout the required retention period.
The same approach is valuable for healthcare organizations, enterprises with strict governance requirements, and businesses seeking additional safeguards against ransomware.
With a consistent LTR immutability experience across Azure SQL Database and Azure SQL Managed Instance, customers can apply the same protection principles regardless of which service hosts their databases.
4. Preserve critical backups with legal holds
Not every data preservation requirement has a predictable end date.
An organization may need to retain a specific backup while responding to an audit, conducting an internal investigation, or addressing a legal matter.
In these situations, a fixed retention period may not be sufficient.
Azure SQL LTR backup immutability also supports legal holds, allowing customers to protect specific existing backups until the hold is explicitly removed.
For example, if an organization needs to preserve a database backup associated with an ongoing investigation, it can apply a legal hold to prevent that backup from being deleted while the investigation continues.
Legal holds can coexist with time-based immutability, providing flexibility for organizations that need both predictable retention policies and event-driven preservation requirements.
This makes immutable backups valuable not only for ransomware resilience, but also for meeting evolving business and governance needs.
5. Consistent protection across Azure SQL Database and Azure SQL Managed Instance
For organizations operating both Azure SQL Database and Azure SQL Managed Instance, consistency matters.
Security and compliance teams shouldn't have to build entirely different backup protection strategies depending on where a database runs.
With a consistent immutability experience across both services, customers can adopt a common approach to protecting recent and historical backups.
Here's how the capabilities work together:
| Capability | Customer benefit |
|---|---|
| Default PITR immutability | Automatic protection for up to seven days of recent backups |
| Locked PITR immutability | Extended protection aligned with configured PITR retention, up to 35 days |
| Time-based LTR immutability | Protect historical backups for their configured retention period, up to 10 years |
| LTR legal holds | Preserve selected backups until the hold is explicitly removed |
Together, these capabilities provide flexibility to address different recovery and retention requirements, from recovering a database to a recent point in time to preserving historical backups for years.
And because the protection is integrated into Azure SQL's managed backup experience, customers don't need to build or maintain separate immutable backup storage infrastructure.
6. Building a stronger defense against ransomware
Let's revisit a common ransomware scenario.
An attacker gains access to a privileged account and attempts to disrupt business operations by modifying production data and deleting available backups.
Without immutability, the attacker may be able to eliminate critical recovery options.
With immutable backups, the story changes.
- Recent recovery points are protected: Default PITR immutability helps preserve backups from the most recent seven days.
- Extended recovery history can be safeguarded: Locked PITR immutability can protect a longer recovery window, giving organizations more options when investigating an incident.
- Historical backups remain protected: Locked LTR immutability helps prevent attackers from deleting backups that organizations need to retain for months or years.
- Critical records can be preserved: Legal holds provide additional protection for specific backups that must remain available during investigations or audits.
While backup immutability doesn't prevent ransomware attacks or guarantee that every restore point is free from compromise, it makes it significantly harder for attackers to eliminate protected backups.
That distinction is important.
A strong ransomware recovery strategy isn't just about having backups. It's about being able to trust that your backups will still be there when you need them.
Immutable backups complement other security and resilience practices, including identity protection, least-privilege access, monitoring, appropriate backup retention, and regular recovery testing.
7. Get started with immutable backups in Azure SQL
Getting started is straightforward.
If you're using a supported Azure SQL Database or Azure SQL Managed Instance database, you already benefit from default PITR backup immutability for up to seven days.
From there, consider your organization's recovery and compliance needs:
- Review your PITR retention settings. Determine whether the default protection window meets your recovery objectives or whether you need a longer immutable retention period.
- Consider locked PITR immutability. For databases requiring extended protection, align immutability with your configured PITR retention.
- Evaluate your long-term backup requirements. Configure LTR immutability for backups that must remain protected for extended periods.
- Use legal holds when needed. Preserve specific historical backups for audits, investigations, or legal requirements.
- Test your recovery procedures. Validate that your organization can restore the right data when an incident occurs.
Before applying permanent retention locks, carefully evaluate your requirements, because locked protection cannot be removed early. Also remember that backup immutability protects backups, not the database resource itself, so resource deletion protection and recovery planning remain important.
Protecting your data. Preserving your ability to recover.
As cyber threats continue to evolve, organizations need confidence not only that their data is protected, but also that they can recover when something goes wrong.
With backup immutability spanning PITR and LTR backups across Azure SQL Database and Azure SQL Managed Instance, we're making it easier for customers to build stronger, more consistent data protection strategies.
From automatic protection for recent backups to long-term immutable retention and legal holds, these capabilities help organizations safeguard critical recovery points, reduce ransomware-related risks, and strengthen their overall resilience.
Because when the unexpected happens, the most important backup is the one you can still recover from.
Learn more:
- PITR backup immutability for both Azure SQL DB and Azure SQL MI - Automatic backup immutability for Azure SQL Database and Azure SQL Managed Instance - Azure SQL | Microsoft Learn
- Azure SQL DB LTR backup immutability - Backup Immutability for Long-Term Retention Backups - Azure SQL Database | Microsoft Learn
- Azure SQL MI LTR backup immutability - LTR backup immutability - Azure SQL Managed Instance | Microsoft Learn
My colleague SudhanshuKhera authored a comprehensive ransomware recovery plan for Azure SQL DB and Azure SQL MI - Overview: Recover Azure SQL Database and Azure SQL Managed Instance from a ransomware attack - Azure SQL Database | Microsoft Learn