Documentation Index

Fetch the complete documentation index at: https://docs.workspot.com/llms.txt

Use this file to discover all available pages before exploring further.

Data Loss on Azure Temporary Drive

  • Published on Jul 15, 2026
  • 2 minute(s) read
  • AA
 Prev Next

Overview

In Azure-based Cloud Desktops, the D: drive may be configured as Azure temporary storage. This disk is non-persistent and is intended only for temporary files, cache, or pagefile usage. Data saved only on this drive can be permanently lost if the VM is stopped, deallocated, resized, moved to another host, or affected by Azure platform maintenance.

This KB explains why D: drive data may disappear, what can be recovered, and how to prevent future data loss.

Symptoms

  • Files previously saved on the D: drive is missing.

  • The D: drive shows a temporary storage warning.

  • The drive appears empty or recreated after user login.

  • No previous files are visible or accessible from the D: drive.

Applies To

  • Workspot Cloud Desktops hosted on Microsoft Azure

  • Azure Windows VMs where the D: drive is Azure temporary storage

  • User reports involving missing files from the D: drive

Issue

A user may save files to the D: drive assuming it is persistent storage. If that drive is Azure temporary storage, the data is not backed by Azure managed disk storage and may be removed when the VM undergoes certain lifecycle or platform events.

Cause

The Azure temporary D: drive is local, non-persistent storage. Microsoft guidance states that it should not be used for data that must be retained, because data loss can occur when a VM is moved to a different host, resized, stopped/deallocated, or impacted by host maintenance or hardware events.

When the temporary disk is recreated or reassigned, files stored only on that disk are permanently lost. Azure does not provide a recovery mechanism for data stored only on temporary storage.

Resolution

  1. Confirm whether the affected D: drive is Azure temporary storage or a managed data disk.

  2. If it is temporary storage, files stored only on this drive cannot be recovered.

  3. If the missing data may have existed on a managed disk, backup, OneDrive, profile container, or network share, validate those locations separately.

  4. Guide the customer to use persistent storage for all business-critical files going forward.

Recommended Persistent Storage Locations

  • User profile storage or profile container

  • OneDrive or approved cloud file storage

  • Corporate network shares

  • Attached Azure managed data disks

Azure VM SKUs with Temporary Drives

Azure VM temporary storage availability depends on the selected VM family, generation, and exact SKU name. In Windows VMs, temporary storage commonly appears as the D: drive. For D, F, and NV series VMs, v3, v4, and v5 generations can differ significantly: some older generations include local temporary storage by default, while newer generations may require a specific local-disk SKU variant such as a “d” series. Always validate the exact SKU before confirming whether the D: drive is temporary storage.

Prevention

  • Do not store user or business-critical data on the Azure temporary D: drive.

  • Educate users that the D: drive may be temporary and is not a safe location for permanent files.

  • Use OneDrive, profile storage, network shares, or managed disks for persistent data.

  • Validate backup, file redirection, and sync policies for customer environments that require data protection.