fixed more validation errors

Author: HeidiSteen

articles/search/.openpublishing.redirection.search.json

@@ -537,7 +537,7 @@
             "redirect_document_id": true
         },
         {
-            "source_path_from_root": "/articles/search/search-howto-index-csv-blobs.md",
+            "source_path_from_root": "/articles/search/search-how-to-index-csv-blobs.md",
             "redirect_url": "/azure/search/search-how-to-index-azure-blob-csv",
             "redirect_document_id": true
         },

articles/search/search-blob-indexer-role-based-access.md

@@ -184,7 +184,7 @@ Assuming no errors, the index is now populated and you can move forward with [qu
 
 ## Deletion tracking 
 
-To effectively manage blob deletion, ensure that you have enabled [deletion tracking](search-how-to-index-changed-deleted-blobs.md) before your indexer runs for the first time. This feature allows the system to detect deleted blobs from your source and delete the corresponding content from the index.  
+To effectively manage blob deletion, ensure that you have enabled [deletion tracking](search-how-to-index-azure-blob-changed-deleted.md) before your indexer runs for the first time. This feature allows the system to detect deleted blobs from your source and delete the corresponding content from the index.  
 
 ## See also
 

articles/search/search-file-storage-integration.md

@@ -46,7 +46,7 @@ To configure and run the indexer, you can use:
 You can use this indexer for the following tasks:
 
 + **Data indexing and incremental indexing:** The indexer can index files and associated metadata from tables. It detects new and updated files and metadata through built-in change detection. You can configure data refresh on a schedule or on demand.
-+ **Deletion detection:** The indexer can [detect deletions through custom metadata](search-how-to-index-changed-deleted-blobs.md).
++ **Deletion detection:** The indexer can [detect deletions through custom metadata](search-how-to-index-azure-blob-changed-deleted.md).
 + **Applied AI through skillsets:** [Skillsets](cognitive-search-concept-intro.md) are fully supported by the indexer. This includes key features like [integrated vectorization](vector-search-integrated-vectorization.md) that adds data chunking and embedding steps.
 + **Parsing modes:** The indexer supports [JSON parsing modes](search-how-to-index-azure-blob-json.md) if you want to parse JSON arrays or lines into individual search documents. It also supports [Markdown parsing mode](search-how-to-index-azure-blob-markdown.md).
 + **Compatibility with other features:** The indexer is designed to work seamlessly with other indexer features, such as [debug sessions](cognitive-search-debug-session.md), [indexer cache for incremental enrichments](enrichment-cache-how-to-configure.md), and [knowledge store](knowledge-store-concept-intro.md).
@@ -89,7 +89,7 @@ You can use 2020-06-30-preview or later for "type": `"azurefile"`. We recommend
 
 1. Set "container" to the root file share, and use "query" to specify any subfolders.
 
-A data source definition can also include [soft deletion policies](search-how-to-index-changed-deleted-blobs.md), if you want the indexer to delete a search document when the source document is flagged for deletion.
+A data source definition can also include [soft deletion policies](search-how-to-index-azure-blob-changed-deleted.md), if you want the indexer to delete a search document when the source document is flagged for deletion.
 
 <a name="Credentials"></a>
 
@@ -231,5 +231,5 @@ Execution history contains up to 50 of the most recently completed executions, w
 
 You can now [run the indexer](search-howto-run-reset-indexers.md), [monitor status](search-monitor-indexers.md), or [schedule indexer execution](search-howto-schedule-indexers.md). The following articles apply to indexers that pull content from Azure Storage:
 
-+ [Change detection and deletion detection](search-how-to-index-changed-deleted-blobs.md)
++ [Change detection and deletion detection](search-how-to-index-azure-blob-changed-deleted.md)
 + [Index large data sets](search-howto-large-index.md)

articles/search/search-get-started-portal-import-vectors.md

@@ -117,9 +117,9 @@ This section points you to the content that works for this quickstart. Before yo
 
 1. (Optional) Synchronize deletions in your container with deletions in the search index. To configure your indexer for deletion detection:
 
-   1. [Enable soft delete](/azure/storage/blobs/soft-delete-blob-enable?tabs=azure-portal#enable-blob-soft-delete-hierarchical-namespace) on your storage account. If you're using [native soft delete](search-how-to-index-changed-deleted-blobs.md#native-blob-soft-delete), the next step isn't required.
+   1. [Enable soft delete](/azure/storage/blobs/soft-delete-blob-enable?tabs=azure-portal#enable-blob-soft-delete-hierarchical-namespace) on your storage account. If you're using [native soft delete](search-how-to-index-azure-blob-changed-deleted.md#native-blob-soft-delete), the next step isn't required.
 
-   1. [Add custom metadata](search-how-to-index-changed-deleted-blobs.md#soft-delete-strategy-using-custom-metadata) that an indexer can scan to determine which blobs are marked for deletion. Give your custom property a descriptive name. For example, you can name the property "IsDeleted" and set it to false. Repeat this step for every blob in the container. When you want to delete the blob, change the property to true. For more information, see [Change and delete detection when indexing from Azure Storage](search-how-to-index-changed-deleted-blobs.md).
+   1. [Add custom metadata](search-how-to-index-azure-blob-changed-deleted.md#soft-delete-strategy-using-custom-metadata) that an indexer can scan to determine which blobs are marked for deletion. Give your custom property a descriptive name. For example, you can name the property "IsDeleted" and set it to false. Repeat this step for every blob in the container. When you want to delete the blob, change the property to true. For more information, see [Change and delete detection when indexing from Azure Storage](search-how-to-index-azure-blob-changed-deleted.md).
 
 ### [ADLS Gen2](#tab/sample-data-adlsgen2)
 
@@ -145,7 +145,7 @@ This section points you to the content that works for this quickstart. Before yo
 
    1. [Enable soft delete](/azure/storage/blobs/soft-delete-blob-enable?tabs=azure-portal#enable-blob-soft-delete-hierarchical-namespace) on your storage account.
 
-   1. [Add custom metadata](search-how-to-index-changed-deleted-blobs.md#soft-delete-strategy-using-custom-metadata) that an indexer can scan to determine which blobs are marked for deletion. Give your custom property a descriptive name. For example, you can name the property "IsDeleted" and set it to false. Repeat this step for every blob in the container. When you want to delete the blob, change the property to true. For more information, see [Change and delete detection when indexing from Azure Storage](search-how-to-index-changed-deleted-blobs.md).
+   1. [Add custom metadata](search-how-to-index-azure-blob-changed-deleted.md#soft-delete-strategy-using-custom-metadata) that an indexer can scan to determine which blobs are marked for deletion. Give your custom property a descriptive name. For example, you can name the property "IsDeleted" and set it to false. Repeat this step for every blob in the container. When you want to delete the blob, change the property to true. For more information, see [Change and delete detection when indexing from Azure Storage](search-how-to-index-azure-blob-changed-deleted.md).
 
 ### [OneLake](#tab/sample-data-onelake)
 

articles/search/search-how-to-create-indexers.md

@@ -242,7 +242,7 @@ If your data source supports change detection, an indexer can detect underlying
 
 Change detection logic is built into the data platforms. How an indexer supports change detection varies by data source:
 
-+ Azure Storage has built-in change detection, which means an indexer can recognize new and updated documents automatically. Blob Storage, Azure Table Storage, and Azure Data Lake Storage Gen2 stamp each blob or row update with a date and time. An indexer automatically uses this information to determine which documents to update in the index. For more information about deletion detection, see [Change and delete detection using indexers for Azure Storage](search-how-to-index-changed-deleted-blobs.md).
++ Azure Storage has built-in change detection, which means an indexer can recognize new and updated documents automatically. Blob Storage, Azure Table Storage, and Azure Data Lake Storage Gen2 stamp each blob or row update with a date and time. An indexer automatically uses this information to determine which documents to update in the index. For more information about deletion detection, see [Change and delete detection using indexers for Azure Storage](search-how-to-index-azure-blob-changed-deleted.md).
 
 + Cloud database technologies provide optional change detection features in their platforms. For these data sources, change detection isn't automatic. You need to specify in the data source definition which policy is used:
 

articles/search/search-how-to-define-index-projections.md

@@ -295,7 +295,7 @@ If you add new content to your data source, new chunks or child documents are ad
 
 If you modify existing content in the data source, chunks are updated incrementally in the search index if the data source you're using supports change tracking and deletion detection. For example, if a word or sentence changes in a document, the chunk in the target index that contains that word or sentence is updated on the next indexer run. Other types of updates, such as changing a field type and some attributions, aren't supported for existing fields. For more information about allowed updates, see [Update an index schema](search-howto-reindex.md#update-an-index-schema).
 
-Some data sources like [Azure Storage](search-how-to-index-changed-deleted-blobs.md) support change and deletion tracking by default, based on the timestamp. Other data sources such as [Microsoft OneLake](search-how-to-index-onelake-files.md), [Azure SQL](search-how-to-index-sql-database.md), or [Azure Cosmos DB](search-how-to-index-cosmosdb-sql.md) must be configured for change tracking.
+Some data sources like [Azure Storage](search-how-to-index-azure-blob-changed-deleted.md) support change and deletion tracking by default, based on the timestamp. Other data sources such as [Microsoft OneLake](search-how-to-index-onelake-files.md), [Azure SQL](search-how-to-index-sql-database.md), or [Azure Cosmos DB](search-how-to-index-cosmosdb-sql.md) must be configured for change tracking.
 
 ### Deleted content
 

articles/search/search-how-to-index-azure-blob-markdown.md

@@ -472,7 +472,7 @@ In `oneToOne` mode, the entire Markdown file is indexed as a single search docum
 To ensure the index reflects the current state of your Markdown files, consider one of the following approaches:
 
 #### Option 1. Soft delete with metadata
-This method uses a soft-delete to delete documents associated with a specific blob. For more information, see [Change and delete detection using indexers for Azure Storage in Azure AI Search](search-how-to-index-changed-deleted-blobs.md#soft-delete-strategy-using-custom-metadata).
+This method uses a soft-delete to delete documents associated with a specific blob. For more information, see [Change and delete detection using indexers for Azure Storage in Azure AI Search](search-how-to-index-azure-blob-changed-deleted.md#soft-delete-strategy-using-custom-metadata).
 
 Steps:
 

articles/search/search-how-to-index-azure-blob-storage.md

@@ -50,7 +50,7 @@ This article uses the REST APIs to illustrate each step.
 You can use this indexer for the following tasks:
 
 + **Data indexing and incremental indexing:** The indexer can index files and associated metadata from blob containers and folders. It detects new and updated files and metadata through built-in change detection. You can configure data refresh on a schedule or on demand. 
-+ **Deletion detection:** The indexer can [detect deletions through native soft delete or through custom metadata](search-how-to-index-changed-deleted-blobs.md).
++ **Deletion detection:** The indexer can [detect deletions through native soft delete or through custom metadata](search-how-to-index-azure-blob-changed-deleted.md).
 + **Applied AI through skillsets:** [Skillsets](cognitive-search-concept-intro.md) are fully supported by the indexer. This includes key features like [integrated vectorization](vector-search-integrated-vectorization.md) that adds data chunking and embedding steps.
 + **Parsing modes:** The indexer supports [JSON parsing modes](search-how-to-index-azure-blob-json.md) if you want to parse JSON arrays or lines into individual search documents. It also supports [Markdown parsing mode](search-how-to-index-azure-blob-markdown.md).
 + **Compatibility with other features:** The indexer is designed to work seamlessly with other indexer features, such as [debug sessions](cognitive-search-debug-session.md), [indexer cache for incremental enrichments](enrichment-cache-how-to-configure.md), and [knowledge store](knowledge-store-concept-intro.md).
@@ -140,7 +140,7 @@ The data source definition specifies the data to index, credentials, and policie
 
 1. Set "container" to the blob container, and use "query" to specify any subfolders.
 
-A data source definition can also include [soft deletion policies](search-how-to-index-changed-deleted-blobs.md), if you want the indexer to delete a search document when the source document is flagged for deletion.
+A data source definition can also include [soft deletion policies](search-how-to-index-azure-blob-changed-deleted.md), if you want the indexer to delete a search document when the source document is flagged for deletion.
 
 <a name="credentials"></a>
 
@@ -396,6 +396,6 @@ PUT /indexers/[indexer name]?api-version=2025-09-01
 
 ## See also
 
-+ [Change detection and deletion detection](search-how-to-index-changed-deleted-blobs.md)
++ [Change detection and deletion detection](search-how-to-index-azure-blob-changed-deleted.md)
 + [Index large data sets](search-howto-large-index.md)
 + [Indexer access to content protected by Azure network security features](search-indexer-securing-resources.md)

articles/search/search-how-to-index-azure-data-lake-storage.md

@@ -115,7 +115,7 @@ The data source definition specifies the data to index, credentials, and policie
 
 1. Set `"container"` to the blob container, and use "query" to specify any subfolders.
 
-A data source definition can also include [soft deletion policies](search-how-to-index-changed-deleted-blobs.md), if you want the indexer to delete a search document when the source document is flagged for deletion.
+A data source definition can also include [soft deletion policies](search-how-to-index-azure-blob-changed-deleted.md), if you want the indexer to delete a search document when the source document is flagged for deletion.
 
 <a name="Credentials"></a>
 
@@ -316,6 +316,6 @@ PUT /indexers/[indexer name]?api-version=2025-09-01
 
 You can now [run the indexer](search-howto-run-reset-indexers.md), [monitor status](search-monitor-indexers.md), or [schedule indexer execution](search-howto-schedule-indexers.md). The following articles apply to indexers that pull content from Azure Storage:
 
-+ [Change detection and deletion detection](search-how-to-index-changed-deleted-blobs.md)
++ [Change detection and deletion detection](search-how-to-index-azure-blob-changed-deleted.md)
 + [Index large data sets](search-howto-large-index.md)
 + [C# Sample: Index Data Lake Gen2 using Microsoft Entra ID](https://github.com/Azure-Samples/azure-search-dotnet-utilities/blob/main/data-lake-gen2-acl-indexing/README.md)

articles/search/search-how-to-index-azure-tables.md

@@ -117,7 +117,7 @@ The data source definition specifies the source data to index, credentials, and
 
 1. Optionally, set "query" to a filter on PartitionKey. Setting this property is a best practice that improves performance. If "query" is null, the indexer executes a full table scan, which can result in poor performance if the tables are large.
 
-A data source definition can also include [soft deletion policies](search-how-to-index-changed-deleted-blobs.md), if you want the indexer to delete a search document when the source document is flagged for deletion.
+A data source definition can also include [soft deletion policies](search-how-to-index-azure-blob-changed-deleted.md), if you want the indexer to delete a search document when the source document is flagged for deletion.
 
 <a name="Credentials"></a>