# Close Azure VM file-recovery access after copying the required files

> How should an Azure VM file-recovery session be ended without leaving recovery access open?

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260909-575-close-azure-vm-file-recovery-access-after-copying-the-required-files/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-10T00:22:21+00:00
- Modified: 2026-09-10T02:14:31+00:00
- Last reviewed by DSE: 2026-09-09
- Resource type: Guide
- DSE priority: Information
- Topics: Business Continuity, Networks & Infrastructure
- Reading time: 1 minutes

## What you need to know

How should an Azure VM file-recovery session be ended without leaving recovery access open?

## Potentially affected

This file-recovery path is for Resource Manager Azure VMs protected to a Recovery Services vault; encrypted VM backups are excluded. Check the recovery machine's documented operating-system, storage, and network compatibility before starting.

## DSE recommendation

Give each file-recovery session an owner and an explicit closeout step.

## Article

## Source facts

The Azure VM file-recovery script provides read-only recovery-point access and is valid for 12 hours. Unmounting that recovery point invalidates the script immediately, rather than waiting for its validity period to end. Microsoft warns that leaving the connection open can disrupt a subsequent backup of the recovery machine. On Linux, disconnected mount paths can remain visible as orphan volumes until explicitly cleaned. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/backup/backup-azure-restore-files-from-vm).

## Applicability

This file-recovery path is for Resource Manager Azure VMs protected to a Recovery Services vault; encrypted VM backups are excluded. Check the recovery machine’s documented operating-system, storage, and network compatibility before starting.

## DSE recommendation

Give each file-recovery session an owner and an explicit closeout step. Track the chosen recovery point, approved destination, and files to recover without distributing the access script or password broadly. After the copy is accepted, close the connection through the documented unmount action. Keep Linux mount cleanup distinct from revoking access; use the documented cleanup procedure only for the recovery session’s mounts.

## Verification

Confirm the requested files are readable at the approved destination, then verify unmount completion and any required local cleanup. If the recovery machine is itself backed up, check its next backup result. Preserve evidence of completion without retaining recovery credentials in the general ticket.

## Official references

[Microsoft Learn: Recover files and folders from Azure VM backup](https://learn.microsoft.com/en-us/azure/backup/backup-azure-restore-files-from-vm).

## Primary reference

- Name: Recover files and folders from Azure VM backup - Azure Backup | Microsoft Learn
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/azure/backup/backup-azure-restore-files-from-vm
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Close Azure VM file-recovery access after copying the required files,” DSE Security, https://update.dsesecurity.com/updates/dse-20260909-575-close-azure-vm-file-recovery-access-after-copying-the-required-files/
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.