# Keep regional backup history separate from a moved Azure workload

> Does moving an Azure VM to another region carry its existing backup history to a new vault?

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260909-502-keep-regional-backup-history-separate-from-a-moved-azure-workload/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-10T00:23:34+00:00
- Modified: 2026-09-10T02:11:17+00:00
- Last reviewed by DSE: 2026-09-09
- Resource type: Guide
- DSE priority: Information
- Topics: Business Continuity, Networks & Infrastructure
- Reading time: 2 minutes

## What you need to know

Does moving an Azure VM to another region carry its existing backup history to a new vault?

## Potentially affected

Apply this planning distinction to an Azure VM regional move. A resource-group or subscription move is a different operation; review the exact workload's migration and protection requirements rather than treating all moves alike.

## DSE recommendation

Maintain two explicit recovery records: historical points in the source region and new protection in the destination.

## Article

## Source facts

Azure Backup does not support moving a Recovery Services vault between regions or transferring backup data from one Recovery Services vault to another. A resource moved to a new region needs protection in a vault there. After an Azure VM changes region, its earlier vault cannot continue backing it up. If the old backup data was retained, it remains available for recovery through the old vault. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/backup/backup-azure-move-recovery-services-vault).

## Applicability

Apply this planning distinction to an Azure VM regional move. A resource-group or subscription move is a different operation; review the exact workload’s migration and protection requirements rather than treating all moves alike.

## DSE recommendation

Maintain two explicit recovery records: historical points in the source region and new protection in the destination. Before moving the workload, have its owner approve retention of the old history and assign responsibility for both vaults. Schedule destination protection and verify its dependencies as part of the move plan. Do not delete source history merely to make the post-move inventory look tidy, and do not treat a running destination VM as proof of new backup coverage.

## Verification

After an approved move, confirm new-region backup jobs and recovery points. Independently exercise an authorized restore from retained source history in a safe destination. Record which vault provides each recovery period and how responders find it. Escalate any gap between the last accepted source backup and the first accepted destination backup.

## Official references

[Microsoft Learn: How to move Azure Backup Recovery Services vaults](https://learn.microsoft.com/en-us/azure/backup/backup-azure-move-recovery-services-vault).

## Primary reference

- Name: How to move Azure Backup Recovery Services vaults - Azure Backup | Microsoft Learn
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/azure/backup/backup-azure-move-recovery-services-vault
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Keep regional backup history separate from a moved Azure workload,” DSE Security, https://update.dsesecurity.com/updates/dse-20260909-502-keep-regional-backup-history-separate-from-a-moved-azure-workload/
Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/
Usage and citation policy: https://update.dsesecurity.com/usage/
Copyright © 2026 Detection Systems & Engineering. All rights reserved.