Merge pull request #7180 from gmndrg/main

Debug sessions update for clarification on functionality

Author: prmerger-automator[bot]

articles/search/cognitive-search-common-errors-warnings.md

@@ -9,7 +9,7 @@ ms.service: azure-ai-search
 ms.custom:
   - ignite-2023
 ms.topic: concept-article
-ms.date: 02/19/2025
+ms.date: 09/21/2025
 ms.update-cycle: 180-days
 ---
 
@@ -423,3 +423,13 @@ This error usually happens in Azure SQL indexers when the source column type use
 For example, if the column used for change detection is of type datetime, but the indexer expects a rowversion type because convertHighWaterMarkToRowVersion is enabled, the mismatch will cause an error.
 
 Check the data type for the 'High Water Mark' column in the source and update the indexer configuration accordingly. Once verified and updated, reset and rerun the indexer to process the column values.
+
+## `Error: Access denied to Virtual Network/Firewall rules.`
+
+This error typically occurs due to one of the following:
+- Firewall restrictions on Azure resources required by your indexer, depending on your configuration. These resources may include: the [data source](search-data-sources-gallery.md#generally-available-data-sources-by-azure-ai-search), Azure Storage account (used for [debug sessions](cognitive-search-debug-session.md), [incremental enrichment](cognitive-search-incremental-indexing-conceptual.md) or [knowledge store](knowledge-store-concept-intro.md)), Azure Function (used for [web API custom skills](cognitive-search-custom-skill-web-api.md)) or AI Services / AI Foundry deployments used during [AI enrichment](cognitive-search-concept-intro.md).
+- Private endpoint configurations that block access from the indexer to those resources.
+
+Ensure that the indexer has access to your setup components by reviewing your resource configurations to confirm they allow traffic to all required services:
+- [Firewall and IP restriction settings](search-indexer-howto-access-ip-restricted.md)
+- [Shared private link setup](search-indexer-howto-access-private.md)

articles/search/cognitive-search-debug-session.md

@@ -9,7 +9,7 @@ ms.service: azure-ai-search
 ms.custom:
   - ignite-2023
 ms.topic: conceptual
-ms.date: 04/10/2025
+ms.date: 09/21/2025
 ms.update-cycle: 365-days
 ---
 
@@ -55,7 +55,7 @@ Debug Sessions work with all generally available [indexer data sources](search-d
 
 + Data sources with encryption enabled via [customer managed keys (CMK)](search-security-manage-encryption-keys.md).
 
-+ Currently, the ability to select which document to debug is unavailable. This limitation isn't permanent and will be lifted soon. At this time, Debug Sessions selects the first document in the source data container or folder.
++ Currently, the ability to select which document to debug is unavailable. This limitation isn't permanent and should be lifted soon. At this time, Debug Sessions selects the first document in the source data container or folder.
 
 ## How a debug session works
 
@@ -65,6 +65,9 @@ A cached copy of the enriched document and skillset is loaded into the visual ed
 
 If the enrichment pipeline doesn't have any errors, a debug session can be used to incrementally enrich a document, test and validate each change before committing the changes.
 
+Debug sessions help identify the root cause of errors or warnings by analyzing the data, skill inputs and outputs, and field mappings. If the indexer encounters configuration issues, such as incorrect network setup, permission-related access errors, or similar, please review the specific error message along with the linked documentation provided. For troubleshooting guidance, refer to the [common indexer errors and warnings](cognitive-search-common-errors-warnings.md).
+
+
 ## Debug session layout
 
 The visual editor is organized into a surface area showing a progression of operations, starting with document cracking, followed by skills, mappings, and an index.