Merge branch 'MicrosoftDocs:main' into main

Author: gmndrg

articles/ai-services/speech-service/includes/intent-recognition-retire.md

@@ -3,11 +3,11 @@ author: goergenj
 manager: nitinme
 ms.service: azure-ai-speech
 ms.topic: include
-ms.date: 07/09/2025
+ms.date: 10/06/2025
 ms.author: jagoerge
 ---
 
 > [!IMPORTANT]
-> Intent recognition in Azure AI Speech is being retired on September 30, 2025. Your applications won't be able to use intent recognition directly via Azure AI Speech after this date. However, you're still able to perform intent recognition using Azure AI Language Service or Azure OpenAI.
+> Intent recognition in Azure AI Speech was retired on September 30, 2025. Applications can no longer use intent recognition via Azure AI Speech. However, you're still able to perform intent recognition using Azure AI Language Service or Azure OpenAI.
 > 
 > This change doesn't affect other Azure AI Speech capabilities such as [speech to text](../speech-to-text.md) (including no change to speaker diarization), [text to speech](../text-to-speech.md), and [speech translation](../speech-translation.md). 

articles/ai-services/speech-service/includes/retire-speaker-recognition.md

@@ -8,6 +8,6 @@ ms.author: pafarley
 ---
 
 > [!IMPORTANT]
-> Speaker recognition in Azure AI Speech will be retired on September 30th 2025. Your applications won't be able to use speaker recognition after this date.
+> Speaker recognition in Azure AI Speech was retired on September 30th, 2025. Applications can no longer use the speaker recognition APIs.
 > 
-> This change doesn't affect other Azure AI Speech capabilities such as [speech to text](../speech-to-text.md) (including no change to speaker diarization), [text to speech](../text-to-speech.md), and [speech translation](../speech-translation.md). 
+> This change doesn't affect other Azure AI Speech capabilities such as [speech to text](../speech-to-text.md) (including no change to speaker diarization), [text to speech](../text-to-speech.md), and [speech translation](../speech-translation.md).

articles/search/cognitive-search-concept-intro.md

@@ -10,27 +10,27 @@ ms.custom:
   - build-2024
   - ignite-2024
 ms.topic: concept-article
-ms.date: 03/11/2025
+ms.date: 10/06/2025
 ms.update-cycle: 365-days
 ---
 
 # Skills for extra processing during indexing (Azure AI Search)
 
-This article describes the skills in Azure AI Search that you can include in a [skillset](cognitive-search-working-with-skillsets.md) to access external processing. 
+This article describes the skills in Azure AI Search that you can include in a [skillset](cognitive-search-working-with-skillsets.md) to access external processing.
 
-A *skill* is an atomic operation that transforms content in some way. Often, it's an operation that recognizes or extracts text, but it can also be a utility skill that reshapes the enrichments that are already created. Typically, the output is either text-based so that it can be used in [full text search](search-lucene-query-architecture.md), or vectors used in [vector search](vector-search-overview.md).
+A *skill* is an atomic operation that transforms content in some way. Often, it's an operation that recognizes or extracts text, but it can also be a utility skill that reshapes existing enrichments. The output is usually text-based for use in [full-text search](search-lucene-query-architecture.md) or vectors for use in [vector search](vector-search-overview.md).
 
-Skills are organized into categories:
+Skills are organized into the following categories:
 
-* A *built-in skill* wraps API calls to an Azure AI resource, where the inputs, outputs, and processing steps are well understood. For skills that call an Azure AI resource, the connection is made over the internal network. For skills that call Azure OpenAI, you provide the connection information that the search service uses to connect to the resource. A small quantity of processing is non-billable, but at larger volumes, processing is billable. Built-in skills are based on pretrained models from Microsoft, which means you can't train the model using your own training data.
+* A *built-in skill* wraps API calls to an Azure AI resource, where the inputs, outputs, and processing steps are well understood. For skills that call an Azure AI resource, the connection is made over the internal network. For skills that call Azure OpenAI, you provide the connection information that the search service uses to connect to the resource. A small quantity of processing is nonbillable, but at larger volumes, processing is billable. Built-in skills are based on pretrained models from Microsoft, which means you can't train the model using your own training data.
 
 * A *custom skill* provides custom code that executes externally to the search service. It's accessed through a URI. Custom code is often made available through an Azure function app. To attach an open-source or third-party vectorization model, use a custom skill.
 
