Merge pull request #312862 from vgs-msft/docs-editor/lifecycle-management-overview-1773092562

Update lifecycle-management-overview.md

Author: prmerger-automator[bot]

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

@@ -85,6 +85,8 @@ For more information about pricing, see [Block Blob pricing](https://azure.micro
 
 - 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).
 
+- The delete action of a lifecycle management policy won't work with any blob that is in a soft-deleted state. Lifecycle management policies that delete objects in a storage account with soft-delete enabled will put the object in a soft-deleted state that is retained for the duration of the soft-delete. See [Soft delete for blobs](./soft-delete-blob-overview.md). 
+
 - A delete action might fail if an Azure Storage Action attempts to delete the same blob. 
 
 - Lifecycle management doesn't affect system containers such as the `$logs` or `$web containers`.

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

@@ -18,6 +18,12 @@ You can use lifecycle management policies to transition blobs to delete blob at
 
 For general information about Azure Storage lifecycle management policies, see [Azure Blob Storage lifecycle management overview](lifecycle-management-overview.md).
 
+> [!IMPORTANT]
+>  Lifecycle management policies that delete blobs in a storage account with soft-delete enabled will put the blob in a soft-deleted state. Such blobs are retained for the duration of the soft-delete retention period. See [Soft delete for blobs](./soft-delete-blob-overview.md). Lifecycle management policies do not impact blobs that are already in a soft-deleted state.
+
+> [!TIP]
+> Use [Azure Storage Actions](../../storage-actions/overview.md) to restore/undelete blobs from a soft-deleted state.
+
 ## Expire data based on age
 
 Some data is expected to expire days or months after creation. You can configure a lifecycle management policy to expire data by deletion based on data age. The following example shows a policy that deletes all block blobs that haven't been modified in the last 365 days.