# Define the completion and return path before converting a disk to Premium SSD v2

> What should a conversion plan establish before changing an existing Azure data disk to Premium SSD v2?

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260909-048-define-the-completion-and-return-path-before-converting-a-disk-to-premium-ssd-v2/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-10T00:31:08+00:00
- Modified: 2026-09-10T00:32:01+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 should a conversion plan establish before changing an existing Azure data disk to Premium SSD v2?

## Potentially affected

Teams evaluating conversion of eligible existing Azure managed data disks to Premium SSD v2.

## DSE recommendation

Approve the conversion prerequisites and a snapshot-based return plan before scheduling the change.

## Article

## Source facts

Microsoft excludes OS disks from conversion to Premium SSD v2. Direct conversion targets 512-byte-sector Premium SSD v2 disks and has additional caching, bursting, encryption, and protection prerequisites. The documented conversion requires a VM restart. During conversion, disk performance is reduced and customer-managed keys cannot be changed or rotated. Completion can be inspected through completionPercent. Returning from Premium SSD v2 to another disk type requires snapshot-based migration rather than a direct switch. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/virtual-machines/disks-convert-types).

## Applicability

Evaluate one identified managed data disk against every current conversion restriction, including its origin and attached services. Record the source type, sector size, encryption arrangement, backup configuration, and application owner. Do not interpret this article as approval to disable an existing protection control.

## DSE recommendation

Approve the conversion prerequisites and a snapshot-based return plan before scheduling the change. Ask the data owner to review recovery evidence and the security owner to assess any prerequisite that changes protection. Schedule the restart within an approved maintenance window and plan around the documented conversion period rather than declaring success immediately after the type-setting request. Give the operator an explicit stop condition for an unmet prerequisite or unexpected progress result.

## Verification

Observe conversion progress through the documented completion field and retain its final value. Once conversion finishes, compare disk settings and application behavior with the approved design. Reconcile the protection controls that were part of the change plan. Keep the original recovery material until the owner accepts the result, and document the tested return procedure instead of promising a simple reverse type change.

## Official references

[Microsoft Learn: Convert managed disks storage between different disk types](https://learn.microsoft.com/en-us/azure/virtual-machines/disks-convert-types). Source reviewed September 9, 2026.

## Primary reference

- Name: Convert managed disks storage between different disk types - Azure Virtual Machines | Microsoft Learn
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/azure/virtual-machines/disks-convert-types
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Define the completion and return path before converting a disk to Premium SSD v2,” DSE Security, https://update.dsesecurity.com/updates/dse-20260909-048-define-the-completion-and-return-path-before-converting-a-disk-to-premium-ssd-v2/
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.