That matters for multi-subscription Azure setups. Until now, many teams ran one vault per subscription, which meant separate policy sets and separate reporting. A Microsoft Q&A volunteer moderator described the old limit in March 2025: "Each vault can only back up resources within the same subscription. You'd need to either move VMs to the vault's subscription or use separate vaults per subscription."
What changed with general availability
Microsoft Learn's Azure Backup "What's new" page now says cross-subscription backup for Azure VMs is generally available in all Azure regions. The VM and the vault must still be in the same tenant and the same region. Microsoft says the feature lets you manage VM backups centrally across subscriptions.
The preview started in April 2026. Microsoft's China-cloud copy of the "What's new" page lists "April 2026 · Cross-subscription backup for Azure VMs (preview)". During the preview, Microsoft pitched the feature at central backup and security teams that want one vault to control VM protection across many project or team subscriptions. Microsoft's documentation repository on GitHub says the preview introduced support for protecting Azure VMs using a Recovery Services vault in a different subscription, within the same Azure AD tenant and region.
The preview was not always available in every region. A Microsoft Q&A answer from earlier this year called it "a region-dependent preview feature" and told admins to watch for regional expansion. The GA note now says the feature is available in all regions.
Summary: One vault can protect VMs across several subscriptions, with production support in every region. It still does not cross a tenant boundary or a region boundary.
Cross-subscription backup vs. cross-subscription restore
These two features have similar names and do different jobs:
| Capability | What it does | Status |
|---|---|---|
| Cross-subscription backup (CSB) | A vault in Subscription B protects a VM in Subscription A | Now GA |
| Cross Subscription Restore (CSR) | Restores recovery points to a subscription other than the source | Already GA, enabled by default on vaults |
Restore targets depend on the tier of the recovery point:
- Snapshot-tier recovery points restore only to the protected VM's subscription.
- Vault-tier recovery points can restore to the protected VM's subscription or the vault's subscription.
- To restore a vault-tier point to any other subscription, Cross Subscription Restore must be enabled on the vault.
- Original Location Restore and "Replace existing disk" work only in the protected VM's subscription.
Microsoft's restore guide says CSR is on by default. You can turn it on, turn it off, or disable it permanently under Vault > Properties > Cross Subscription Restore. A permanent disable can't be undone. A regular disable can be reversed from the same menu.
Summary: Your backup topology and your restore targets are configured separately. Test both.
Limitations to check first
Microsoft's VM backup support matrix lists one firm exclusion: "Cross-subscription backup isn't supported for Confidential VMs (CVMs), including ADE encrypted CVMs." The same entry says "Movement of backed-up data between vaults isn't supported." In other words, you can't move existing backup history into the new central vault.
The restore path has more limits than the backup path. Microsoft says Cross Subscription Restore does not work for legacy recovery points from VMs that used unmanaged disks and VMs with disks having Azure Encryptions (ADE), and the restore documentation adds VMs with customer-managed-key (CMK) encrypted disks. The Azure VM troubleshooting page also has error codes that reject CSR in these cases:
- Trusted Launch VMs
- Encrypted VMs
- Restores combined with Cross Region Restore
- Restores from snapshot-tier points
- Target subscriptions not registered to the Recovery Services resource provider
The documentation doesn't fully agree on whether CSR works alongside Cross Region Restore. The restore guide says it does, while the troubleshooting page lists an error for that combination. If you depend on Trusted Launch VMs or regional DR, test those restore paths yourself.
Moving vaults: The documentation on this has changed. Earlier guidance on GitHub said a vault that contains cross-subscription protected Azure VM backup items can't be moved across subscriptions or between resource groups. Microsoft's current vault-move guide says such vaults can now be moved, as long as the cross-subscription VMs stay in their original subscriptions. Vaults still can't move between regions.
PowerShell support
The Az.RecoveryServices module supports CSB in recent releases. According to Microsoft's Azure PowerShell release notes:
Enable-AzRecoveryServicesBackupProtectionhas an optional-ContainerSubscriptionIdparameter for a VM in a different subscription from the vault.Get-AzRecoveryServicesBackupItemandGet-AzRecoveryServicesBackupJobDetailnow return aContainerSubscriptionIdproperty, which helps when you inventory or audit backups.Restore-AzRecoveryServicesBackupItemsupports Original Location Recovery for cross-subscription items. It works out the container subscription from the recovery point, so you don't need to supply it.- The cmdlets check your input before calling the service. If the VM, resource group or subscription doesn't exist, or the VM is in a different region from the vault, you get a clear error naming the VM.
A later release fixed cross-subscription protection for VMs that use user-assigned managed identities. If you use those identities, update the module before scripting a rollout.
Why it matters, and what it doesn't do
This section is analysis based on general industry practice, not Microsoft claims.
Many organizations give each team or project its own Azure subscription for billing, isolation and RBAC. That made sense for separating workloads but scattered backup management across many vaults. With CSB, a platform team can own one hardened vault per region with immutability, soft delete and Multi-User Authorization, while application teams keep their own subscriptions.
Keeping backups in a different subscription from production may also help with security, since an attacker who compromises a workload subscription doesn't automatically control the vault. That benefit depends on your RBAC design. CSB keeps everything in one tenant, so a compromised identity with tenant-wide rights can still reach both subscriptions.
What we don't know yet: the materials reviewed don't mention pricing changes, a maximum number of subscriptions per vault, or a way to move VMs that are already protected into a central vault. Because backup data can't move between vaults, switching to a central vault probably means stopping protection in the old vault (keeping its data) and starting protection again in the new one. That's our inference, not Microsoft's guidance, so check the Microsoft documentation before you plan the migration.
Rollout checklist
- Confirm the VM and vault share a tenant and region.
- Exclude Confidential VMs.
- Check RBAC permissions in both the workload and vault subscriptions.
- Decide whether to keep CSR at its default (enabled) or disable it. Don't disable it permanently by accident.
- Update Az.RecoveryServices before you automate anything.
- Run a test restore for each recovery-point tier and target subscription, especially for Trusted Launch or encrypted VMs.
General availability makes this a supported production option. The tenant and region limits still apply, and restores have extra restrictions, so test them before you depend on them.
References
- (Launched) Generally Available: Cross-subscription backup for Azure Virtual Machines in Azure Backup Azure Updates · 2026-11-18T18:00:04Z
- azure-docs/articles/backup/backup-support-matrix.md at main · MicrosoftDocs/azure-docs · GitHub github.com
- azure-docs/articles/backup/whats-new.md at main · MicrosoftDocs/azure-docs · GitHub github.com