Merge pull request #7324 from MicrosoftDocs/main

Auto Publish – main to live - 2025-09-27 05:07 UTC

Author: learn-build-service-prod[bot]

articles/ai-foundry/how-to/model-deployment-policy.md

@@ -1,6 +1,6 @@
 ---
-title: Manage AI model deployment in Azure AI Foundry (Preview)
-description: Control AI model deployment in Azure AI Foundry Portal with built-in Azure Policy definitions. Learn how to govern and manage model deployments effectively.
+title: Built-in policy for model deployment (Preview)
+description: Manage AI model deployment in Azure AI Foundry Portal with built-in Azure Policy definitions. Learn how to govern and manage model deployments effectively.
 #customer intent: As an IT admin, I want to control the deployment of AI models in Azure AI Foundry Portal so that I can ensure compliance with organizational policies.
 author: jonburchel
 ms.author: jburchel
@@ -11,7 +11,7 @@ ms.service: azure-ai-foundry
 ai-usage: ai-assisted
 ---
 
-# Control AI model deployment with built-in policy in Azure AI Foundry portal (Preview)
+# Built-in policy for model deployment in Azure AI Foundry portal (Preview)
 
 Azure Policy provides built-in policy definitions that help you govern the deployment of AI models in Azure AI Foundry Portal. You can use
 these policies to control what models your developers can deploy in Azure AI Foundry portal.

articles/ai-foundry/toc-files/security-governance/toc.yml

@@ -22,7 +22,7 @@ items:
     href: ../../how-to/disable-local-auth.md
 - name: Azure policies
   items:
-  - name: Manage model deployment policy (Preview)
+  - name: Built-in policy for model deployment (Preview)
     href: ../../how-to/model-deployment-policy.md
   - name: Built-in policy definitions
     displayName: samples, policies, definitions, Azure Policy

articles/ai-services/language-service/entity-linking/how-to/call-api.md

@@ -6,14 +6,18 @@ author: laujan
 manager: nitinme
 ms.service: azure-ai-language
 ms.topic: how-to
-ms.date: 06/21/2025
+ms.date: 09/26/2025
 ms.author: lajanuar
 ms.custom: language-service-entity-linking
 ---
 
 # How to use entity linking
 