-* A *utility* is internal to Azure AI Search, with no dependency on external resources or outbound connections. Most utilities are non-billable.
+* A *utility* is internal to Azure AI Search, with no dependency on external resources or outbound connections. Most utilities are nonbillable.
 
 ## Azure AI resource skills
 
-Skills that call the Azure AI are billed at the Standard rate when you [attach an AI service resource](cognitive-search-attach-cognitive-services.md).
+Skills that call Azure AI are billed at the Standard rate when you [attach an Azure AI services multi-service resource](cognitive-search-attach-cognitive-services.md).
 
 | OData type  | Description | Metered by |
 |-------|-------------|-------------|
@@ -55,18 +55,6 @@ Skills that call models deployed on Azure OpenAI are billed at the Standard rate
 |-------|-------------|-------------|
 |[Microsoft.Skills.Text.AzureOpenAIEmbeddingSkill](cognitive-search-skill-azure-openai-embedding.md) | Connects to a deployed embedding model on Azure OpenAI for integrated vectorization. | Azure OpenAI ([pricing](https://azure.microsoft.com/pricing/details/cognitive-services/openai-service/#pricing)) |
 
-## Utility skills
-
-Skills that execute only on Azure AI Search, iterate mostly on nodes in the enrichment cache, and are mostly non-billable.
-
-| OData type  | Description | Metered by |
-|-------|-------------|-------------|
-| [Microsoft.Skills.Util.ConditionalSkill](cognitive-search-skill-conditional.md) | Allows filtering, assigning a default value, and merging data based on a condition. | Not applicable |
-| [Microsoft.Skills.Util.DocumentExtractionSkill](cognitive-search-skill-document-extraction.md) | Extracts content from a file within the enrichment pipeline. | Azure AI Search ([pricing](https://azure.microsoft.com/pricing/details/search/)) for image extraction. |
-| [Microsoft.Skills.Text.MergeSkill](cognitive-search-skill-textmerger.md) | Consolidates text from a collection of fields into a single field.  | Not applicable |
-| [Microsoft.Skills.Util.ShaperSkill](cognitive-search-skill-shaper.md) | Maps output to a complex type (a multi-part data type, which might be used for a full name, a multi-line address, or a combination of last name and a personal identifier.) | Not applicable |
-| [Microsoft.Skills.Text.SplitSkill](cognitive-search-skill-textsplit.md) | Splits text into pages so that you can enrich or augment content incrementally. | Not applicable |
-
 ## Custom skills
 
 [Custom skills](cognitive-search-custom-skill-web-api.md) wrap external code that you design, develop, and deploy to the web. You can then call the module from within a skillset as a custom skill.
@@ -78,8 +66,20 @@ Skills that execute only on Azure AI Search, iterate mostly on nodes in the enri
 
 For guidance on creating a custom skill, see [Define a custom interface](cognitive-search-custom-skill-interface.md) and [Example: Creating a custom skill for AI enrichment](cognitive-search-create-custom-skill-example.md).
 
-## See also
+## Utility skills
+
+Skills that execute only on Azure AI Search, iterate mostly on nodes in the enrichment cache, and are mostly nonbillable.
+
+| OData type  | Description | Metered by |
+|-------|-------------|-------------|
+| [Microsoft.Skills.Util.ConditionalSkill](cognitive-search-skill-conditional.md) | Allows filtering, assigning a default value, and merging data based on a condition. | Not applicable |
+| [Microsoft.Skills.Util.DocumentExtractionSkill](cognitive-search-skill-document-extraction.md) | Extracts content from a file within the enrichment pipeline. | Azure AI Search ([pricing](https://azure.microsoft.com/pricing/details/search/)) for image extraction. |
+| [Microsoft.Skills.Text.MergeSkill](cognitive-search-skill-textmerger.md) | Consolidates text from a collection of fields into a single field.  | Not applicable |
+| [Microsoft.Skills.Util.ShaperSkill](cognitive-search-skill-shaper.md) | Maps output to a complex type (a multi-part data type, which might be used for a full name, a multi-line address, or a combination of last name and a personal identifier.) | Not applicable |
+| [Microsoft.Skills.Text.SplitSkill](cognitive-search-skill-textsplit.md) | Splits text into pages so that you can enrich or augment content incrementally. | Not applicable |
+
+## Related content
 
-+ [How to define a skillset](cognitive-search-defining-skillset.md)
-+ [Custom Skills interface definition](cognitive-search-custom-skill-interface.md)
++ [Create a skillset](cognitive-search-defining-skillset.md)
++ [Add a custom skill to an AI enrichment pipeline](cognitive-search-custom-skill-interface.md)
 + [Tutorial: Enriched indexing with AI](tutorial-skillset.md)

articles/search/cognitive-search-predefined-skills.md

@@ -9,7 +9,7 @@ ms.custom:
   - ignite-2023
   - build-2024
 ms.topic: reference
-ms.date: 09/26/2025
+ms.date: 10/06/2025
 ---
 
 #	Azure OpenAI Embedding skill
@@ -45,7 +45,7 @@ Parameters are case-sensitive.
 
 | Inputs | Description |
 |---------------------|-------------|
-| `resourceUri` | Required. The URI of the model provider. This parameter only supports URLs with the `openai.azure.com` domain, such as `https://<resourcename>.openai.azure.com`. If your Azure OpenAI endpoint has a URL with the `cognitiveservices.azure.com` domain, such as `https://<resourcename>.cognitiveservices.azure.com`, you must create a [custom subdomain](/azure/ai-services/openai/how-to/use-your-data-securely#enabled-custom-subdomain) with `openai.azure.com` for the Azure OpenAI resource and use `https://<resourcename>.openai.azure.com` instead. This field is required if your Azure OpenAI resource is deployed behind a private endpoint or uses Virtual Network (VNet) integration. [Azure API Management](/azure/api-management/api-management-key-concepts) endpoints are supported with URL `https://<resourcename>.azure-api.net `. Shared private links aren't supported for API Management endpoints.
+| `resourceUri` | Required. The URI of the model provider. This parameter only supports URLs with the `openai.azure.com` domain, such as `https://<resourcename>.openai.azure.com`. This field is required if your Azure OpenAI resource is deployed behind a private endpoint or uses Virtual Network (VNet) integration. [Azure API Management](/azure/api-management/api-management-key-concepts) endpoints are supported with URL `https://<resourcename>.azure-api.net`. Shared private links aren't supported for API Management endpoints. |
 | `apiKey`   |  The secret key used to access the model. If you provide a key, leave `authIdentity` empty. If you set both the `apiKey` and `authIdentity`, the `apiKey` is used on the connection. |
 | `deploymentId`   | Required. The name of the deployed Azure OpenAI embedding model. The model should be an embedding model, such as text-embedding-ada-002. See the [List of Azure OpenAI models](/azure/ai-services/openai/concepts/models) for supported models.|
 | `authIdentity`   | A user-managed identity used by the search service for connecting to Azure OpenAI. You can use either a [system or user managed identity](search-how-to-managed-identities.md). To use a system managed identity, leave `apiKey` and `authIdentity` blank. The system-managed identity is used automatically. A managed identity must have [Cognitive Services OpenAI User](/azure/ai-services/openai/how-to/role-based-access-control#azure-openai-roles) permissions to send text to Azure OpenAI. |

articles/search/cognitive-search-skill-azure-openai-embedding.md

@@ -13,7 +13,7 @@ ms.date: 03/07/2025
 ms.update-cycle: 365-days
 ---
 
-# Full text search in Azure AI Search
+# Full-text search in Azure AI Search
 
 Full text search is an approach in information retrieval that matches on plain text stored in an index. For example, given a query string "hotels in San Diego on the beach", the search engine looks for tokenized strings based on those terms. To make scans more efficient, query strings undergo lexical analysis: lower-casing all terms, removing stop words like "the", and reducing terms to primitive root forms. When matching terms are found, the search engine retrieves documents, ranks them in order of relevance, and returns the top results.
 

articles/search/search-lucene-query-architecture.md

@@ -1,11 +1,11 @@
 ---
 title: Supported Regions
 titleSuffix: Azure AI Search
-description: Shows supported regions and feature availability across regions for Azure AI Search.
+description: Learn about the regions that offer Azure AI Search and the features available in each region.
 author: haileytap
 ms.author: haileytapia
 manager: nitinme
-ms.date: 09/25/2025
+ms.date: 10/06/2025
 ms.service: azure-ai-search
 ms.topic: conceptual
 ms.custom:
@@ -121,16 +121,18 @@ You can create an Azure AI Search service in any of the following Azure public r
 
 ## Azure operated by 21Vianet
 
-| Region | AI enrichment | Availability zones | Agentic retrieval | Confidential computing | Semantic ranker | Query rewrite |
+| Region | AI enrichment <sup>1</sup> | Availability zones | Agentic retrieval | Confidential computing | Semantic ranker | Query rewrite |
 |--|--|--|--|--|--|--|
 | China East |  |  |  |  |  |  |
-| China East 2 <sup>1</sup> | ✅ |  |  |  |  |  |
+| China East 2 <sup>2</sup> | ✅ |  |  |  |  |  |
 | China East 3 |  |  |  |  |  |  |
 | China North |  |  |  |  |  |  |
-| China North 2 <sup>1</sup> |  |  |  |  |  |  |
+| China North 2 <sup>2</sup> |  |  |  |  |  |  |
 | China North 3 |  | ✅ | ✅ |  | ✅ | ✅ |
 
-<sup>1</sup> [Higher storage limits](search-limits-quotas-capacity.md#service-limits) aren't available in this region. If you want higher limits, choose a different region.
+<sup>1</sup> Only China East 2 fully supports AI enrichment. In other 21Vianet regions, you can use skillsets with the [Azure OpenAI Embedding skill](cognitive-search-skill-azure-openai-embedding.md) for integrated vectorization, which depends on the availability of Azure OpenAI and Azure AI Search in your region. Otherwise, AI enrichment isn't supported.
+
+<sup>2</sup> [Higher storage limits](search-limits-quotas-capacity.md#service-limits) aren't available in this region. If you want higher limits, choose a different region.
 
 ## Related content
 

articles/search/search-region-support.md

@@ -8,7 +8,7 @@ ms.service: azure-ai-search
 ms.custom:
   - build-2024
 ms.topic: reference
-ms.date: 09/26/2025
+ms.date: 10/06/2025
 ms.update-cycle: 365-days
 ---
 
@@ -39,7 +39,7 @@ Parameters are case-sensitive.
 
 | Parameter name	 | Description |
 |--------------------|-------------|
-| `resourceUri` | The URI of the model provider. This parameter only supports URLs with the `openai.azure.com` domain, such as `https://<resourcename>.openai.azure.com`. If your Azure OpenAI endpoint has a URL with the `cognitiveservices.azure.com` domain, such as `https://<resourcename>.cognitiveservices.azure.com`, you must create a [custom subdomain](/azure/ai-services/openai/how-to/use-your-data-securely#enabled-custom-subdomain) with `openai.azure.com` for the Azure OpenAI resource and use `https://<resourcename>.openai.azure.com` instead. [Azure API Management](/azure/api-management/api-management-key-concepts) endpoints are supported with URL `https://<resourcename>.azure-api.net `. Shared private links aren't supported for API Management endpoints. |
+| `resourceUri` | The URI of the model provider. This parameter only supports URLs with the `openai.azure.com` domain, such as `https://<resourcename>.openai.azure.com`. [Azure API Management](/azure/api-management/api-management-key-concepts) endpoints are supported with URL `https://<resourcename>.azure-api.net`. Shared private links aren't supported for API Management endpoints. |
 | `apiKey`   |  The secret key used to access the model. If you provide a key, leave `authIdentity` empty. If you set both the `apiKey` and `authIdentity`, the `apiKey` is used on the connection. |
 | `deploymentId`   | The name of the deployed Azure OpenAI embedding model. The model should be an embedding model, such as text-embedding-ada-002. See the [List of Azure OpenAI models](/azure/ai-services/openai/concepts/models) for supported models.|
 | `authIdentity`   | A user-managed identity used by the search service for connecting to Azure OpenAI. You can use either a [system or user managed identity](search-how-to-managed-identities.md). To use a system managed identity, leave `apiKey` and `authIdentity` blank. The system-managed identity is used automatically. A managed identity must have [Cognitive Services OpenAI User](/azure/ai-services/openai/how-to/role-based-access-control#azure-openai-roles) permissions to send text to Azure OpenAI. |