Merge pull request #249902 from normesta/lifecycle-management

Adding a known issues list

Author: prmerger-automator[bot]

articles/storage/blobs/lifecycle-management-overview.md

@@ -5,7 +5,7 @@ description: Use Azure Storage lifecycle management policies to create automated
 author: normesta
 
 ms.author: normesta
-ms.date: 08/10/2023
+ms.date: 08/30/2023
 ms.service: azure-storage
 ms.subservice: storage-common-concepts
 ms.topic: conceptual
@@ -457,6 +457,20 @@ Each update to a blob's last access time is billed under the [other operations](
 
 For more information about pricing, see [Block Blob pricing](https://azure.microsoft.com/pricing/details/storage/blobs/).
 
+## Known issues and limitations
+
+- Tiering is not yet supported in a premium block blob storage account. For all other accounts, tiering is allowed only on block blobs and not for append and page blobs.
+
+- A lifecycle management policy must be read or written in full. Partial updates are not supported.
+
+- Each rule can have up to 10 case-sensitive prefixes and up to 10 blob index tag conditions.
+
+- If you enable firewall rules for your storage account, lifecycle management requests may be blocked. You can unblock these requests by providing exceptions for trusted Microsoft services. For more information, see the **Exceptions** section in [Configure firewalls and virtual networks](../common/storage-network-security.md#exceptions).
+
+- A lifecycle management policy can't change the tier of a blob that uses an encryption scope.
+
+- The delete action of a lifecycle management policy won't work with any blob in an immutable container. With an immutable policy, objects can be created and read, but not modified or deleted. For more information, see [Store business-critical blob data with immutable storage](./immutable-storage-overview.md).
+
 ## Frequently asked questions (FAQ)
 
 See [Lifecycle management FAQ](storage-blob-faq.yml#lifecycle-management-policies).

articles/storage/blobs/lifecycle-management-policy-configure.md

@@ -5,7 +5,7 @@ description: Configure a lifecycle management policy to automatically move data
 author: normesta
 
 ms.author: normesta
-ms.date: 05/02/2023
+ms.date: 08/30/2023
 ms.service: azure-storage
 ms.subservice: storage-common-concepts
 ms.topic: conceptual
@@ -216,22 +216,8 @@ To define a lifecycle management policy with an Azure Resource Manager template,
 
 ---
 
-A lifecycle management policy must be read or written in full. Partial updates are not supported.
-
-
-> [!NOTE]
-> Each rule can have up to 10 case-sensitive prefixes and up to 10 blob index tag conditions.
-
-> [!NOTE]
-> If you enable firewall rules for your storage account, lifecycle management requests may be blocked. You can unblock these requests by providing exceptions for trusted Microsoft services. For more information, see the **Exceptions** section in [Configure firewalls and virtual networks](../common/storage-network-security.md#exceptions).
-
-> [!NOTE]
-> A lifecycle management policy can't change the tier of a blob that uses an encryption scope.
-
-> [!NOTE]
-> The delete action of a lifecycle management policy won't work with any blob in an immutable container. With an immutable policy, objects can be created and read, but not modified or deleted. For more information, see [Store business-critical blob data with immutable storage](./immutable-storage-overview.md).
-
 ## See also
 
 - [Optimize costs by automatically managing the data lifecycle](lifecycle-management-overview.md)
+- [Known issues and limitations for lifecycle management policies](lifecycle-management-overview.md#known-issues-and-limitations)
 - [Access tiers for blob data](access-tiers-overview.md)