# Track new resource identifiers during a regional-to-zonal VM move

> DSE recommends preparing a source-to-target resource map before the move window.

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260917-032-track-new-resource-identifiers-during-a-regional-to-zonal-vm-move/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-17T16:34:28+00:00
- Modified: 2026-09-17T16:35:03+00:00
- Last reviewed by DSE: 2026-09-17
- Resource type: Guide
- DSE priority: Information
- Topics: IT
- Reading time: 2 minutes

## What you need to know

DSE recommends preparing a source-to-target resource map before the move window.

## Potentially affected

This applies to the documented regional-to-zonal move of a single-instance Azure VM within one region, when the team is planning the post-move handoff.

## DSE recommendation

DSE recommends preparing a source-to-target resource map before the move window.

## Article

## Source facts

Microsoft’s same-region move workflow creates a copy of the source VM in the target zone and does not retain the source VM’s ARM identifier. It creates a new NIC and new disks for the target configuration. After the move, Microsoft directs operators to review settings such as extensions, RBAC, backup, and disaster recovery. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/virtual-machines/move-virtual-machines-regional-zonal-portal)

## Applicability

This applies to the documented regional-to-zonal move of a single-instance Azure VM within one region, when the team is planning the post-move handoff.

## DSE recommendation

DSE recommends preparing a source-to-target resource map before the move window. Give the owner of each dependent setting a place to record the target identifier and required follow-up. Include monitoring, access, backup, and recovery checks in the acceptance plan where they are relevant to the workload. Keep the source resource’s disposition as a separate explicit decision after target validation, rather than using a familiar VM name as proof of unchanged identity.

## Verification

Compare the target VM, NIC, and disk identifiers with the captured source inventory. Ask each setting owner to verify the target configuration and document unresolved differences. Confirm the workload’s acceptance criteria before closing the move, and retain the resource map so later support work identifies the correct machine.

## Official references

- [Microsoft: Move Azure single-instance virtual machines from regional to zonal availability – Azure Virtual Machines | Microsoft Learn](https://learn.microsoft.com/en-us/azure/virtual-machines/move-virtual-machines-regional-zonal-portal)

## Primary reference

- Name: Move Azure single-instance virtual machines from regional to zonal availability - Azure Virtual Machines | Microsoft Learn
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/azure/virtual-machines/move-virtual-machines-regional-zonal-portal
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Track new resource identifiers during a regional-to-zonal VM move,” DSE Security, https://update.dsesecurity.com/updates/dse-20260917-032-track-new-resource-identifiers-during-a-regional-to-zonal-vm-move/
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.