{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260917-022-treat-azure-disk-performance-plus-as-a-creation-time-choice/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260917-022-treat-azure-disk-performance-plus-as-a-creation-time-choice/", "slug": "dse-20260917-022-treat-azure-disk-performance-plus-as-a-creation-time-choice", "url": "https://update.dsesecurity.com/updates/dse-20260917-022-treat-azure-disk-performance-plus-as-a-creation-time-choice/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260917-022-treat-azure-disk-performance-plus-as-a-creation-time-choice.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260917-022-treat-azure-disk-performance-plus-as-a-creation-time-choice/" }, "title": "Treat Azure disk performance plus as a creation-time choice", "summary": "DSE recommends recording performance plus in the new-disk specification before deployment.", "format": { "slug": "guide", "name": "Guide" }, "priority": { "slug": "info", "name": "Information" }, "featured": false, "image": { "theme": "managed-it", "label": "Managed IT operations", "alt": "A controlled technology lifecycle progressing from assessment to approved production.", "card_url": "https://update.dsesecurity.com/assets/editorial/managed-it-card.webp?v=1.8.20", "hero_url": "https://update.dsesecurity.com/assets/editorial/managed-it-hero.webp?v=1.8.20", "social_url": "https://update.dsesecurity.com/assets/editorial/managed-it-social-v2.jpg?v=1.8.20", "width": 2400, "height": 1350 }, "topics": [ { "slug": "it", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" } ], "author": { "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team", "type": "Organization" }, "publisher": { "name": "Detection Systems & Engineering", "url": "https://dsesecurity.com/" }, "published_at": "2026-09-17T16:34:38+00:00", "modified_at": "2026-09-17T16:35:03+00:00", "reviewed_on": "2026-09-17", "reading_minutes": 2, "word_count": 238, "potentially_affected": "Use this decision when evaluating performance plus for an existing managed disk or specifying a new eligible disk, after identifying the disk type and recovery history.", "dse_recommendation": "DSE recommends recording performance plus in the new-disk specification before deployment.", "primary_source": { "name": "Increase performance of Premium SSD, Standard SSD, and Standard HDD - Azure Virtual Machines | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/azure/virtual-machines/disks-enable-performance", "published_on": null, "authority": "Microsoft Learn" }, "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usage_info": "https://update.dsesecurity.com/usage/", "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "content_html": "

Source facts

\n

Microsoft limits performance plus to Premium SSD, Standard SSD, and Standard HDD managed disks with capacity of at least 513 GiB. It can be enabled only when the disk is created; the documented workaround for an existing disk creates a snapshot and then a new disk. Disks created as part of virtual-machine creation are excluded; the disk must be created separately. The feature is not supported for disks recovered using Azure Site Recovery. Microsoft Learn

\n

Applicability

\n

Use this decision when evaluating performance plus for an existing managed disk or specifying a new eligible disk, after identifying the disk type and recovery history.

\n

DSE recommendation

\n

DSE recommends recording performance plus in the new-disk specification before deployment. For an existing workload, write a replacement-disk plan that identifies the source disk, snapshot, target disk, attachment steps, and acceptance criteria. Check the documented eligibility conditions before scheduling work. Keep the original disk available under an agreed recovery plan while the replacement is assessed, rather than treating this as an ordinary setting change.

\n

Verification

\n

Inspect the new disk properties for the requested feature and compare its resource identifier with the planned target. Confirm the workload uses that disk before collecting performance observations. Evaluate those observations against the agreed workload criteria, and record any unresolved attachment, recovery, or performance issue before completing the change.

\n

Official references

\n", "content_text": "Source facts\nMicrosoft limits performance plus to Premium SSD, Standard SSD, and Standard HDD managed disks with capacity of at least 513 GiB. It can be enabled only when the disk is created; the documented workaround for an existing disk creates a snapshot and then a new disk. Disks created as part of virtual-machine creation are excluded; the disk must be created separately. The feature is not supported for disks recovered using Azure Site Recovery. Microsoft Learn\nApplicability\nUse this decision when evaluating performance plus for an existing managed disk or specifying a new eligible disk, after identifying the disk type and recovery history.\nDSE recommendation\nDSE recommends recording performance plus in the new-disk specification before deployment. For an existing workload, write a replacement-disk plan that identifies the source disk, snapshot, target disk, attachment steps, and acceptance criteria. Check the documented eligibility conditions before scheduling work. Keep the original disk available under an agreed recovery plan while the replacement is assessed, rather than treating this as an ordinary setting change.\nVerification\nInspect the new disk properties for the requested feature and compare its resource identifier with the planned target. Confirm the workload uses that disk before collecting performance observations. Evaluate those observations against the agreed workload criteria, and record any unresolved attachment, recovery, or performance issue before completing the change.\nOfficial references\n\nMicrosoft: Increase performance of Premium SSD, Standard SSD, and Standard HDD – Azure Virtual Machines | Microsoft Learn", "content_markdown": "## Source facts\n\nMicrosoft limits performance plus to Premium SSD, Standard SSD, and Standard HDD managed disks with capacity of at least 513 GiB. It can be enabled only when the disk is created; the documented workaround for an existing disk creates a snapshot and then a new disk. Disks created as part of virtual-machine creation are excluded; the disk must be created separately. The feature is not supported for disks recovered using Azure Site Recovery. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/virtual-machines/disks-enable-performance)\n\n## Applicability\n\nUse this decision when evaluating performance plus for an existing managed disk or specifying a new eligible disk, after identifying the disk type and recovery history.\n\n## DSE recommendation\n\nDSE recommends recording performance plus in the new-disk specification before deployment. For an existing workload, write a replacement-disk plan that identifies the source disk, snapshot, target disk, attachment steps, and acceptance criteria. Check the documented eligibility conditions before scheduling work. Keep the original disk available under an agreed recovery plan while the replacement is assessed, rather than treating this as an ordinary setting change.\n\n## Verification\n\nInspect the new disk properties for the requested feature and compare its resource identifier with the planned target. Confirm the workload uses that disk before collecting performance observations. Evaluate those observations against the agreed workload criteria, and record any unresolved attachment, recovery, or performance issue before completing the change.\n\n## Official references\n\n- [Microsoft: Increase performance of Premium SSD, Standard SSD, and Standard HDD – Azure Virtual Machines | Microsoft Learn](https://learn.microsoft.com/en-us/azure/virtual-machines/disks-enable-performance)" }, "json_ld": { "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://dsesecurity.com/#organization", "name": "Detection Systems & Engineering", "alternateName": "DSE Security", "url": "https://dsesecurity.com/", "logo": { "@type": "ImageObject", "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20" } }, { "@type": "Organization", "@id": "https://update.dsesecurity.com/#editorial-team", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/", "parentOrganization": { "@id": "https://dsesecurity.com/#organization" } }, { "@type": "WebSite", "@id": "https://update.dsesecurity.com/#website", "name": "DSE Updates", "alternateName": "DSE Security Knowledge Hub", "url": "https://update.dsesecurity.com/", "inLanguage": "en-US", "publisher": { "@id": "https://dsesecurity.com/#organization" }, "potentialAction": { "@type": "SearchAction", "target": { "@type": "EntryPoint", "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}" }, "query-input": "required name=search_term_string" } }, { "@type": "WebPage", "@id": "https://update.dsesecurity.com/updates/dse-20260917-022-treat-azure-disk-performance-plus-as-a-creation-time-choice/", "url": "https://update.dsesecurity.com/updates/dse-20260917-022-treat-azure-disk-performance-plus-as-a-creation-time-choice/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-17" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260917-022-treat-azure-disk-performance-plus-as-a-creation-time-choice/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Treat Azure disk performance plus as a creation-time choice", "item": "https://update.dsesecurity.com/updates/dse-20260917-022-treat-azure-disk-performance-plus-as-a-creation-time-choice/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260917-022-treat-azure-disk-performance-plus-as-a-creation-time-choice/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260917-022-treat-azure-disk-performance-plus-as-a-creation-time-choice/", "url": "https://update.dsesecurity.com/updates/dse-20260917-022-treat-azure-disk-performance-plus-as-a-creation-time-choice/", "headline": "Treat Azure disk performance plus as a creation-time choice", "description": "DSE recommends recording performance plus in the new-disk specification before deployment.", "abstract": "DSE recommends recording performance plus in the new-disk specification before deployment.", "articleBody": "Source facts\nMicrosoft limits performance plus to Premium SSD, Standard SSD, and Standard HDD managed disks with capacity of at least 513 GiB. It can be enabled only when the disk is created; the documented workaround for an existing disk creates a snapshot and then a new disk. Disks created as part of virtual-machine creation are excluded; the disk must be created separately. The feature is not supported for disks recovered using Azure Site Recovery. Microsoft Learn\nApplicability\nUse this decision when evaluating performance plus for an existing managed disk or specifying a new eligible disk, after identifying the disk type and recovery history.\nDSE recommendation\nDSE recommends recording performance plus in the new-disk specification before deployment. For an existing workload, write a replacement-disk plan that identifies the source disk, snapshot, target disk, attachment steps, and acceptance criteria. Check the documented eligibility conditions before scheduling work. Keep the original disk available under an agreed recovery plan while the replacement is assessed, rather than treating this as an ordinary setting change.\nVerification\nInspect the new disk properties for the requested feature and compare its resource identifier with the planned target. Confirm the workload uses that disk before collecting performance observations. Evaluate those observations against the agreed workload criteria, and record any unresolved attachment, recovery, or performance issue before completing the change.\nOfficial references\n\nMicrosoft: Increase performance of Premium SSD, Standard SSD, and Standard HDD – Azure Virtual Machines | Microsoft Learn", "datePublished": "2026-09-17T16:34:38+00:00", "dateModified": "2026-09-17T16:35:03+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260917-022-treat-azure-disk-performance-plus-as-a-creation-time-choice/" }, "inLanguage": "en-US", "isAccessibleForFree": true, "author": { "@type": "Organization", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team" }, "publisher": { "@id": "https://dsesecurity.com/#organization" }, "image": { "@type": "ImageObject", "@id": "https://update.dsesecurity.com/updates/dse-20260917-022-treat-azure-disk-performance-plus-as-a-creation-time-choice/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/managed-it-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/managed-it-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Treat Azure disk performance plus as a creation-time choice" }, "articleSection": [ "IT" ], "keywords": [ "IT", "Guide", "Information priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" } ], "wordCount": 238, "timeRequired": "PT2M", "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usageInfo": "https://update.dsesecurity.com/usage/", "copyrightHolder": { "@id": "https://dsesecurity.com/#organization" }, "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "citation": { "@type": "CreativeWork", "name": "Increase performance of Premium SSD, Standard SSD, and Standard HDD - Azure Virtual Machines | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/azure/virtual-machines/disks-enable-performance" } } ] } }