Update storage-lifecycle-management-concepts.md

Author: xyh1

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

@@ -20,7 +20,7 @@ The lifecycle management policy lets you:
 - Transition blobs to a cooler storage tier (hot to cool, hot to archive, or cool to archive) to optimize for performance and cost
 - Delete blobs at the end of their lifecycles
 - Define rules to be run once per day at the storage account level
-- Apply rules to containers or a subset of blobs (using name prefixes or [blob index tags](storage-manage-and-find-blobs.md) as filters)
+- Apply rules to containers or a subset of blobs (using name prefixes or [blob index tags](storage-manage-find-blobs.md) as filters)
 
 Consider a scenario where data gets frequent access during the early stages of the lifecycle, but only occasionally after two weeks. Beyond the first month, the data set is rarely accessed. In this scenario, hot storage is best during the early stages. Cool storage is most appropriate for occasional access. Archive storage is the best tier option after the data ages over a month. By adjusting storage tiers in respect to the age of data, you can design the least expensive storage options for your needs. To achieve this transition, lifecycle management policy rules are available to move aging data to cooler tiers.
 
@@ -292,7 +292,7 @@ Filters include:
 | blobIndexMatch | An array of dictionary values consisting of Blob Index tag key and value conditions to be matched. Each rule can define up to 10 Blob Index tag condition. For example, if you want to match all blobs with `Project = Contoso` under `https://myaccount.blob.core.windows.net/` for a rule, the blobIndexMatch is `{"name": "Project","op": "==","value": "Contoso"}`. | If you don't define blobIndexMatch, the rule applies to all blobs within the storage account. | No |
 
 > [!NOTE]
-> Blob Index is in public preview, and is available in the **France Central** and **France South** regions. To learn more about this feature along with known issues and limitations, see [Manage and find data on Azure Blob Storage with Blob Index (Preview)](storage-manage-and-find-blobs.md).
+> Blob Index is in public preview, and is available in the **France Central** and **France South** regions. To learn more about this feature along with known issues and limitations, see [Manage and find data on Azure Blob Storage with Blob Index (Preview)](storage-manage-find-blobs.md).
 
 ### Rule actions
 
@@ -406,7 +406,7 @@ Some data is expected to expire days or months after creation. You can configure
 ```
 
 ### Delete data with Blob Index tags
-Some data should only be expired if explicitly marked for deletion. You can configure a lifecycle management policy to expire data that are tagged with blob index key/value attributes. The following example shows a policy that deletes all block blobs tagged with `Project = Contoso`. To learn more about the Blob Index, see [Manage and find data on Azure Blob Storage with Blob Index (Preview)](storage-manage-and-find-blobs.md).
+Some data should only be expired if explicitly marked for deletion. You can configure a lifecycle management policy to expire data that are tagged with blob index key/value attributes. The following example shows a policy that deletes all block blobs tagged with `Project = Contoso`. To learn more about the Blob Index, see [Manage and find data on Azure Blob Storage with Blob Index (Preview)](storage-manage-find-blobs.md).
 
 ```json
 {
@@ -484,3 +484,7 @@ When a blob is moved from one access tier to another, its last modification time
 Learn how to recover data after accidental deletion:
 
 - [Soft delete for Azure Storage blobs](../blobs/storage-blob-soft-delete.md)
+
+Learn how to manage and find data with Blob Index:
+
+- [Manage and find data on Azure Blob Storage with Blob Index](storage-manage-find-blobs.md)