# Map every restored disk before rebuilding a VM from its restore point

> What must be reconstructed after selecting an Azure VM restore point?

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260909-072-map-every-restored-disk-before-rebuilding-a-vm-from-its-restore-point/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-10T00:30:44+00:00
- Modified: 2026-09-10T00:35:07+00:00
- Last reviewed by DSE: 2026-09-09
- Resource type: Guide
- DSE priority: Information
- Topics: Business Continuity, IT
- Reading time: 2 minutes

## What you need to know

What must be reconstructed after selecting an Azure VM restore point?

## Potentially affected

Recovery operators rebuilding an Azure VM from an existing VM restore point.

## DSE recommendation

Prepare a disk-restore-point-to-target-disk map before creating the replacement VM.

## Article

## Source facts

An Azure VM restore point contains individual disk restore-point identifiers. Microsoft’s recovery procedure creates disks from those identifiers, then creates a new VM and attaches the restored disks. A target disk can be created in a different zone from its disk restore point. When the VM restore point was copied between regions, every constituent disk copy must finish before the VM can be restored. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/virtual-machines/manage-restore-points).

## Applicability

Start with a selected restore point and an approved replacement-VM recovery plan. Identify the intended recovery time, every required disk, and the target region and zone. Review the source restore point’s coverage and consistency separately; reconstruction does not resolve data that was excluded from capture.

## DSE recommendation

Prepare a disk-restore-point-to-target-disk map before creating the replacement VM. Have the application owner confirm the OS and data-disk roles and the intended attachment arrangement. For a cross-region recovery, require completion evidence for the entire disk set before beginning reconstruction. Keep the original VM and recovery artifacts outside any cleanup operation until the replacement is accepted.

## Verification

Inspect the new disks and VM attachments against the approved map. Boot the replacement in the authorized recovery environment and test the application’s expected data and service behavior. Record the restore point, constituent disk identifiers, target resources, and result together. Investigate an omitted or incorrectly attached disk explicitly instead of accepting a successful VM creation response as proof that the complete workload was restored.

## Official references

[Microsoft Learn: Manage VM restore points](https://learn.microsoft.com/en-us/azure/virtual-machines/manage-restore-points). Source reviewed September 9, 2026.

## Primary reference

- Name: Manage Virtual Machine restore points - Azure Virtual Machines | Microsoft Learn
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/azure/virtual-machines/manage-restore-points
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Map every restored disk before rebuilding a VM from its restore point,” DSE Security, https://update.dsesecurity.com/updates/dse-20260909-072-map-every-restored-disk-before-rebuilding-a-vm-from-its-restore-point/
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.