Merge pull request #225674 from normesta/normesta-reg-updates-11

Addressing a github issue

Author: prmerger-automator[bot]

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

@@ -444,6 +444,10 @@ The platform runs the lifecycle policy once a day. Once you configure a policy,
 
 The updated policy takes up to 24 hours to go into effect. Once the policy is in effect, it could take up to 24 hours for the actions to run. Therefore, the policy actions may take up to 48 hours to complete. If the update is to disable or delete a rule, and enableAutoTierToHotFromCool was used, auto-tiering to Hot tier will still happen. For example, set a rule including enableAutoTierToHotFromCool based on last access. If the rule is disabled/deleted, and a blob is currently in cool and then accessed, it will move back to Hot as that is applied on access outside of lifecycle management. The blob won't then move from Hot to Cool given the lifecycle management rule is disabled/deleted. The only way to prevent autoTierToHotFromCool is to turn off last access time tracking.
 
+### The run completes but doesn't move or delete some blobs
+
+Depending on the size and number of objects in a storage account, more than one run might be required to process all of the objects. 
+
 ### I rehydrated an archived blob. How do I prevent it from being moved back to the Archive tier temporarily?
 
 If there's a lifecycle management policy in effect for the storage account, then rehydrating a blob by changing its tier can result in a scenario where the lifecycle policy moves the blob back to the archive tier. This can happen if the last modified time, creation time, or last access time is beyond the threshold set for the policy. There are three ways to prevent this from happening: