# Plan a new account when moving standard block blobs to premium

> Can an existing standard general-purpose v2 storage account be converted directly into premium block blob storage?

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260909-555-plan-a-new-account-when-moving-standard-block-blobs-to-premium/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-10T00:22:41+00:00
- Modified: 2026-09-10T02:14:30+00:00
- Last reviewed by DSE: 2026-09-09
- Resource type: Guide
- DSE priority: Information
- Topics: Cybersecurity, Networks & Infrastructure
- Reading time: 2 minutes

## What you need to know

Can an existing standard general-purpose v2 storage account be converted directly into premium block blob storage?

## Potentially affected

Use this decision for a proposed move from a standard general-purpose v2 account to premium block blob storage. Review the current feature-support matrix for the actual workload; this article does not reproduce the source's historical pricing or performance examples.

## DSE recommendation

Treat the proposal as a data migration, not an account-setting change.

## Article

## Source facts

Microsoft says an existing standard general-purpose v2 account cannot be converted into a premium block blob account. The documented route is to create a premium block blob account and migrate the data. Microsoft also requires checking feature compatibility before choosing premium because some Blob Storage features have absent or partial support in that account type. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/storage/blobs/storage-blob-block-blob-premium).

## Applicability

Use this decision for a proposed move from a standard general-purpose v2 account to premium block blob storage. Review the current feature-support matrix for the actual workload; this article does not reproduce the source’s historical pricing or performance examples.

## DSE recommendation

Treat the proposal as a data migration, not an account-setting change. Identify the destination account, required storage features and every caller that must use the new location. Have the data owner approve the copy, cutover and verification plan before creating a production dependency on premium. Preserve the existing authoritative data and access arrangement until the destination has been accepted. Keep performance expectations separate from the supported migration route and measure them with the real workload.

## Verification

In an approved pilot, verify the destination account type and each required feature against current documentation. Reconcile copied content and the intended application access at the new location. Test the agreed cutover and recovery decision without deleting the source as part of the initial check. A successful account creation should not be recorded as proof that the data and its consumers have migrated.

## Official references

[Microsoft Learn: Premium block blob storage accounts](https://learn.microsoft.com/en-us/azure/storage/blobs/storage-blob-block-blob-premium).

## Primary reference

- Name: Premium block blob storage accounts - Azure Storage | Microsoft Learn
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/azure/storage/blobs/storage-blob-block-blob-premium
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Plan a new account when moving standard block blobs to premium,” DSE Security, https://update.dsesecurity.com/updates/dse-20260909-555-plan-a-new-account-when-moving-standard-block-blobs-to-premium/
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.