Merge pull request #93096 from xyh1/patch-75

Update storage-lifecycle-management-concepts.md

Author: PRMerger10

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

@@ -52,7 +52,7 @@ This article shows how to manage policy by using the portal and PowerShell metho
 > [!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](https://docs.microsoft.com/azure/storage/common/storage-network-security#exceptions).
 
-### Azure portal
+# [Portal](#tab/azure-portal)
 
 There are two ways to add a policy through the Azure portal. 
 
@@ -122,7 +122,7 @@ There are two ways to add a policy through the Azure portal.
 
 6. For more information about this JSON example, see the [Policy](#policy) and [Rules](#rules) sections.
 
-### PowerShell
+# [Powershell](#tab/azure-powershell)
 
 The following PowerShell script can be used to add a policy to your storage account. The `$rgname` variable must be initialized with your resource group name. The `$accountName` variable must be initialized with your storage account name.
 
@@ -152,7 +152,7 @@ $rule1 = New-AzStorageAccountManagementPolicyRule -Name Test -Action $action -Fi
 $policy = Set-AzStorageAccountManagementPolicy -ResourceGroupName $rgname -StorageAccountName $accountName -Rule $rule1
 ```
 
-## Azure Resource Manager template with lifecycle management policy
+# [Template](#tab/template)
 
 You can define lifecycle management by using Azure Resource Manager templates. Here is a sample template to deploy a RA-GRS GPv2 storage account with a lifecycle management policy.
 
@@ -194,6 +194,8 @@ You can define lifecycle management by using Azure Resource Manager templates. H
 }
 ```
 
+---
+
 ## Policy
 
 A lifecycle management policy is a collection of rules in a JSON document:
@@ -341,6 +343,9 @@ This example shows how to transition block blobs prefixed with `container1/foo`
 
 Some data stays idle in the cloud and is rarely, if ever, accessed once stored. The following lifecycle policy is configured to archive data once it's ingested. This example transitions block blobs in the storage account within container `archivecontainer` into an archive tier. The transition is accomplished by acting on blobs 0 days after last modified time:
 
+> [!NOTE] 
+> It is recommended to upload your blobs directly the archive tier to be more efficient. You can use the x-ms-acess-tier header for [PutBlob](https://docs.microsoft.com/rest/api/storageservices/put-blob) or [PutBlockList](https://docs.microsoft.com/rest/api/storageservices/put-block-list) with REST version 2018-11-09 and newer or our latest blob storage client libraries. 
+
 ```json
 {
   "rules": [
@@ -423,9 +428,8 @@ For data that is modified and accessed regularly throughout its lifetime, snapsh
 **I created a new policy, why do the actions not run immediately?**  
 The platform runs the lifecycle policy once a day. Once you configure a policy, it can take up to 24 hours for some actions to run for the first time.  
 
-**I manually rehydrate an archived blob, how do I prevent it from being moved back to the Archive tier temporarily?**  
-When a blob is moved from one access tier to another, its last modification time doesn't change. If you manually rehydrate an archived blob to hot tier, it would be moved back to archive tier by the lifecycle management engine. Disable the rule that affects this blob temporarily to prevent it from being archived again. Copy the blob to another location if it needs to stay in hot tier permanently. Re-enable the rule when the blob can be safely moved back to archive tier. 
-
+**I manually rehydrated an archived blob, how do I prevent it from being moved back to the Archive tier temporarily?**  
+When a blob is moved from one access tier to another, its last modification time doesn't change. If you manually rehydrate an archived blob to hot tier, it would be moved back to archive tier by the lifecycle management engine. Disable the rule that affects this blob temporarily to prevent it from being archived again. Re-enable the rule when the blob can be safely moved back to archive tier. You may also copy the blob to another location if it needs to stay in hot or cool tier permanently.
 
 ## Next steps