# Keep Azure Files share copying separate from application cutover

> DSE recommends listing the source account, share name, destination account, intended copy scope, and acceptance sample before starting.

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260917-062-keep-azure-files-share-copying-separate-from-application-cutover/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-17T16:33:58+00:00
- Modified: 2026-09-17T16:38:45+00:00
- Last reviewed by DSE: 2026-09-17
- Resource type: Guide
- DSE priority: Information
- Topics: IT
- Reading time: 1 minutes

## What you need to know

DSE recommends listing the source account, share name, destination account, intended copy scope, and acceptance sample before starting.

## Potentially affected

This guide is for an operator carrying out an approved Azure Files share copy through Storage Explorer, with source and destination accounts already chosen.

## DSE recommendation

DSE recommends listing the source account, share name, destination account, intended copy scope, and acceptance sample before starting.

## Article

## Source facts

Microsoft documents a Storage Explorer workflow that copies an Azure file share and pastes it into another storage account. The source share is selected under its account, while Paste File Share is invoked on the destination account. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/storage/storage-explorer/vs-azure-tools-storage-explorer-files)

## Applicability

This guide is for an operator carrying out an approved Azure Files share copy through Storage Explorer, with source and destination accounts already chosen.

## DSE recommendation

DSE recommends listing the source account, share name, destination account, intended copy scope, and acceptance sample before starting. Agree how changes to the source will be handled during the copy and who owns the later application decision. Preserve the source under the agreed recovery arrangements until the destination has been assessed. Treat copying the share and redirecting application access as two separately controlled steps with their own completion evidence.

## Verification

Open the destination account and confirm that the expected share and directory structure are present. Compare a representative set of files with the source, including application-relevant content and properties identified by the owner. Record incomplete or discrepant items and resolve them before a cutover decision. Retain the copy observations without claiming that application access has moved unless that separate action was performed and tested.

## Official references

- [Microsoft: Using Storage Explorer with Azure Files | Microsoft Learn](https://learn.microsoft.com/en-us/azure/storage/storage-explorer/vs-azure-tools-storage-explorer-files)

## Primary reference

- Name: Using Storage Explorer with Azure Files | Microsoft Learn
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/azure/storage/storage-explorer/vs-azure-tools-storage-explorer-files
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Keep Azure Files share copying separate from application cutover,” DSE Security, https://update.dsesecurity.com/updates/dse-20260917-062-keep-azure-files-share-copying-separate-from-application-cutover/
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.