Skip to content

Commit f5e51d8

Browse files
Merge pull request #7181 from MicrosoftDocs/main
Auto Publish – main to live - 2025-09-22 05:01 UTC
2 parents 8392214 + b94a579 commit f5e51d8

File tree

4 files changed

+20
-6
lines changed

4 files changed

+20
-6
lines changed

articles/ai-foundry/concepts/a-b-experimentation.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ ms.service: azure-ai-foundry
99
ms.custom:
1010
- ignite-2024
1111
ms.topic: concept-article
12-
ms.date: 07/02/2025
12+
ms.date: 09/18/2025
1313

1414
#CustomerIntent: As an AI application developer, I want to learn about A/B experiments so that I can evaluate and improve my applications.
1515
---

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

Lines changed: 11 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ ms.service: azure-ai-search
99
ms.custom:
1010
- ignite-2023
1111
ms.topic: concept-article
12-
ms.date: 02/19/2025
12+
ms.date: 09/21/2025
1313
ms.update-cycle: 180-days
1414
---
1515

@@ -423,3 +423,13 @@ This error usually happens in Azure SQL indexers when the source column type use
423423
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.
424424

425425
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.
426+
427+
## `Error: Access denied to Virtual Network/Firewall rules.`
428+
429+
This error typically occurs due to one of the following:
430+
- 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).
431+
- Private endpoint configurations that block access from the indexer to those resources.
432+
433+
Ensure that the indexer has access to your setup components by reviewing your resource configurations to confirm they allow traffic to all required services:
434+
- [Firewall and IP restriction settings](search-indexer-howto-access-ip-restricted.md)
435+
- [Shared private link setup](search-indexer-howto-access-private.md)

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

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ ms.service: azure-ai-search
99
ms.custom:
1010
- ignite-2023
1111
ms.topic: conceptual
12-
ms.date: 04/10/2025
12+
ms.date: 09/21/2025
1313
ms.update-cycle: 365-days
1414
---
1515

@@ -55,7 +55,7 @@ Debug Sessions work with all generally available [indexer data sources](search-d
5555

5656
+ Data sources with encryption enabled via [customer managed keys (CMK)](search-security-manage-encryption-keys.md).
5757

58-
+ 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.
58+
+ 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.
5959

6060
## How a debug session works
6161

@@ -65,6 +65,9 @@ A cached copy of the enriched document and skillset is loaded into the visual ed
6565

6666
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.
6767

68+
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).
69+
70+
6871
## Debug session layout
6972

7073
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.

articles/search/cognitive-search-skill-document-intelligence-layout.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ ms.custom:
99
- references_regions
1010
- ignite-2024
1111
ms.topic: reference
12-
ms.date: 07/10/2025
12+
ms.date: 09/19/2025
1313
ms.update-cycle: 365-days
1414
---
1515

@@ -34,9 +34,10 @@ This skill is bound to a [billable Azure AI multi-service resource](cognitive-se
3434
3535
## Limitations
3636

37-
During the public preview, this skill has the following restrictions:
37+
This skill has the following limitations:
3838

3939
+ The skill isn't suitable for large documents requiring more than 5 minutes of processing in the AI Document Intelligence layout model. The skill times out, but charges still apply to the AI Services multi-services resource if it attaches to the skillset for billing purposes. Ensure documents are optimized to stay within processing limits to avoid unnecessary costs.
40+
+ Since this skill calls the Azure AI Document Intelligence layout model, all documented [service behaviors for different document types](/azure/ai-services/document-intelligence/prebuilt/layout#pages) for different file types apply to its output. For example, Word (DOCX) and PDF files may produce different results due to differences in how images are handled. If consistent image behavior across DOCX and PDF is required, consider converting documents to PDF or reviewing the [multimodal search documentation](multimodal-search-overview.md) for alternative approaches.
4041

4142
## Supported regions
4243

0 commit comments

Comments
 (0)