Update lifecycle-management-best-practices.md

fixed links

Author: vgs-msft

articles/storage/blobs/lifecycle-management-best-practices.md

@@ -19,7 +19,7 @@ There are many factors that influence the execution time that Lifecycle Manageme
 
 Lifecycle policies enable users to create filter sets (prefix or file path) if they want to scope which subset of objects in the storage account should be processed by Lifecycle Management. If no scope is used or broad scopes are defined, then a large number of objects might need to be processed by Lifecycle Management and this might increase the time needed for the policy to complete.  Additionally, if a significant percentage of objects meet the policy conditions, especially the first time LCM is enabled on a storage account or broadly scoped policies with substantial number of objects, could also increase the processing time.  
 
-All requests made to storage account, including requests made by Lifecycle policy runs, accrue to the same limit on requests per second, and as that limit approaches, priority is given to requests made by workloads. The latency of processing objects also increases if the scalability and performance limits of the storage account are reached. This is particularly relevant for operations that need to be performed within specific time frames.  Learn more about [Scalability and performance targets for standard storage accounts](https://learn.microsoft.com/en-us/azure/storage/common/scalability-targets-standard-account).
+All requests made to storage account, including requests made by Lifecycle policy runs, accrue to the same limit on requests per second, and as that limit approaches, priority is given to requests made by workloads. The latency of processing objects also increases if the scalability and performance limits of the storage account are reached. This is particularly relevant for operations that need to be performed within specific time frames.  Learn more about [Scalability and performance targets for standard storage accounts](../common/scalability-targets-standard-accounts.md).
 
 Lifecycle Management also prioritizes customer workloads that utilize or impact the storage account. This allows for customer workloads to run with limited to no interruptions however, it can impact the rate of objects processed by Lifecycle Management. In such cases it is possible that the rate of object creation and modification is higher than the rate at which Lifecycle Management can process the storage account.  
 
@@ -32,13 +32,13 @@ Any of the above conditions could lead Lifecycle Management to take multiple day
 ### Narrow the Scope of the Lifecycle Policy
 In cases where Lifecycle Management is taking a long time to complete a run, it is advisable to apply filter sets to narrow the scope of the search and evaluation thereby enabling Lifecycle Management to optimize the operations. This can be done by adding Prefixes and/or Blob Index tags while authoring the lifecycle rules. 
   > [!TIP] 
-> Use [Azure Storage Copilot](https://learn.microsoft.com/en-us/azure/copilot/improve-storage-accounts#reduce-storage-costs) to help configure an Lifecycle Management  policy.
+> Use [Azure Storage Copilot](/azure/copilot/improve-storage-accounts#reduce-storage-costs) to help configure an Lifecycle Management policy.
 
 ### Optimize for Storage and Transactions costs
 
-It may be more cost effective for the small objects to stay in their current tier, than paying transaction costs to move them to cheaper storage tiers. Avoid moving small files to lower tiers, unless required. [Learn more](https://learn.microsoft.com/en-us/azure/storage/blobs/access-tiers-best-practices#pack-small-files-before-moving-data-to-cooler-tiers) about choosing the right storage tier.
+It may be more cost effective for the small objects to stay in their current tier, than paying transaction costs to move them to cheaper storage tiers. Avoid moving small files to lower tiers, unless required. [Learn more](./access-tiers-best-practices#pack-small-files-before-moving-data-to-cooler-tiers) about choosing the right storage tier.
   > [!TIP] 
-> [Azure Storage Actions](https://learn.microsoft.com/en-us/azure/storage-actions/overview) supports size-based object targeting, and tiering/deleting operations.
+> [Azure Storage Actions](../../storage-actions/overview) supports size-based object targeting, and tiering/deleting operations.
 
 ### Set appropriate Time-based Rules
 Avoid policy conditions using a short duration between object Creation/Modification/Last Access time and the intended operation by the policy. Lifecycle Management can take up to 24 hours to begin processing once the prior run is completed. Policy changes and updates can also take up to 24 hours to go into effect. This includes deleting all the rules to make a policy inactive. Policies that take multiple days to complete may not operate on objects evaluated earlier in the run but meet the conditions over the run period.
@@ -47,9 +47,9 @@ Avoid policy conditions using a short duration between object Creation/Modificat
 The request rate and bandwidth of your storage account depend on object size, access patterns, and workload type. Lifecycle Management may experience a slower rate of processing objects during high traffic workloads. If you consistently notice the storage account reaching the account limits and a slowdown in Lifecycle management processing, request an increase in account limits. Lifecycle management performance may improve based on the resource allocation by workload prioritization. Contact [Azure Support](https://azure.microsoft.com/support/faq/) to request an increase.
 
 ### Setup Troubleshooting and Monitoring
-Periodically evaluating the performance of your Lifecycle Management Policy is recommended. Setup [Event Grid Notifications](https://learn.microsoft.com/en-us/azure/event-grid/blob-event-quickstart-portal) to get notified on when an Lifecycle Management run completed. Use Storage Logs in [Azure Monitor](https://learn.microsoft.com/en-us/azure/storage/blobs/monitor-blob-storage?tabs=azure-portal) to dive into run details.
+Periodically evaluating the performance of your Lifecycle Management Policy is recommended. Setup [Event Grid Notifications](../../event-grid/blob-event-quickstart-portal) to get notified on when an Lifecycle Management run completed. Use Storage Logs in [Azure Monitor](monitor-blob-storage?tabs=azure-portal) to dive into run details.
 
 ## Next Steps
-- [Blob Storage FAQ](articles/storage/blobs/storage-blob-faq.yml)
+- [Blob Storage FAQ](storage-blob-faq.yml)
 - [Configure a lifecycle management policy](lifecycle-management-policy-configure.md)
-- [Plan and manage Costs for Blob Storage](https://learn.microsoft.com/en-us/azure/storage/common/storage-plan-manage-costs?toc=%2Fazure%2Fstorage%2Fblobs%2Ftoc.json&bc=%2Fazure%2Fstorage%2Fblobs%2Fbreadcrumb%2Ftoc.json)
+- [Plan and manage Costs for Blob Storage](../../common/storage-plan-manage-costs?toc=%2Fazure%2Fstorage%2Fblobs%2Ftoc.json&bc=%2Fazure%2Fstorage%2Fblobs%2Fbreadcrumb%2Ftoc.json)