|
| 1 | +--- |
| 2 | +title: We're retiring Azure unmanaged disks by September 30, 2025 |
| 3 | +description: This article provides a high-level overview of the retirement of Azure unmanaged disks and how to migrate to Azure managed disks. |
| 4 | +author: roygara |
| 5 | +ms.service: storage |
| 6 | +ms.subservice: disks |
| 7 | +ms.workload: infrastructure-services |
| 8 | +ms.topic: conceptual |
| 9 | +ms.date: 10/03/2022 |
| 10 | +ms.author: rogarana |
| 11 | +--- |
| 12 | + |
| 13 | +# Migrate your Azure unmanaged disks by September 30, 2025 |
| 14 | + |
| 15 | +**Applies to:** :heavy_check_mark: Linux VMs :heavy_check_mark: Windows VMs |
| 16 | + |
| 17 | +In 2017, we launched [Azure managed disks](https://azure.microsoft.com/blog/announcing-general-availability-of-managed-disks-and-larger-scale-sets/). We've been enhancing capabilities ever since. Because Azure managed disks now have the full capabilities of unmanaged disks and other advancements, we'll begin deprecating unmanaged disks on September 13, 2022. This functionality will be fully retired on September 30, 2025. |
| 18 | + |
| 19 | +With managed disks, you don't have to worry about managing storage accounts for creating a disk, because Azure manages the storage accounts under the hood. The abstraction reduces maintenance overhead for you. Also, it allows managed disks to provide numerous benefits over unmanaged disks, such as better [reliability](manage-availability.md#use-managed-disks-for-vms-in-an-availability-set), [scalability](../azure-resource-manager/management/azure-subscription-service-limits.md#virtual-machine-disk-limits), large disks, [bursting](disk-bursting.md), and [shared disks](disks-shared-enable.md). If you use unmanaged disks, start planning your [Windows](windows/convert-unmanaged-to-managed-disks.md) or [Linux](linux/convert-unmanaged-to-managed-disks.md) migration now. Complete the migration by September 30, 2025, to take advantage of Azure managed disks. |
| 20 | + |
| 21 | +## How does this affect me? |
| 22 | + |
| 23 | +- As of November 18, 2022, new customer subscriptions won't be eligible to create unmanaged disks. |
| 24 | +- As of September 30, 2023, existing customers won't be able to create new unmanaged disks. |
| 25 | +- On September 30, 2025, customers will no longer be able to start IaaS VMs by using unmanaged disks. Any VMs that are still running or allocated will be stopped and deallocated. |
| 26 | + |
| 27 | +## What actions should I take? |
| 28 | + |
| 29 | +Start planning your migration to Azure managed disks today. |
| 30 | + |
| 31 | +1. Make a list of all affected VMs: |
| 32 | + |
| 33 | + - The VMs with **Uses managed disks** set to **No** on the [Azure portal's VM pane](https://ms.portal.azure.com/#blade/HubsExtension/BrowseResourceBlade/resourceType/Microsoft.ClassicCompute%2FVirtualMachines) are all the affected VMs within the subscription. |
| 34 | + - You can also query Azure Resource Graph by using the [portal](https://portal.azure.com/#blade/HubsExtension/ArgQueryBlade/query/resources%0A%7C%20where%20type%20%3D%3D%20%22microsoft.classiccompute%2Fvirtualmachines%22) or [PowerShell](https://github.com/MicrosoftDocs/azure-docs/blob/master/articles/governance/resource-graph/concepts/work-with-data.md) to view the list of all flagged VMs and related information for the selected subscriptions. |
| 35 | + - On February 28, 2020, we sent out emails to subscription owners with a list of all subscriptions that contain these VMs. Please use them to build this list. |
| 36 | + |
| 37 | +1. [Learn more](windows/migrate-to-managed-disks.md) about migrating your VMs to managed disks. For more information, see [Frequently asked questions about migrating to managed disks](faq-for-disks.yml). |
| 38 | + |
| 39 | +1. For technical questions, issues, and help with adding subscriptions to the allow list, [contact support](https://ms.portal.azure.com/#create/Microsoft.Support/Parameters/%7B%22pesId%22:%226f16735c-b0ae-b275-ad3a-03479cfa1396%22,%22supportTopicId%22:%228a82f77d-c3ab-7b08-d915-776b4ff64ff4%22%7D). |
| 40 | + |
| 41 | +1. Complete the migration as soon as possible to prevent business impact and to take advantage of the improved reliability, scalability, security, and new features of Azure managed disks. |
| 42 | + |
| 43 | +## What resources are available for this migration? |
| 44 | + |
| 45 | +- [Microsoft Q&A](https://github.com/MicrosoftDocs/azure-docs/blob/master/answers/topics/azure-virtual-machines-migration.html): Microsoft and community support for migration. |
| 46 | +- [Azure Migration Support](https://ms.portal.azure.com/#create/Microsoft.Support/Parameters/%7B%22pesId%22:%226f16735c-b0ae-b275-ad3a-03479cfa1396%22,%22supportTopicId%22:%221135e3d0-20e2-aec5-4ef0-55fd3dae2d58%22%7D): Dedicated support team for technical assistance during migration. |
| 47 | +- [Microsoft FastTrack](https://www.microsoft.com/fasttrack): FastTrack can assist eligible customers with planning and execution of this migration. [Nominate yourself](https://azure.microsoft.com/programs/azure-fasttrack/#nomination). |
| 48 | +- If your company/organization has partnered with Microsoft or works with Microsoft representatives such as cloud solution architects (CSAs) or technical account managers (TAMs), please work with them for additional resources for migration. |
0 commit comments