-The entity linking feature can be used to identify and disambiguate the identity of an entity found in text (for example, determining whether an occurrence of the word "*Mars*" refers to the planet, or to the Roman god of war). It will return the entities in the text with links to [Wikipedia](https://www.wikipedia.org/) as a knowledge base.
+> [!IMPORTANT]
+> Entity Linking is retiring from Azure AI Language effective **September 1, 2028**. After this date, the Entity Linking feature is no longer supported.   During the support window, we recommend that users migrate existing workloads and direct all new projects to Azure AI Language [**Named Entity Recognition**](../../named-entity-recognition/overview.md) or consider other alternative solutions.
+
+
+The entity linking feature enables the detection and clarification of the specific identity of entities mentioned within text. For instance, it can determine whether the term "Mars" refers to the planet or to the Roman god of war. This capability helps eliminate ambiguity by associating each entity with the correct context. It returns the entities in the text with links to [Wikipedia](https://www.wikipedia.org/) as a knowledge base.
 
 
 ## Development options
@@ -24,20 +28,20 @@ The entity linking feature can be used to identify and disambiguate the identity
 
 ### Specify the entity linking model
 
-By default, entity linking will use the latest available AI model on your text. You can also configure your API requests to use a specific [model version](../../concepts/model-lifecycle.md).
+By default, entity linking uses the latest available AI model on your text. You can also configure your API requests to use a specific [model version](../../concepts/model-lifecycle.md).
 
 ### Input languages
 
-When you submit documents to be processed by entity linking, you can specify which of [the supported languages](../language-support.md) they're written in. if you don't specify a language, entity linking will default to English. Due to [multilingual and emoji support](../../concepts/multilingual-emoji-support.md), the response may contain text offsets. 
+When you submit documents to for entity linking processing, you can specify which of [the supported languages](../language-support.md) they're written in. If you don't specify a language, entity linking defaults to English. Due to [multilingual and emoji support](../../concepts/multilingual-emoji-support.md), the response may contain text offsets. 
 
 ## Submitting data
 
-Entity linking produces a higher-quality result when you give it smaller amounts of text to work on. This is opposite from some features, like key phrase extraction which performs better on larger blocks of text. To get the best results from both operations, consider restructuring the inputs accordingly.
+Entity linking produces a higher-quality result when you give it smaller amounts of text to work on. This characteristic is opposite from some features, like key phrase extraction that performs better on larger blocks of text. To get the best results from both operations, consider restructuring the inputs accordingly.
 
-To send an API request, you will need a Language resource endpoint and key.
+To send an API request, you need a Language resource endpoint and API key.
 
 > [!NOTE]
-> You can find the key and endpoint for your Language resource on the Azure portal. They will be located on the resource's **Key and endpoint** page, under **resource management**. 
+> You can find the key and endpoint for your Language resource on the Azure portal. They're located on the resource's **Key and endpoint** page, under **resource management**. 
 
 Analysis is performed upon receipt of the request. Using entity linking synchronously is stateless. No data is stored in your account, and results are returned immediately in the response.
 

articles/ai-services/language-service/entity-linking/language-support.md

@@ -13,6 +13,10 @@ ms.custom: language-service-entity-linking
 
 # Entity linking language support 
 
+> [!IMPORTANT]
+> Entity Linking is retiring from Azure AI Language effective **September 1, 2028**. After this date, the Entity Linking feature is no longer supported.   During the support window, we recommend that users migrate existing workloads and direct all new projects to Azure AI Language [**Named Entity Recognition**](../named-entity-recognition/overview.md) or consider other alternative solutions.
+
+
 | Language | Language code | Notes |
 |:---------|:-------------:|:-----:|
 | English  |     `en`      |      |

articles/ai-services/language-service/entity-linking/overview.md

@@ -13,6 +13,10 @@ ms.custom: language-service-entity-linking
 
 # What is entity linking in Azure AI Language?
 
+> [!IMPORTANT]
+> Entity Linking is retiring from Azure AI Language effective **September 1, 2028**. After this date, the Entity Linking feature is no longer supported.   During the support window, we recommend that users migrate existing workloads and direct all new projects to Azure AI Language [**Named Entity Recognition**](../named-entity-recognition/overview.md) or consider other alternative solutions.
+
+
 Entity linking is one of the features offered by [Azure AI Language](../overview.md), a collection of machine learning and AI algorithms in the cloud for developing intelligent applications that involve written language. Entity linking identifies and disambiguates the identity of entities found in text. For example, in the sentence "*We went to Seattle last week.*", the word "*Seattle*" would be identified, with a link to more information on Wikipedia.
 
 This documentation contains the following types of articles:

articles/ai-services/language-service/entity-linking/quickstart.md

@@ -6,7 +6,7 @@ author: laujan
 manager: nitinme
 ms.service: azure-ai-language
 ms.topic: quickstart
-ms.date: 06/21/2025
+ms.date: 09/26/2025
 ms.author: lajanuar
 ms.devlang: csharp
 # ms.devlang: csharp, java, javascript, python
@@ -17,6 +17,10 @@ zone_pivot_groups: programming-languages-entity-linking
 
 # Quickstart: Entity Linking using the client library and REST API
 
+> [!IMPORTANT]
+> Entity Linking is retiring from Azure AI Language effective **September 1, 2028**. After this date, the Entity Linking feature is no longer supported.   During the support window, we recommend that users migrate existing workloads and direct all new projects to Azure AI Language [**Named Entity Recognition**](../named-entity-recognition/overview.md) or consider other alternative solutions.
+
+
 ::: zone pivot="programming-language-csharp"
 
 [!INCLUDE [C# quickstart](includes/quickstarts/csharp-sdk.md)]

articles/ai-services/language-service/overview.md

@@ -6,7 +6,7 @@ author: laujan
 manager: nitinme
 ms.service: azure-ai-language
 ms.topic: overview
-ms.date: 07/17/2025
+ms.date: 09/26/2025
 ms.author: lajanuar
 ---
 
@@ -48,7 +48,7 @@ The Language service also provides several new features as well, which can eithe
       :::image type="content" source="media/overview/text-pii.png" alt-text="A screenshot of text personally identifying information in Azure AI Foundry." lightbox="media/overview/text-pii.png":::
    :::column-end:::
    :::column span="":::
-      [PII detection](./personally-identifiable-information/overview.md) identifies entities in text and conversations (chat or transcripts) that are associated with individuals.
+      [Personally Identifiable Information (PII) detection](./personally-identifiable-information/overview.md) identifies entities in text and conversations (chat or transcripts) that are associated with individuals.
 
    :::column-end:::
 :::row-end:::
@@ -105,6 +105,10 @@ Conversation summarization recaps and segments long meetings into timestamped ch
 
 ### Entity linking
 
+> [!IMPORTANT]
+> Entity Linking is retiring from Azure AI Language effective **September 1, 2028**. After this date, the Entity Linking feature is no longer supported.   During the support window, we recommend that users migrate existing workloads and direct all new projects to Azure AI Language [**Named Entity Recognition**](named-entity-recognition/overview.md) or consider other alternative solutions.
+
+
 :::row:::
    :::column span="":::
       :::image type="content" source="media/studio-examples/entity-linking.png" alt-text="A screenshot of an entity linking example." lightbox="media/studio-examples/entity-linking.png":::

articles/ai-services/speech-service/includes/quickstarts/voice-live-agents/intro.md

@@ -16,4 +16,4 @@ You can create and run an application to use voice live with agents for real-tim
 
 - This separation also supports better maintainability and scalability for scenarios where multiple conversational experiences or business logic variations are needed.
 
-To instead use the voice live API without agents, see the [voice live quickstart](/azure/ai-services/speech-service/voice-live-quickstart).
+To instead use the Voice live API without agents, see the [Voice live API quickstart](/azure/ai-services/speech-service/voice-live-quickstart).

articles/ai-services/speech-service/includes/quickstarts/voice-live-api/intro.md

@@ -1,9 +1,9 @@
 ---
-author: PatrickFarley
+author: goergenj
 ms.service: azure-ai-speech
 ms.topic: include
-ms.date: 7/31/2025
-ms.author: pafarley
+ms.date: 9/26/2025
+ms.author: jagoerge
 ---
 
 You create and run an application to use voice live directly with generative AI models for real-time voice agents.
@@ -16,4 +16,4 @@ You create and run an application to use voice live directly with generative AI
 
 - Direct model use is suitable for scenarios where agent-level abstraction or built-in logic is unnecessary.
 
-To instead use the voice live API with agents, see the [voice live agents quickstart](/azure/ai-services/speech-service/voice-live-agents-quickstart).
+To instead use the Voice live API with agents, see the [Voice live API agents quickstart](/azure/ai-services/speech-service/voice-live-agents-quickstart).

articles/ai-services/speech-service/regions.md

@@ -6,7 +6,7 @@ author: goergenj
 manager: nitinme
 ms.service: azure-ai-speech
 ms.topic: conceptual
-ms.date: 9/16/2025
+ms.date: 9/26/2025
 ms.author: jagoerge
 ms.custom: references_regions
 #Customer intent: As a developer, I want to learn about the available regions and endpoints for the Speech service.
@@ -187,9 +187,9 @@ The regions in these tables support most of the core features of the Speech serv
 |uksouth| - | - | Global standard | Global standard | Global standard | Global standard | - | - | - | - | - | - |
 |westeurope| - | - | Data zone standard | Data zone standard | Data zone standard | Data zone standard | - | - | - | - | - | - |
 
-<sup>1</sup> The Azure AI Foundry resource must be in Central India. Azure AI Speech features remain in Central India. The voice live API uses Sweden Central as needed for generative AI load balancing.
+<sup>1</sup> The Azure AI Foundry resource must be in Central India. Azure AI Speech features remain in Central India. The Voice live API uses Sweden Central as needed for generative AI load balancing.
 
-<sup>2</sup> The Azure AI Foundry resource must be in West US 2. Azure AI Speech features remain in West US 2. The voice live API uses East US 2 as needed for generative AI load balancing.
+<sup>2</sup> The Azure AI Foundry resource must be in West US 2. Azure AI Speech features remain in West US 2. The Voice live API uses East US 2 as needed for generative AI load balancing.
 
 # [Intent recognition](#tab/intent-recognition)