search

azure-deprecation / dashboard

Notices about Azure services & features being deprecated
https://azure-deprecation-notices.cloud
MIT License
134 stars 6 forks source link

Azure Storage Accounts (classic) are retiring on August 2024 #215

Open azure-deprecation-automation opened 2 years ago

azure-deprecation-automation commented 2 years ago

Azure Storage Accounts (classic) are retiring on August 2024

Deadline: Aug 31, 2024 Impacted Services:

More information:

Notice

Here's the official report from Microsoft:

In August 2021, we announced Azure Cloud Services (classic) will be retired on 31 August 2024. Because classic storage accounts are dependent on Azure Cloud Services (classic), they'll be retired on the same date. Before that date, you'll need to migrate them to Azure Resource Manager, which provides the same capabilities as well as new features, including:

  • A management layer that simplifies deployment by enabling you to create, update, and delete resources.
  • Resource grouping, which allows you to deploy, monitor, manage, and apply access control policies to resources as a group.

Beginning 1 August 2022, you'll no longer be able to create new classic storage account resources, however, resources created before that date will be supported through 31 August 2024.

Timeline

Phase Date Description
Announcement Mar 29, 2022 Deprecation was announced
Creation No Longer Allowed Aug 01, 2022 Customers will no longer be able to create new classic Azure Storage Accounts
Deprecation Aug 31, 2024 Storage account will no longer be available

Impact

Azure Storage Accounts (classic) are retiring on August 2024 and migrate to the new Azure Storage Accounts.

Required Action

A migration guide to the newer Azure Storage Accounts is available here.

Here's the official report from Microsoft:

To avoid service disruptions, review Azure Resource Manager pricing and migrate your classic storage accounts before 31 August 2024.

Contact

You can get in touch through the following options:

azure-deprecation-automation commented 2 years ago

This issue is automatically managed and suggest to use GitHub Discussions to discuss this deprecation.