Skip to content

Commit 1ffc332

Browse files
committed
Updating based on expirements
1 parent ed8ac68 commit 1ffc332

File tree

1 file changed

+1
-6
lines changed

1 file changed

+1
-6
lines changed

articles/storage/blobs/upgrade-to-data-lake-storage-gen2-how-to.md

Lines changed: 1 addition & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: normesta
55
ms.service: azure-blob-storage
66
ms.custom: devx-track-azurepowershell
77
ms.topic: conceptual
8-
ms.date: 01/18/2024
8+
ms.date: 11/15/2024
99
ms.author: normesta
1010
---
1111

@@ -36,18 +36,13 @@ The following features are supported for Data Lake Storage accounts, but are not
3636
- Blob snapshots
3737
- Encryption scopes
3838
- Immutable storage
39-
- Last access time tracking for lifecycle management
4039
- Soft delete for blobs
4140
- Soft delete for containers
4241

4342
If your storage account has such features enabled, you must disable them before performing the upgrade. If you want to resume using the features after the upgrade is complete, re-enable them.
4443

4544
In some cases, you will have to allow time for clean-up operations after a feature is disabled before upgrading. One example is the [blob soft delete](soft-delete-blob-overview.md) feature. You must disable blob soft delete and then allow all soft-delete blobs to expire before you can upgrade the account.
4645

47-
> [!IMPORTANT]
48-
> You cannot upgrade a storage account to Data Lake Storage that has **ever** had the change feed feature enabled.
49-
> Simply disabling change feed will not allow you to perform an upgrade. Instead, you must create an account with the hierarchical namespace feature enabled on it, and move then transfer your data into that account.
50-
5146
### Remove page blobs from the storage account
5247

5348
You cannot upgrade a storage account that contains page blobs. Make sure to remove page blobs from the storage account before you perform the upgrade.

0 commit comments

Comments
 (0)