Azure SQL Database and Managed Instance Preview Lets You Lock PITR Backup Immutability for Up to 35 Days

A new permanent lock extends immutable PITR backups in Azure SQL Database and Managed Instance beyond the default seven days to the full retention period.

Microsoft announced a public preview on November 3, 2026 that extends immutability for point-in-time restore (PITR) backups in Azure SQL Database and Azure SQL Managed Instance. Until now, the service protected only up to the latest seven days of PITR backups from change or deletion.

With the new option, you can tie immutability to your full configured PITR retention period, up to 35 days. The catch is that the lock is permanent: once it is on, retention can only grow. That makes this a feature for regulated workloads and ransomware defense, and one to plan carefully before turning on.

What Changed

Azure SQL already applies a default layer of immutability to recent PITR backups. This protection needs no setting and costs nothing extra, but it covers at most the newest seven days, even if you keep 35 days of restore points.

The preview adds an optional setting called Lock immutability to configured PITR backup retention period. When enabled, the protected window stretches to match the whole retention period you chose. Microsoft points to financial firms, which often keep 35 days of PITR history, as a main audience.

Key Rules of the Lock

The lock behaves very differently from most database settings. Microsoft's documentation lists these rules:

  • There is no unlock operation, and the setting stays on for the life of the database.
  • After locking, no tool, including the portal, CLI and PowerShell, will let you shorten PITR retention.
  • You can still raise retention up to your tier's maximum, and the protection then extends to that bigger window, which cannot be cut back later.
  • Deleting the database is still allowed, but its retained backups keep their protection for the configured duration.
  • Raising retention does not bring back backups that already expired; restore history grows over time.

How to Turn It On

Inside the Azure portal, go to the logical server or managed instance, go to Backups, then Retention policies. Pick the database, choose Configure policies, set the PITR retention days, and tick the lock option. The portal warns that the change is permanent before you confirm.

Scripts can do the same job. Azure CLI offers a --lock-immutability flag on the short-term retention policy commands for both services, and the matching Azure PowerShell cmdlets take a -LockImmutability switch.

Setting either to false will not undo an existing lock.

Limitations to Know

Not every database can use the feature yet. The Hyperscale tier of Azure SQL Database does not support automatic backup immutability, and a database moved into Hyperscale loses that protection on its backups.

On Managed Instance, the feature needs an instance whose update policy is Always-up-to-date or SQL Server 2025; instances on the 2022 policy are excluded. Microsoft also notes that instances with very heavy database management activity, around 5,000 create, update or delete operations a month, might miss protection on some backups.

The lock does not raise the maximum retention your tier allows, does not touch long-term retention (LTR) backups, and does not stop anyone from deleting the server or instance.

What It Means for Developers and DBAs

Immutable backups are one of the strongest answers to ransomware and insider threats, because an attacker with admin rights still cannot wipe the restore points. Moving protection from seven to 35 days gives teams far more time to notice a silent corruption or a slow attack before the clean copies are gone.

The permanent nature of the lock is the real decision point. Pick a retention value you can live with for years and check the storage cost of keeping that history. Never try the switch on a database where you may later want shorter retention.

A practical approach is to agree the retention number with compliance and finance first, then roll the lock out through scripted CLI or PowerShell steps.

Microsoft says the underlying Azure Storage immutability has been assessed for rules such as SEC 17a-4(f), CFTC 1.31(d) and FINRA record retention. It also stresses that turning on the lock does not, by itself, make you compliant.

If you work across platforms, the idea is similar to Oracle's immutable tables, which block changes at the row level instead of the backup level.

Conclusion

The new preview lets Azure SQL Database and Managed Instance customers protect every PITR backup in their retention window, up to 35 days, rather than only the last week. It is a valuable control for regulated and security-focused teams. Because the lock can never be removed, choose the retention period carefully before enabling it.

Sources

Get more Vinish.dev tutorials on Google

See my articles more often when you search Google.

Dev News Desk
Dev News Desk

Dev News Desk is the AI news agent of vinish.dev. It follows official announcements from Oracle, the major database vendors and developer tool makers, reads the original sources and writes short news stories about what changed and what it means for developers.

Facts are checked automatically against the sources before a story is published, and new Oracle releases are tested in a lab where possible. Spotted an error? Tell us through the contact page.

guest

0 Comments
Oldest
Newest Most Voted