Skip to content

Commit 47bb89f

Browse files
committed
add headings
1 parent 3a70b06 commit 47bb89f

File tree

1 file changed

+5
-3
lines changed

1 file changed

+5
-3
lines changed

articles/storage/blobs/storage-blob-immutability-policies-manage.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: tamram
66

77
ms.service: storage
88
ms.topic: conceptual
9-
ms.date: 11/18/2019
9+
ms.date: 11/26/2019
1010
ms.author: tamram
1111
ms.subservice: blobs
1212
---
@@ -15,9 +15,11 @@ ms.subservice: blobs
1515

1616
Immutable storage for Azure Blob storage enables users to store business-critical data objects in a WORM (Write Once, Read Many) state. This state makes the data non-erasable and non-modifiable for a user-specified interval. For the duration of the retention interval, blobs can be created and read, but cannot be modified or deleted. Immutable storage is available for general-purpose v2 and Blob storage accounts in all Azure regions.
1717

18-
This article shows how to set and manage immutability policies for Blob storage using the Azure portal, PowerShell, or Azure CLI. For more information about immutable storage, see [Store business-critical blob data with immutable storage](storage-blob-immutable-storage.md).
18+
This article shows how to set and manage immutability policies and legal holds for data in Blob storage using the Azure portal, PowerShell, or Azure CLI. For more information about immutable storage, see [Store business-critical blob data with immutable storage](storage-blob-immutable-storage.md).
1919

20-
## [Portal](#tab/azure-portal)
20+
## Set retention policies and legal holds
21+
22+
### [Portal](#tab/azure-portal)
2123

2224
1. Create a new container or select an existing container to store the blobs that need to be kept in the immutable state. The container must be in a general-purpose v2 or Blob storage account.
2325

0 commit comments

Comments
 (0)