# Include downgrade timing and tooling in a Premium SSD tier-change plan

> Which restrictions matter when temporarily raising an Azure Premium SSD's performance tier?

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260909-047-include-downgrade-timing-and-tooling-in-a-premium-ssd-tier-change-plan/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-10T00:31:09+00:00
- Modified: 2026-09-10T00:32:01+00:00
- Last reviewed by DSE: 2026-09-09
- Resource type: Guide
- DSE priority: Information
- Topics: IT, Networks & Infrastructure
- Reading time: 2 minutes

## What you need to know

Which restrictions matter when temporarily raising an Azure Premium SSD's performance tier?

## Potentially affected

Operators changing performance tiers on Azure Premium SSD managed disks.

## DSE recommendation

Record the baseline tier, permitted return time, attachment scope, and execution tool before approving a temporary tier increase.

## Article

## Source facts

Azure Premium SSD managed disks can change performance tier without resizing the disk. A tier cannot fall below the disk’s baseline, and downgrades are limited to once per twelve hours. Shared-disk changes require stopping all attached VMs. Microsoft additionally warns that Terraform shuts down a running VM when used for this change, unlike the other documented methods. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/virtual-machines/disks-change-performance).

## Applicability

Review a Premium SSD managed disk, not Ultra Disk or Premium SSD v2 performance settings. Identify its baseline and current tier, the supported target, and every attached VM. Ask the workload owner to state how long the higher performance is required before deciding when to return.

## DSE recommendation

Record the baseline tier, permitted return time, attachment scope, and execution tool before approving a temporary tier increase. Make the change plan explicit about any required shutdown rather than treating the feature’s general online capability as a property of every tool or attachment arrangement. Assign an owner to revisit the temporary increase after the workload event ends.

## Verification

Inspect the resulting tier and unchanged capacity after the approved operation. Run the agreed workload measurement and compare it with the purpose of the increase. Before returning to baseline, check the downgrade interval and the same attachment/tooling conditions again. Preserve the original tier, actual change times, and final result so a failed or delayed return is visible instead of becoming an undocumented permanent setting.

## Official references

[Microsoft Learn: Performance tiers for Azure managed disks](https://learn.microsoft.com/en-us/azure/virtual-machines/disks-change-performance). Source reviewed September 9, 2026.

## Primary reference

- Name: Performance tiers for Azure managed disks - Azure Virtual Machines | Microsoft Learn
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/azure/virtual-machines/disks-change-performance
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Include downgrade timing and tooling in a Premium SSD tier-change plan,” DSE Security, https://update.dsesecurity.com/updates/dse-20260909-047-include-downgrade-timing-and-tooling-in-a-premium-ssd-tier-change-plan/
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.