View Diff on GitHub
# ハイライト
このコードの差分には、主にAzure Languageサービスのドキュメント更新が含まれています。新機能としては、複数の画像ファイルの追加があり、特に「会話型言語理解」と「エンティティリンク」などの説明をサポートするものです。さらに、多くの文書において、機能の廃止予定やMicrosoft Foundryモデルへの移行が告知されており、ユーザーに大きな変更を知らせています。
新機能
- 「会話型言語理解」「エンティティリンク」などに関する新しい説明用画像ファイルの追加。
- バージョン管理や品質向上を目的とした画像ファイルの更新。
重要な変更
- 多くのAzure Languageサービス機能の廃止予定日が設定され、ユーザーに対しMicrosoft Foundryモデルへの移行が推奨されています。
- 一部のセクションタイトルや内容が調整され、ドキュメントの整合性と可読性が改善されました。
その他の更新
- 更新日と共にドキュメントが新しい情報を反映するよう修正されました。
- 各機能に合わせた詳細セクションのアップデート、構成の再検討が行われています。
インサイト
この更新の根底にある動機は、Azure Languageサービスのエコシステムを最新かつ一貫したものに保つことにあります。多くの機能に対して具体的な廃止予定日が設定され、ユーザーはMicrosoft Foundryモデルへのスムーズな移行が求められています。
これにより、Azureは最新の自然言語処理技術に対応した強化されたサービスを提供し続けることに注力していることがわかります。また、新たに追加された複数の画像ファイルは、サービス利用者の理解を促進するためのビジュアルサポートを提供し、これまでテキストベースの説明のみだった部分が、より直感的なものへと進化している様子が伺えます。
ドキュメントの再構築と内容の精査により、ユーザーにとって最も関連性の高い情報が、洗練されたコンテンツとして分かりやすく提供されるよう努められています。これに伴い、利用者が必要となる情報を素早く見つけ、正しい意思決定を行い、サービスを最適に活用するための援助がしっかりと意識されています。
結果として、これらの変更はAzure Languageサービスの成長とユーザーエクスペリエンスの向上に寄与し、長期的な視点でのユーザー満足度の向上を目指すものです。
Summary Table
Modified Contents
articles/ai-services/language-service/concepts/regional-support.md
Diff
@@ -6,13 +6,14 @@ author: laujan
manager: nitinme
ms.service: azure-ai-language
ms.topic: concept-article
-ms.date: 03/06/2026
+ms.date: 03/27/2026
ms.author: lajanuar
ms.custom: references_regions
---
-# Language supported regions
+<!-- markdownlint-disable MD025 -->
+# Azure Language region support
-The Language is available for use in several Azure regions. Use this article to learn about the regional support and limitations.
+The Azure Language features are available for use in several Azure regions. Use this article to learn about the regional support and limitations.
## Region support overview
@@ -161,6 +162,8 @@ Custom text classification is only available in some Azure regions. Some regions
## Summarization
+[!INCLUDE [availability](../summarization/includes/regional-availability.md)]
+
|Region |Text abstractive summarization|Conversation summarization |
|----------------------|------------------------------|-----------------------------------------|
|AustraliaEast|✓|✓|
Summary
{
"modification_type": "minor update",
"modification_title": "言語サービスの地域サポートに関する更新"
}
Explanation
この変更では、Azure Language Serviceに関する文書の更新が行われています。主な変更点は、文書のタイトルが「Language supported regions」から「Azure Language region support」に変更されたこと、発行日が2026年3月6日から2026年3月27日に更新されたことです。また、文の一部が修正され、サービス内容の説明がより明確になっています。さらに、テキスト要約に関連する地域のサポート情報を示すテーブルが追加され、特定の地域でのカスタムテキスト分類の可用性についても触れられています。全体として、この更新は内容の明確化と最新の情報を反映させることを目的としています。
articles/ai-services/language-service/conversational-language-understanding/overview.md
Diff
@@ -6,15 +6,19 @@ author: laujan
manager: nitinme
ms.service: azure-ai-language
ms.topic: overview
-ms.date: 12/05/2025
+ms.date: 03/30/2026
ms.author: lajanuar
ms.custom: language-service-clu
---
+<!-- markdownlint-disable MD025 -->
# What is conversational language understanding?
-Conversational language understanding is one of the custom features offered by [Azure Language](../overview.md). It's a cloud-based API service that applies machine-learning intelligence to enable you to build natural language understanding component to be used in an end-to-end conversational application.
+> [!IMPORTANT]
+> Conversational Language Understanding (CLU) is retiring from Azure Language effective **March 31, 2029**. After this date, the CLU feature is no longer supported. During the support window, we recommend that users migrate existing workloads and direct all new projects to [Microsoft Foundry models](../../../foundry/concepts/foundry-models-overview.md), which offer enhanced capabilities for natural language understanding and can be easily integrated into your applications.
-Conversational language understanding (CLU) enables users to build custom natural language understanding models to predict the overall intention of an incoming utterance and extract important information from it. CLU only provides the intelligence to understand the input text for the client application and doesn't perform any actions. Developers can iteratively label utterances, train, and evaluate model performance before making it available for consumption by creating a CLU project. The quality of the labeled data greatly impacts model performance. To simplify building and customizing your model, the service offers a custom web portal that can be accessed through the [Microsoft Foundry](https://ai.azure.com/). You can easily get started with the service by following the steps in this [quickstart](quickstart.md).
+Conversational language understanding is one of the custom features offered by [Azure Language](../overview.md). It's a cloud-based API service that applies machine-learning intelligence to enable you to build natural language understanding component to be used in an end-to-end conversational application.
+
+Conversational language understanding (CLU) enables users to build custom natural language understanding models to predict the overall intention of an incoming utterance and extract important information from it. CLU only provides the intelligence to understand the input text for the client application and doesn't perform any actions. Developers can iteratively label utterances, train, and evaluate model performance before making it available for consumption by creating a CLU project. The quality of the labeled data greatly impacts model performance. To simplify building and customizing your model, the service offers a custom web portal that can be accessed through the [Microsoft Foundry](https://ai.azure.com/). You can easily get started with the service by following the steps in this [quickstart](quickstart.md).
This documentation contains the following article types:
@@ -27,7 +31,7 @@ This documentation contains the following article types:
CLU can be used in multiple scenarios across various industries. Some examples are:
-### Multi-turn conversations
+### Multi-turn conversations
Use CLU with entity slot filling to enable natural, progressive information gathering across multiple conversation turns. Instead of overwhelming users with complex forms, your application can collect required details as they emerge naturally in dialogue. This approach is ideal for scenarios like booking systems, customer service workflows, or any application where complete information needs to be gathered through conversational exchanges.
@@ -70,15 +74,15 @@ Option 1 (LLM-powered quick deploy):
2. **Deploy the model**: Deploying a model with the LLM-based training config makes it available for use via the Runtime API.
-3. **Predict intents and entities**: Use your custom model deployment to predict custom intents and prebuilt entities from user's utterances.
+3. **Predict intents and entities**: Use your custom model deployment to predict custom intents and prebuilt entities from user's utterances.
Option 2 (Custom machine learned model)
Follow these steps to get the most out of your trained model:
1. **Define your schema**: Know your data and define the actions and relevant information that needs to be recognized from user's input utterances. In this step, you create the [intents](glossary.md#intent) that you want to assign to user's utterances, and the relevant [entities](glossary.md#entity) you want extracted.
-2. **Label your data**: The quality of data labeling is a key factor in determining model performance.
+2. **Label your data**: The quality of data labeling is a key factor in determining model performance.
3. **Train the model**: Your model starts learning from your labeled data.
@@ -101,16 +105,16 @@ As you use CLU, see the following reference documentation and samples for Azure
|C# (Runtime) | [C# documentation](/dotnet/api/overview/azure/ai.language.conversations-readme) | [C# samples](https://github.com/Azure/azure-sdk-for-net/tree/main/sdk/cognitivelanguage/Azure.AI.Language.Conversations/samples) |
|Python (Runtime)| [Python documentation](/python/api/overview/azure/ai-language-conversations-readme?view=azure-python-preview&preserve-view=true) | [Python samples](https://github.com/Azure/azure-sdk-for-python/tree/main/sdk/cognitivelanguage/azure-ai-language-conversations/samples) |
-## Responsible AI
+## Responsible AI
-An AI system includes the technology, the individuals who operate the system, the people who experience its effects, and the broader environment where the system functions all play a role. Read the transparency note for CLU to learn about responsible AI use and deployment in your systems.
+An AI system includes the technology, the individuals who operate the system, the people who experience its effects, and the broader environment where the system functions all play a role. Read the transparency note for CLU to learn about responsible AI use and deployment in your systems.
[!INCLUDE [Responsible AI links](../includes/overview-responsible-ai-links.md)]
## Next steps
-* Use the [quickstart article](quickstart.md) to start using conversational language understanding.
+* Use the [quickstart article](quickstart.md) to start using conversational language understanding.
-* As you go through the project development lifecycle, review the [glossary](glossary.md) to learn more about the terms used throughout the documentation for this feature.
+* As you go through the project development lifecycle, review the [glossary](glossary.md) to learn more about the terms used throughout the documentation for this feature.
* Remember to view the [service limits](service-limits.md) for information such as [regional availability](service-limits.md#regional-availability).
Summary
{
"modification_type": "minor update",
"modification_title": "会話型言語理解の概要に関する更新"
}
Explanation
この変更では、「会話型言語理解」に関する文書の重要な更新が行われています。主な変更点は、Azure Languageの機能である会話型言語理解(CLU)の廃止が2029年3月31日と明記されたことです。この変更に伴い、ユーザーには既存のワークロードをMicrosoft Foundryモデルに移行することが推奨されています。また、文書内の一部の説明が明確になり、構文が整理されています。特に、「CLUは、顧客の意思を予測し、重要な情報を抽出するためのカスタム自然言語理解モデルを構築するために使用される」との説明が強調されています。加えて、ドキュメント全体の規約や次のステップも整理されており、ユーザーが迅速にサービスを利用できるように配慮されています。この更新は、内容の明瞭化とユーザーへの重要な情報の強調を目的としています。
articles/ai-services/language-service/custom-named-entity-recognition/overview.md
Diff
@@ -1,18 +1,19 @@
---
-title: Custom named entity recognition - Foundry Tools
+title: What is the custom named entity recognition (CNER) feature in Azure Language?
titleSuffix: Foundry Tools
description: Customize an AI model to label and extract information from documents using Azure Language.
author: laujan
manager: nitinme
ms.service: azure-ai-language
ms.topic: overview
-ms.date: 11/18/2025
+ms.date: 03/30/2026
ms.author: lajanuar
ms.custom: language-service-custom-ner
---
-# What is custom named entity recognition?
+<!-- markdownlint-disable MD025 -->
+# What is custom named entity recognition in Azure Language?
-Custom named entity recognition (NER) is a cloud-based API service that uses machine learning to help you build models designed for your unique entity recognition requirements. It's one of the specialized features available through [Azure Language in Foundry Tools](../overview.md). With custom NER, you can create AI models that extract domain-specific entities from unstructured text, such as contracts or financial documents. When you start a Custom NER project, you can repeatedly label data, train and evaluate your model, and improve its performance before deploying it. The quality of your labeled data is essential, as it directly impacts the model's accuracy.
+Custom named entity recognition (CNER) is an Azure Language [core capability](../overview.md#core-capabilities). The CNER feature is a cloud-based API service that uses machine learning to help you build models designed for your unique entity recognition requirements. You can create AI models that extract domain-specific entities from unstructured text, such as contracts or financial documents. When you start a custom CNER project, you can repeatedly label data, train and evaluate your model, and improve its performance before deploying it. The quality of your labeled data is essential, as it directly impacts the model's accuracy.
To simplify building and customizing your model, the service offers a custom web platform that can be accessed through the [Microsoft Foundry](https://ai.azure.com/). You can easily get started with the service by following the steps in this [quickstart](quickstart.md).
Summary
{
"modification_type": "minor update",
"modification_title": "カスタム命名エンティティ認識機能の概要更新"
}
Explanation
この変更では、Azure Languageの「カスタム命名エンティティ認識(CNER)」機能に関する文書が更新されています。主な変更点は、タイトルが「Custom named entity recognition - Foundry Tools」から「What is the custom named entity recognition (CNER) feature in Azure Language?」に変更されたことです。また、発行日が2025年11月18日から2026年3月30日に更新されています。さらに、CNERについての記述が強調され、特にこの機能がAzure Languageの「コア機能」であることが明記されています。
文書中の説明も一部改訂され、CNERが提供するサービスの特長を強調しています。具体的には、専門的なエンティティを抽出するためのモデルを構築するためのプロセスや、ラベル付けされたデータの質がモデルの精度に与える影響についても触れられています。全体として、この更新は内容の明確化とCNER機能の重要性を強調することを目的としています。
articles/ai-services/language-service/custom-text-classification/overview.md
Diff
@@ -7,17 +7,21 @@ author: laujan
manager: nitinme
ms.service: azure-ai-language
ms.topic: overview
-ms.date: 12/15/2025
+ms.date: 03/30/2026
ms.author: lajanuar
ms.custom: language-service-custom-classification
---
+<!-- markdownlint-disable MD025 -->
# What is custom text classification?
-Custom text classification is one of the custom features offered by [Azure Language in Foundry Tools](../overview.md). It's a cloud-based API service that applies machine-learning intelligence to enable you to build custom models for text classification tasks.
+> [!IMPORTANT]
+> Custom text classification is retiring from Azure Language effective **March 31, 2029**. After this date, the feature is no longer supported. During the support window, we recommend that users migrate existing workloads and direct all new projects to [Microsoft Foundry models](../../../foundry/concepts/foundry-models-overview.md), which offer enhanced capabilities for natural language understanding and can be easily integrated into your applications.
-Custom text classification enables users to build custom AI models to classify text into custom classes predefined by the user. By creating a custom text classification project, developers can iteratively label data, train, evaluate, and improve model performance before making it available for consumption. The quality of the labeled data greatly impacts model performance. To simplify building and customizing your model, the service offers a unified platform for building, managing, and deploying AI solutions that can be accessed through the [Microsoft Foundry](https://ai.azure.com/). You can easily get started with the service by following the steps in this [quickstart](quickstart.md).
+Custom text classification is one of the custom features offered by [Azure Language in Foundry Tools](../overview.md). It's a cloud-based API service that applies machine-learning intelligence to enable you to build custom models for text classification tasks.
-Custom text classification supports two types of projects:
+Custom text classification enables users to build custom AI models to classify text into custom classes predefined by the user. By creating a custom text classification project, developers can iteratively label data, train, evaluate, and improve model performance before making it available for consumption. The quality of the labeled data greatly impacts model performance. To simplify building and customizing your model, the service offers a unified platform for building, managing, and deploying AI solutions that can be accessed through the [Microsoft Foundry](https://ai.azure.com/). You can easily get started with the service by following the steps in this [quickstart](quickstart.md).
+
+Custom text classification supports two types of projects:
* **Single label classification** - you can assign a single class for each document in your dataset. For example, a movie script could only be classified as "Romance" or "Comedy."
* **Multi label classification** - you can assign multiple classes for each document in your dataset. For example, a movie script could be classified as "Comedy" or "Romance" and "Comedy."
@@ -42,7 +46,7 @@ Search is foundational to any app that surfaces text content to users. Common sc
## Project development lifecycle
-Creating a custom text classification project typically involves several different steps.
+Creating a custom text classification project typically involves several different steps.
:::image type="content" source="media/development-lifecycle.png" alt-text="The development lifecycle" lightbox="media/development-lifecycle.png":::
@@ -73,16 +77,16 @@ As you use custom text classification, see the following reference documentation
| JavaScript (Runtime) | [JavaScript documentation](/javascript/api/overview/azure/ai-text-analytics-readme?view=azure-node-preview&preserve-view=true) | [JavaScript samples - Single label classification](https://github.com/Azure/azure-sdk-for-js/blob/%40azure/ai-text-analytics_6.0.0-beta.1/sdk/textanalytics/ai-text-analytics/samples/v5/javascript/customText.js) [JavaScript samples - Multi label classification](https://github.com/Azure/azure-sdk-for-js/blob/%40azure/ai-text-analytics_6.0.0-beta.1/sdk/textanalytics/ai-text-analytics/samples/v5/javascript/customText.js) |
| Python (Runtime) | [Python documentation](/python/api/azure-ai-textanalytics/azure.ai.textanalytics?view=azure-python-preview&preserve-view=true) | [Python samples - Single label classification](https://github.com/Azure/azure-sdk-for-python/blob/main/sdk/textanalytics/azure-ai-textanalytics/samples/sample_single_label_classify.py) [Python samples - Multi label classification](https://github.com/Azure/azure-sdk-for-python/blob/main/sdk/textanalytics/azure-ai-textanalytics/samples/sample_multi_label_classify.py) |
-## Responsible AI
+## Responsible AI
-An AI system includes not only the technology, but also the people who use it, the people affected by it, and the deployment environment. Read the [transparency note for custom text classification](/azure/ai-foundry/responsible-ai/language-service/custom-text-classification-transparency-note) to learn about responsible AI use and deployment in your systems.
+An AI system includes not only the technology, but also the people who use it, the people affected by it, and the deployment environment. Read the [transparency note for custom text classification](/azure/ai-foundry/responsible-ai/language-service/custom-text-classification-transparency-note) to learn about responsible AI use and deployment in your systems.
[!INCLUDE [Responsible AI links](../includes/overview-responsible-ai-links.md)]
## Next steps
-* Use the [quickstart article](quickstart.md) to start using custom text classification.
+* Use the [quickstart article](quickstart.md) to start using custom text classification.
-* As you go through the project development lifecycle, review the [glossary](glossary.md) to learn more about the terms used throughout the documentation for this feature.
+* As you go through the project development lifecycle, review the [glossary](glossary.md) to learn more about the terms used throughout the documentation for this feature.
* Remember to view the [service limits](service-limits.md) for information such as regional availability.
Summary
{
"modification_type": "minor update",
"modification_title": "カスタムテキスト分類機能の概要更新"
}
Explanation
この変更では、Azure Languageの「カスタムテキスト分類」機能に関する文書が更新されています。主な更新内容には、発行日の変更(2025年12月15日から2026年3月30日へ)や、重要な情報としてカスタムテキスト分類が2029年3月31日をもって廃止される旨が追加されたことが含まれています。この情報は、ユーザーが既存のワークロードをMicrosoft Foundryモデルに移行することが推奨されていることを強調しています。
さらに、カスタムテキスト分類の定義が明確化され、ユーザーがどのようにして文書を分類するモデルを構築できるかについての詳細が提供されています。新たに「シングルラベル分類」と「マルチラベル分類」の2種類のプロジェクトサポートが明記され、具体的な例も示されています。文書の整頓に伴い、全体的な流れがスムーズになっており、ユーザーがサービスを効果的に利用できるようになることを目指しています。
articles/ai-services/language-service/entity-linking/overview.md
Diff
@@ -6,14 +6,14 @@ author: laujan
manager: nitinme
ms.service: azure-ai-language
ms.topic: overview
-ms.date: 11/18/2025
+ms.date: 03/30/2026
ms.author: lajanuar
ms.custom: language-service-entity-linking
---
# What is entity linking in Azure Language in Foundry Tools?
> [!IMPORTANT]
-> Entity Linking is retiring from Azure Language in Foundry Tools 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 Language [**Named Entity Recognition**](../named-entity-recognition/overview.md) or consider other alternative solutions.
+> Entity Linking is retiring from Azure Language in Foundry Tools 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 Language [**Named Entity Recognition**](../named-entity-recognition/overview.md) or [Foundry models](../../../foundry/concepts/foundry-models-overview.md), which offer enhanced capabilities for natural language understanding and can be easily integrated into your applications.
Entity linking is one of the features offered by [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.
Summary
{
"modification_type": "minor update",
"modification_title": "エンティティリンク機能の概要更新"
}
Explanation
この変更では、Azure Languageの「エンティティリンク」機能に関する文書が更新されています。主な変更点として、発行日が2025年11月18日から2026年3月30日に変更されました。また、エンティティリンク機能が2028年9月1日をもって廃止されるという重要な情報が追加されており、廃止後はこの機能がサポートされないことが明記されています。
さらに、ユーザーに対して既存のワークロードを「ネーミングエンティティ認識」や「Foundryモデル」へ移行することが推奨されており、これらのモデルが自然言語理解において強化された機能を提供し、アプリケーションに統合しやすいことが強調されています。全体として、この更新はユーザーへ新しい方向性を示すことを目的としています。
articles/ai-services/language-service/key-phrase-extraction/overview.md
Diff
@@ -6,12 +6,16 @@ author: laujan
manager: nitinme
ms.service: azure-ai-language
ms.topic: overview
-ms.date: 11/18/2025
+ms.date: 03/30/2026
ms.author: lajanuar
ms.custom: language-service-key-phrase
---
+<!-- markdownlint-disable MD025 -->
# What is key phrase extraction in Azure Language in Foundry Tools?
+> [!IMPORTANT]
+> Key phrase extraction is retiring from Azure Language effective **March 31, 2029**. After this date, the feature is no longer supported. During the support window, we recommend that users migrate existing workloads and direct all new projects to [Microsoft Foundry models](../../../foundry/concepts/foundry-models-overview.md), which offer enhanced capabilities for natural language understanding and can be easily integrated into your applications.
+
Key phrase extraction is one of the features offered by [Azure Language in Foundry Tools](../overview.md). This capability is part of a suite of cloud-based machine learning and AI tools designed for building intelligent applications that process written language. Use key phrase extraction to quickly identify the main concepts in text. For example, in the text "*The food was delicious and the staff were wonderful.*", key phrase extraction returns the main topics: "*food*" and "*wonderful staff*."
This documentation contains the following types of articles:
@@ -37,5 +41,5 @@ An AI system includes the technology, the individuals who operate the system, th
## Next steps
There are two ways to get started using the entity linking feature:
-* [Microsoft Foundry](../../../ai-foundry/what-is-foundry.md) is a web-based platform that lets you use several Language features without needing to write code.
+* [Microsoft Foundry](../../../foundry/what-is-foundry.md) is a web-based platform that lets you use several Language features without needing to write code.
* The [quickstart article](quickstart.md) for instructions on making requests to the service using the REST API and client library SDK.
Summary
{
"modification_type": "minor update",
"modification_title": "キーフレーズ抽出機能の概要更新"
}
Explanation
この変更では、Azure Languageの「キーフレーズ抽出」機能に関する文書が更新されています。主な変更点には、発行日が2025年11月18日から2026年3月30日に変更されたことが含まれています。また、重要な情報としてキーフレーズ抽出機能が2029年3月31日をもって廃止されることが明記され、廃止後はこの機能がサポートされないことが強調されています。ユーザーには、既存のワークロードをMicrosoft Foundryモデルに移行し、新しいプロジェクトをそちらに向けることが推奨されています。
さらに、キーフレーズ抽出の定義が整理され、テキスト内の主な概念を迅速に特定するための能力が説明されています。具体例として、「食べ物」や「素晴らしいスタッフ」といった主要なトピックが挙げられています。全体として、この更新はユーザーが将来の代替手段を考慮するための指針となることを目的としています。
articles/ai-services/language-service/language-detection/overview.md
Diff
@@ -1,18 +1,19 @@
---
-title: What is language detection in Azure Language in Foundry Tools?
+title: What is language detection in Azure Language?
titleSuffix: Foundry Tools
description: An overview of language detection in Azure Language, which helps you detect the language that text is written in by returning language codes.
author: laujan
manager: nitinme
ms.service: azure-ai-language
ms.topic: overview
-ms.date: 11/18/2025
+ms.date: 03/30/2026
ms.author: lajanuar
ms.custom: language-service-language-detection
---
-# What is language detection in Azure Language in Foundry Tools?
+<!-- markdownlint-disable MD025 -->
+# What is language detection in Azure Language?
-Language detection is one of the features offered by [Azure Language in Foundry Tools](../overview.md), a collection of machine learning and AI algorithms in the cloud for developing intelligent applications that involve written language. Language detection is able to detect more than 100 languages in their primary script. In addition, the service offers [script detection](./how-to/call-api.md#script-name-and-script-code) for each detected language using [ISO 15924 standard](https://wikipedia.org/wiki/ISO_15924) for a [select number of languages](./language-support.md#script-detection).
+Language detection is an Azure Language prebuilt [core capability](../overview.md#core-capabilities). Language detection can identify more than 100 languages in their primary script. In addition, the service offers [script detection](./how-to/call-api.md#script-name-and-script-code) for each detected language using [ISO 15924 standard](https://wikipedia.org/wiki/ISO_15924) for a [select number of languages](./language-support.md#script-detection).
This documentation contains the following types of articles:
* [**Quickstarts**](quickstart.md) are getting-started instructions to guide you through making requests to the service.
@@ -22,25 +23,25 @@ This documentation contains the following types of articles:
* Language detection: For each document, returns the main language, its ISO 639-1 code, readable name, confidence score, script name, and ISO 15924 script code.
-* Script detection: To distinguish between multiple scripts used to write certain languages, such as Kazakh, language detection returns a script name and script code according to the ISO 15924 standard.
+* Script detection: To distinguish between multiple scripts used to write certain languages, such as Kazakh, language detection returns a script name and script code according to the ISO 15924 standard.
* Ambiguous content handling: To help disambiguate language based on the input, you can specify an ISO 3166-1 alpha-2 country/region code. For example, the word "communication" is common to both English and French. Specifying the origin of the text as France can help the language detection model determine the correct language.
[!INCLUDE [Typical workflow for pre-configured language features](../includes/overview-typical-workflow.md)]
-
## Get started with language detection
[!INCLUDE [development options](./includes/development-options.md)]
-## Responsible AI
+## Responsible AI
-An AI system includes not only the technology, but also individuals who operate the system, people who experience its effects, and the broader environment where the system functions. Read the [transparency note for language detection](/azure/ai-foundry/responsible-ai/language-service/transparency-note-language-detection) to learn about responsible AI use and deployment in your systems.
+An AI system includes not only the technology, but also individuals who operate the system, people who experience its effects, and the broader environment where the system functions. Read the [transparency note for language detection](/azure/ai-foundry/responsible-ai/language-service/transparency-note-language-detection) to learn about responsible AI use and deployment in your systems.
[!INCLUDE [Responsible AI links](../includes/overview-responsible-ai-links.md)]
## Next steps
-There are two ways to get started using the entity linking feature:
+There are two ways to get started using the language detection feature:
+
* [Microsoft Foundry](../../../ai-foundry/what-is-foundry.md) is a web-based platform that lets you use several Language features without needing to write code.
-* The [quickstart article](quickstart.md) for instructions on making requests to the service using the REST API and client library SDK.
+* The [quickstart article](quickstart.md) for instructions on making requests to the service using the REST API and client library SDK.
Summary
{
"modification_type": "minor update",
"modification_title": "言語検出機能の概要更新"
}
Explanation
この変更では、Azure Languageの「言語検出」機能に関する最新の情報が文書に反映されています。主な変更点として、タイトルが「Azure Language in Foundry Tools」から「Azure Language」に変更され、発行日が2025年11月18日から2026年3月30日に更新されました。
言語検出機能の説明が強化され、これはAzure Languageのコア機能として位置付けられ、100以上の言語をその主要なスクリプトで識別できるという点が明確化されています。また、言語検出サービスには、特定の言語に対してISO 15924標準に基づいたスクリプト検出機能も含まれています。
さらに、文書の中で言及される「エンティティリンク」機能の説明が「言語検出」機能に置き換えられ、言語の識別方法や信頼度スコア、スクリプト名、ISOコードなどの情報が詳述されています。全体として、この更新はユーザーに最新の機能と推奨される使用方法を提供することを目的としています。
articles/ai-services/language-service/media/overview/call-center-summarization.png
Summary
{
"modification_type": "minor update",
"modification_title": "コールセンター要約画像の更新"
}
Explanation
この変更は、コールセンター要約に関連する画像ファイル(call-center-summarization.png)に対して行われたもので、具体的にはファイル自体の内容が更新されることが示されています。変更の詳細には明示的な追加や削除はありませんが、画像のバージョンまたは品質が向上する可能性が考えられます。この更新は、コールセンター要約機能をより視覚的に示すための補助的な役割を果たしています。ユーザーにとってより良い理解を促進することが目的です。
articles/ai-services/language-service/media/overview/conversation-pii.png
Summary
{
"modification_type": "minor update",
"modification_title": "会話におけるPII画像の更新"
}
Explanation
この変更は、会話に関連する個人識別情報(PII)の画像ファイル(conversation-pii.png)に対して行われたもので、具体的な内容の追加や削除はありませんが、画像自体が更新されたことを示しています。画像の品質や視覚内容が改善された可能性があり、これによりユーザーが会話におけるPIIに関する概念をより良く理解できるようになります。この更新は、適切な情報を提供し、ユーザーの理解を深めるための役割を果たしています。
articles/ai-services/language-service/media/overview/conversation-summarization.png
Summary
{
"modification_type": "minor update",
"modification_title": "会話要約画像の更新"
}
Explanation
この変更は、会話要約に関連する画像ファイル(conversation-summarization.png)に対するもので、内容の追加や削除はありませんが、ファイルが更新されたことを示しています。画像の更新は、視覚的な説明をより効果的にするためのもので、ユーザーが会話要約機能を理解しやすくすることを目的としています。この更新により、情報の提示が改善され、全体的なユーザーエクスペリエンスが向上することが期待されます。
articles/ai-services/language-service/media/overview/conversational-language-understanding.png
Summary
{
"modification_type": "new feature",
"modification_title": "会話型言語理解の画像追加"
}
Explanation
この変更は、会話型言語理解に関連する新しい画像ファイル(conversational-language-understanding.png)の追加を示しています。この画像は、会話型言語理解の概念や機能を視覚的に表現するために使用され、ユーザーがサービスの利用方法や利点を把握しやすくすることを目的としています。この追加により、ドキュメントに視覚的な要素が加わり、全体的な情報の理解が向上することが期待されます。
articles/ai-services/language-service/media/overview/entity-linking.png
Summary
{
"modification_type": "new feature",
"modification_title": "エンティティリンクの画像追加"
}
Explanation
この変更は、新たにエンティティリンクに関連する画像ファイル(entity-linking.png)が追加されたことを示しています。この画像は、エンティティリンクの機能やプロセスを視覚的に説明することを目的としており、ユーザーがこのサービスの使い方や応用を理解するのに役立ちます。ドキュメント内に視覚的要素が追加されることで、情報の伝達がより効果的になり、ユーザーエクスペリエンスが向上することが期待されます。
articles/ai-services/language-service/media/overview/key-phrase-extraction.png
Summary
{
"modification_type": "minor update",
"modification_title": "キーフレーズ抽出の画像の修正"
}
Explanation
この変更は、キーフレーズ抽出に関連する画像ファイル(key-phrase-extraction.png)の修正を示しています。具体的な内容は明記されていませんが、画像が更新されることで、より正確な情報や視覚的要素が提供されることが期待されます。この修正は、ドキュメントの品質向上や、ユーザーがサービスの概念をより良く理解するのに寄与します。画像の変更により、エンティティ抽出のプロセスやその重要性に関する理解が深まることでしょう。
articles/ai-services/language-service/media/overview/language-detection.png
Summary
{
"modification_type": "minor update",
"modification_title": "言語検出の画像の修正"
}
Explanation
この変更は、言語検出に関連する画像ファイル(language-detection.png)が修正されたことを示しています。画像の具体的な変更点は記されていませんが、更新により、より明確で理にかなった情報や視覚的なコンテンツが提供されることが期待されます。この修正は、ユーザーに対して言語検出の機能やプロセスをより良く理解させるためのものであり、ドキュメントの内容が向上し、全体的なユーザーエクスペリエンスを高めることに寄与します。
articles/ai-services/language-service/media/overview/named-entity-recognition.png
Summary
{
"modification_type": "minor update",
"modification_title": "固有表現抽出の画像の修正"
}
Explanation
この変更は、固有表現抽出に関連する画像ファイル(named-entity-recognition.png)の修正を示しています。具体的な内容は記載されていませんが、画像の更新により、より正確で分かりやすいビジュアル情報が提供されることが予想されます。この修正は、固有表現抽出の概念やその適用方法をユーザーに対して明確に示し、ドキュメントの質を向上させることに寄与します。ユーザーは、画像を通じてこのAI機能の重要性や実用性をよりよく理解できるようになるでしょう。
articles/ai-services/language-service/media/overview/orchestration-workflow.png
Summary
{
"modification_type": "new feature",
"modification_title": "オーケストレーションワークフローの画像追加"
}
Explanation
この変更は、オーケストレーションワークフローに関連する新しい画像ファイル(orchestration-workflow.png)が追加されたことを示しています。この画像は、AIサービスのオーケストレーションプロセスを視覚的に表現するものであり、ユーザーがワークフローの全体像や各ステップの関係性を理解するのに役立ちます。新しいビジュアルコンテンツの追加により、ドキュメント全体の情報価値が向上し、特にオーケストレーション機能に関心のあるユーザーに対して、より親しみやすいリソースとなることが期待されます。
articles/ai-services/language-service/media/overview/question-answering.png
Summary
{
"modification_type": "new feature",
"modification_title": "質問応答機能の画像追加"
}
Explanation
この変更は、質問応答機能に関連する新たな画像ファイル(question-answering.png)が追加されたことを示しています。この画像は、AIサービスの質問応答機能を視覚的に説明するためのものであり、ユーザーがこの機能の使用方法やそのプロセスをよりよく理解できるように設計されています。新しいビジュアルコンテンツの追加により、ドキュメントの魅力が向上し、特に質問応答機能を利用しようとしているユーザーに対して、明確かつ効果的な情報が提供されることが期待されます。これにより、ユーザーはより自信を持ってAIサービスを活用できるようになるでしょう。
articles/ai-services/language-service/media/overview/sentiment-analysis.png
Summary
{
"modification_type": "minor update",
"modification_title": "感情分析機能画像の更新"
}
Explanation
この変更は、感情分析機能に関連する画像ファイル(sentiment-analysis.png)が更新されたことを示しています。具体的な変更内容は記載されていませんが、一般的には画像の品質向上や内容の調整、または最新の情報に基づく修正が行われることが想定されます。この更新により、ユーザーは感情分析機能の利用において、より正確で信頼性のあるビジュアル情報を得ることができます。ドキュメントの視覚的な要素が改善されることで、ユーザーの理解が促進され、より効果的な学習や利用が実現されることが期待されます。
articles/ai-services/language-service/media/overview/text-analytics-for-health.png
Summary
{
"modification_type": "minor update",
"modification_title": "健康向けテキスト分析機能画像の更新"
}
Explanation
この変更は、健康向けテキスト分析機能に関連する画像ファイル(text-analytics-for-health.png)が更新されたことを示しています。具体的な内容は不明ですが、通常、このような更新は画像の解像度向上や情報の更新、あるいはデザインの改善に関連していることが多いです。更新された画像は、ユーザーが健康データを分析するためのテキスト分析機能について、より明確で理解しやすい情報を提供することを目指しています。この変更により、文書の視覚的なクオリティが向上し、利用者がこの機能を効果的に活用できるようになることが期待されます。
articles/ai-services/language-service/media/overview/text-classification.png
Summary
{
"modification_type": "new feature",
"modification_title": "テキスト分類機能の画像追加"
}
Explanation
この変更は、テキスト分類機能に関連する新しい画像ファイル(text-classification.png)が追加されたことを示しています。この追加により、ドキュメントに視覚的な要素が強化され、ユーザーがテキスト分類機能の理解を深めるのに役立つ情報が提供されます。新しい画像は、機能の使用方法や応用例を示すために利用されることが考えられ、ユーザーにとって情報がより直感的に理解しやすくなる効果があります。これにより、文書の有用性が向上し、テキスト分類機能の使用促進が期待されます。
articles/ai-services/language-service/media/overview/text-pii.png
Summary
{
"modification_type": "minor update",
"modification_title": "テキストPII機能画像の更新"
}
Explanation
この変更は、テキストの個人識別情報(PII)に関連する画像ファイル(text-pii.png)が更新されたことを示しています。具体的な内容の詳細は提供されていませんが、一般的にこのような更新は画像の品質向上や情報の最新化、あるいはデザインの改善を目指して行われます。新しい画像は、ユーザーがテキストPII機能をより理解しやすくするためのビジュアルを提供し、情報の正確性や伝えたいメッセージを強化する役割を果たすことが期待されます。このような更新により、文書全体の品質が向上し、利用者がテキストに関するブラックアウトやプライバシー保護の機能を理解し、活用する手助けとなります。
articles/ai-services/language-service/media/overview/text-summarization.png
Summary
{
"modification_type": "minor update",
"modification_title": "テキスト要約機能画像の更新"
}
Explanation
この変更は、テキスト要約機能に関連する画像ファイル(text-summarization.png)が更新されたことを示しています。具体的な更新内容は記載されていないものの、この種の変更は通常、画像の改善や最新の情報に基づいたアップデートを目的としています。ユーザーに対してテキスト要約機能の使い方や特長をより理解しやすく伝えるために、視覚的な情報を向上させることが期待されます。新しい画像は、ドキュメント全体の視覚的な一貫性を保ちつつ、要約機能をより効果的に説明する役割を果たすことになります。この更新により、ユーザーが機能の利点を認識し、活用する助けとなるでしょう。
articles/ai-services/language-service/named-entity-recognition/overview.md
Diff
@@ -1,18 +1,19 @@
---
-title: What is the Named Entity Recognition (NER) feature in Azure Language in Foundry Tools?
+title: What is the named entity recognition (NER) feature in Azure Language?
titleSuffix: Foundry Tools
-description: An overview of the Named Entity Recognition feature in Azure Language, which helps you extract categories of entities in text.
+description: An overview of the named entity recognition feature in Azure Language, which helps you extract categories of entities in text.
author: laujan
manager: nitinme
ms.service: azure-ai-language
ms.topic: overview
-ms.date: 11/18/2025
+ms.date: 03/30/2026
ms.author: lajanuar
ms.custom: language-service-ner
---
-# What is Named Entity Recognition (NER) in Azure Language in Foundry Tools?
+<!-- markdownlint-disable MD025 -->
+# What is named entity recognition (NER) in Azure Language?
-Named Entity Recognition (NER) is one of the features offered by [Azure Language in Foundry Tools](../overview.md), a collection of machine learning and AI algorithms in the cloud for developing intelligent applications that involve written language. The NER feature can identify and categorize entities in unstructured text. For example: people, places, organizations, and quantities. The prebuilt NER feature has a preset list of [recognized entities](concepts/named-entity-categories.md). The custom NER feature allows you to train the model to recognize specialized entities specific to your use case.
+Named entity recognition (NER) is an Azure Language prebuilt [core capability](../overview.md#core-capabilities). The NER feature can identify and categorize entities in unstructured text such as people, places, organizations, and quantities. The prebuilt NER feature has a preset list of [recognized entities](concepts/named-entity-categories.md). The custom NER feature allows you to train the model to recognize specialized entities specific to your use case.
* [**Quickstarts**](quickstart.md) are getting-started instructions to guide you through making requests to the service.
* [**How-to guides**](how-to-call.md) contain instructions for using the service in more specific or customized ways.
Summary
{
"modification_type": "minor update",
"modification_title": "命名エンティティ認識機能の概要ドキュメントの修正"
}
Explanation
この変更は、Azureの命名エンティティ認識(NER)機能に関するドキュメント(overview.md)の修正を示しています。具体的には、タイトルや説明文の表現が改善され、より明確で簡潔になっています。変更された内容には、以下のポイントが含まれています。
- タイトルが「What is the Named Entity Recognition (NER) feature in Azure Language in Foundry Tools?」から「What is the named entity recognition (NER) feature in Azure Language?」に変更され、言葉の使い方が一貫性を持つよう修正されています。
- 説明文においても、表現が整理され、より簡潔に情報が伝えられるよう更新されています。
- 日付の更新が行われ、ドキュメントの最新性が確保されています。
これらの変更により、ユーザーがNER機能についてより理解しやすく、正確な情報にアクセスできるようになります。また、ドキュメント全体の整合性と可読性が向上しており、利用者の利便性が増しています。
articles/ai-services/language-service/orchestration-workflow/overview.md
Diff
@@ -6,13 +6,16 @@ author: laujan
manager: nitinme
ms.service: azure-ai-language
ms.topic: overview
-ms.date: 01/17/2026
+ms.date: 03/30/2026
ms.author: lajanuar
ms.custom: language-service-orchestration
---
<!-- markdownlint-disable MD025 -->
# What is orchestration workflow?
+> [!IMPORTANT]
+> Orchestration workflow is retiring from Azure Language effective **March 31, 2029**. After this date, the orchestration workflow feature is no longer supported. During the support window, we recommend that users migrate existing workloads and direct all new projects to [Microsoft Foundry models](../../../foundry/concepts/foundry-models-overview.md), which offer enhanced capabilities for natural language understanding and can be easily integrated into your applications.
+
Orchestration workflow is one of the features offered by [Azure Language in Foundry Tools](../overview.md). This cloud-based API service uses machine learning to facilitate the development of orchestration models that seamlessly integrate [Conversational Language Understanding (CLU)](../conversational-language-understanding/overview.md) and [Custom question Answering](../question-answering/overview.md) projects.
Developers can create an orchestration workflow to iteratively tag utterances, train models, and evaluate their performance before deployment.
Summary
{
"modification_type": "minor update",
"modification_title": "オーケストレーションワークフロー機能の引退に関する警告の追加"
}
Explanation
この変更は、オーケストレーションワークフローに関するドキュメント(overview.md)に対して行われた更新を示しています。主に、オーケストレーションワークフローの機能が引退することに関する重要な警告が追加されています。具体的には以下のポイントが修正されています。
- 新たに追加された重要なメッセージとして、「オーケストレーションワークフローは2029年3月31日をもってAzure Languageから引退する」という情報が掲載されました。この日付以降は、オーケストレーションワークフロー機能はサポートされなくなります。
- 引退に伴い、ユーザーには既存のワークロードの移行を推奨し、新たなプロジェクトにはMicrosoft Foundryモデルを利用するように指示されています。Foundryモデルは、自然言語理解の強化された機能を提供し、アプリケーションへの統合が容易です。
- その他、日付の更新や若干の文言の調整が行われています。
これにより、ユーザーは今後の計画を考慮する際に必要な情報を得ることができ、適切な措置を講じることが可能になります。また、全体的な文書の内容が最新の情報に基づいて更新されたことで、正確さと信頼性が向上しています。
articles/ai-services/language-service/overview.md
Diff
@@ -6,7 +6,7 @@ author: laujan
manager: nitinme
ms.service: azure-ai-language
ms.topic: overview
-ms.date: 11/18/2025
+ms.date: 03/30/2026
ms.author: lajanuar
---
@@ -15,226 +15,204 @@ ms.author: lajanuar
Azure Language is a cloud-based service that provides Natural Language Processing (NLP) features for understanding and analyzing text. Use this service to help build intelligent applications using the web-based Microsoft Foundry, REST APIs, and client libraries. For AI agent development, the service capabilities are also available as tools in Azure Language [MCP server](#azure-language-mcp-server), which is available both as a remote server in the **Microsoft Foundry Tool Catalog** and as a local server for self-hosted environments.
-## Available tools
+## Core capabilities
-Azure Language provides specialized tools that enable seamless integration between AI agents and language processing services through standardized protocols.
+**Recommended for new development**
-### Azure Language MCP server
+Core capabilities are the primary, actively evolving features of Azure Language. These features receive ongoing investment and feature updates, and are recommended for new development and long-term planning. If you are starting a new project or designing a future architecture, use core capabilities as the foundation for your natural language processing workflows.
-The MCP (Model Context Protocol) server creates a standardized bridge that connects AI agents directly to Azure Language services through industry-standard protocols. This integration enables developers to build sophisticated conversational applications with reliable natural language processing capabilities while ensuring enterprise-grade compliance, data protection, and processing accuracy throughout their AI workflows.
+* [Language detection](#language-detection)
+* **Named entity recognition (NER)**
+ * [Custom NER](#custom-ner)
+ * [Prebuilt NER](#prebuilt-ner)
+* [PII detection](#personally-identifiable-information-pii-detection)
+* [Text analytics for health](#text-analytics-for-health)
-Azure Language provides both remote and local MCP server options:
-* **Remote server**: Available through Foundry Tool Catalog for cloud-hosted deployments.
-* **Local server**: Available for developers who prefer to host the server in their own environment.
+> [!TIP]
+> Unsure which feature to use? See [Which Azure Language core feature should I use](#which-core-language-feature-should-i-use) to help you decide.
-For more information, *see* [Azure Language MCP server](concepts/foundry-tools-agents.md#azure-language-mcp-server-preview).
+[**Microsoft Foundry**](https://ai.azure.com/) enables you to use most of the following service features without the need to write code.
-## Available agents
+### Language detection
-Azure Language offers prebuilt agents that handle specific conversational AI scenarios with built-in governance, routing logic, and quality control mechanisms.
+[Language detection](./language-detection/overview.md) evaluates text and detects a wide range of languages and variant dialects.
-### Azure Language Intent Routing agent
+:::image type="content" source="media/overview/language-detection.png" alt-text="A screenshot of language detection in Foundry." lightbox="media/overview/language-detection.png":::
-The Intent Routing agent intelligently manages conversation flows by understanding user intentions and delivering accurate responses in conversational AI applications. This agent uses predictable decision-making processes combined with controlled response generation to ensure consistent, reliable interactions that organizations can trust and monitor.
+### Custom NER
-For more information, *see* [Azure Language Intent Routing agent](concepts/foundry-tools-agents.md#azure-language-intent-routing-agent-preview).
+[Custom named entity recognition (CNER)](custom-named-entity-recognition/overview.md) enables you to build custom AI models to extract custom entity categories (labels for words or phrases), using unstructured text that you provide.
-### Azure Language Exact Question Answering agent
+:::image type="content" source="media/studio-examples/custom-named-entity-recognition.png" alt-text="A screenshot of a custom NER example." lightbox="media/studio-examples/custom-named-entity-recognition.png":::
-The Exact Question Answering agent provides reliable, word-for-word responses to your most important business questions. This agent automates frequently asked questions while maintaining human oversight and quality control to ensure accuracy and compliance.
+### Prebuilt NER
-For more information, *see* [Azure Language Exact Question Answering agent](concepts/foundry-tools-agents.md#azure-language-exact-question-answering-agent-preview).
+[Prebuilt named entity recognition (NER)](./named-entity-recognition/overview.md) identifies different entries in text and categorizes them into predefined types.
-## Available features
+:::image type="content" source="media/overview/named-entity-recognition.png" alt-text="A screenshot of named entity recognition in Foundry." lightbox="media/overview/named-entity-recognition.png":::
-> [!TIP]
-> Unsure which feature to use? See [Which Language feature should I use](#which-language-feature-should-i-use) to help you decide.
+### Personally identifiable information (PII) detection
-[**Microsoft Foundry**](https://ai.azure.com/) enables you to use most of the following service features without the need to write code.
+> [!IMPORTANT]
+> The Azure Language in Foundry Tools text personally identifiable information (PII) detection anonymization feature (synthetic replacement) is currently available in `preview` and licensed to you as part of your Azure subscription. Your use of this feature is subject to the terms applicable to **Previews** as described in the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms) and the [Microsoft Products and Services Data Protection Addendum (DPA)](https://www.microsoft.com/licensing/docs/view/microsoft-products-and-services-data-protection-addendum-dpa).
-### Named Entity Recognition (NER)
+[Personally identifiable information (PII) detection](./personally-identifiable-information/overview.md) identifies entities in text and conversations (chat or transcripts) that are associated with individuals.
-:::row:::
- :::column span="":::
- :::image type="content" source="media/overview/named-entity-recognition.png" alt-text="A screenshot of named entity recognition in Foundry." lightbox="media/overview/named-entity-recognition.png":::
- :::column-end:::
- :::column span="":::
- [Named entity recognition](./named-entity-recognition/overview.md) identifies different entries in text and categorizes them into predefined types.
+***Conversation PII detection***
- :::column-end:::
-:::row-end:::
+:::image type="content" source="media/overview/conversation-pii.png" alt-text="A screenshot of conversation personally identifying information in Foundry." lightbox="media/overview/conversation-pii.png":::
-### Personal and health data information detection
+***Text PII detection***
-> [!IMPORTANT]
-> The Azure Language in Foundry Tools Text Personally Identifiable Information (PII) detection anonymization feature (synthetic replacement) is currently available in `preview` and licensed to you as part of your Azure subscription. Your use of this feature is subject to the terms applicable to **Previews** as described in the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms) and the [Microsoft Products and Services Data Protection Addendum (DPA)](https://www.microsoft.com/licensing/docs/view/microsoft-products-and-services-data-protection-addendum-dpa).
+:::image type="content" source="media/overview/text-pii.png" alt-text="A screenshot of text personally identifying information in Foundry." lightbox="media/overview/text-pii.png":::
-:::row:::
- :::column span="":::
- :::image type="content" source="media/overview/conversation-pii.png" alt-text="A screenshot of conversation personally identifying information in Foundry." lightbox="media/overview/conversation-pii.png":::
- :::image type="content" source="media/overview/text-pii.png" alt-text="A screenshot of text personally identifying information in Foundry." lightbox="media/overview/text-pii.png":::
- :::column-end:::
- :::column span="":::
+### Text analytics for health
- [Personally Identifiable Information (PII) detection](./personally-identifiable-information/overview.md) identifies entities in text and conversations (chat or transcripts) that are associated with individuals.
+[Text analytics for health](./text-analytics-for-health/overview.md) extracts and labels relevant health information from unstructured text.
- :::column-end:::
-:::row-end:::
+:::image type="content" source="media/overview/text-analytics-for-health.png" alt-text="A screenshot of text analytics for health in Foundry." lightbox="media/overview/text-analytics-for-health.png":::
-### Language detection
+## Legacy capabilities
-:::row:::
- :::column span="":::
- :::image type="content" source="media/overview/language-detection.png" alt-text="A screenshot of language detection in Foundry." lightbox="media/overview/language-detection.png":::
- :::column-end:::
- :::column span="":::
- [Language detection](./language-detection/overview.md) evaluates text and detects a wide range of languages and variant dialects.
+**Supported for existing implementations**
- :::column-end:::
-:::row-end:::
+Legacy capabilities are established features that provide a stable, supported base for existing workloads and scenarios. These features are supported for existing implementations and established use cases.
-### Sentiment Analysis and opinion mining
+* [Conversational language understanding](#conversational-language-understanding)
+* [Custom text classification](#custom-text-classification)
+* [Entity linking](#entity-linking)
+* [Key phrase extraction](#key-phrase-extraction)
+* [Orchestration workflow](#orchestration-workflow)
+* [Question answering](#question-answering)
+* [Sentiment analysis and opinion mining](#sentiment-analysis-and-opinion-mining)
+* [Summarization](#summarization)
-:::row:::
- :::column span="":::
- :::image type="content" source="media/overview/sentiment-analysis.png" alt-text="A screenshot of sentiment analysis in Foundry." lightbox="media/overview/sentiment-analysis.png":::
- :::column-end:::
- :::column span="":::
- [Sentiment analysis and opinion mining](./sentiment-opinion-mining/overview.md) preconfigured features that help you understand public perception of your brand or topic. These features analyze text to identify positive or negative sentiments and can link them to specific elements within the text.
+### Conversational language understanding
- :::column-end:::
-:::row-end:::
+[Conversational language understanding (CLU)](./conversational-language-understanding/overview.md) enables users to build custom natural language understanding models to predict the overall intention of an incoming utterance and extract important information from it.
-### Summarization
+:::image type="content" source="media/overview/conversational-language-understanding.png" alt-text="A screenshot of a conversational language understanding example." lightbox="media/overview/conversational-language-understanding.png":::
-:::row:::
- :::column span="":::
- :::image type="content" source="media/overview/conversation-summarization.png" alt-text="A screenshot of conversation summarization in Foundry." lightbox="media/overview/conversation-summarization.png":::
- :::image type="content" source="media/overview/call-center-summarization.png" alt-text="A screenshot of call center summarization in Foundry." lightbox="media/overview/call-center-summarization.png":::
- :::image type="content" source="media/overview/text-summarization.png" alt-text="A screenshot of text summarization in Foundry." lightbox="media/overview/text-summarization.png":::
- :::column-end:::
- :::column span="":::
- [Summarization](./summarization/overview.md) condenses information for text and conversations (chat and transcripts).
- Text summarization generates a summary, supporting two approaches: Extractive summarization creates a summary by selecting key sentences from the document and preserving their original positions. In contrast, abstractive summarization generates a summary by producing new, concise, and coherent sentences or phrases that aren't directly copied from the original document.
-Conversation summarization recaps and segments long meetings into timestamped chapters. Call center summarization summarizes customer issues and resolution.
- :::column-end:::
-:::row-end:::
+### Custom text classification
-### Key phrase extraction
+[Custom text classification](./custom-text-classification/overview.md) enables you to build custom AI models to classify unstructured text documents into custom classes you define. Creating a custom text classification project typically involves several different steps:
-:::row:::
- :::column span="":::
- :::image type="content" source="media/overview/key-phrase-extraction.png" alt-text="A screenshot of key phrase extraction in Foundry." lightbox="media/overview/key-phrase-extraction.png":::
- :::column-end:::
- :::column span="":::
- [Key phrase extraction](./key-phrase-extraction/overview.md) is a preconfigured feature that evaluates and returns the main concepts in unstructured text, and returns them as a list.
- :::column-end:::
-:::row-end:::
+:::image type="content" source="media/overview/text-classification.png" alt-text="A screenshot of a custom text classification example." lightbox="media/overview/text-classification.png":::
### Entity linking
-> [!IMPORTANT]
-> Entity Linking is retiring from Azure Language in Foundry Tools 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 Language [**Named Entity Recognition**](named-entity-recognition/overview.md) or consider other alternative solutions.
+[Entity linking](./entity-linking/overview.md) is a preconfigured feature that disambiguates the identity of entities (words or phrases) found in unstructured text and returns links to Wikipedia.
+:::image type="content" source="media/overview/entity-linking.png" alt-text="A screenshot of an entity linking example." lightbox="media/overview/entity-linking.png":::
-:::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":::
- :::column-end:::
- :::column span="":::
- [Entity linking](./entity-linking/overview.md) is a preconfigured feature that disambiguates the identity of entities (words or phrases) found in unstructured text and returns links to Wikipedia.
- :::column-end:::
-:::row-end:::
+### Key phrase extraction
-### Text analytics for health
+[Key phrase extraction](./key-phrase-extraction/overview.md) is a preconfigured feature that evaluates and returns the main concepts in unstructured text, and returns them as a list.
-:::row:::
- :::column span="":::
- :::image type="content" source="media/overview/text-analytics-for-health.png" alt-text="A screenshot of text analytics for health in Foundry." lightbox="media/overview/text-analytics-for-health.png":::
- :::column-end:::
- :::column span="":::
- [Text analytics for health](./text-analytics-for-health/overview.md) Extracts and labels relevant health information from unstructured text.
- :::column-end:::
-:::row-end:::
+:::image type="content" source="media/overview/key-phrase-extraction.png" alt-text="A screenshot of key phrase extraction in Foundry." lightbox="media/overview/key-phrase-extraction.png":::
-### Custom text classification
+### Orchestration workflow
-:::row:::
- :::column span="":::
- :::image type="content" source="media/studio-examples/single-classification.png" alt-text="A screenshot of a custom text classification example." lightbox="media/studio-examples/single-classification.png":::
- :::column-end:::
- :::column span="":::
- [Custom text classification](./custom-text-classification/overview.md) enables you to build custom AI models to classify unstructured text documents into custom classes you define.
- :::column-end:::
-:::row-end:::
+[Orchestration workflow](./orchestration-workflow/overview.md) is a custom feature that enables you to connect [conversational language understanding (CLU)](./conversational-language-understanding/overview.md) AND [custom question answering (CQA)](./question-answering/overview.md) applications.
-### Custom Named Entity Recognition (Custom NER)
+:::image type="content" source="media/overview/orchestration-workflow.png" alt-text="A screenshot of an orchestration workflow example." lightbox="media/overview/orchestration-workflow.png":::
+### Question answering
-:::row:::
- :::column span="":::
- :::image type="content" source="media/studio-examples/custom-named-entity-recognition.png" alt-text="A screenshot of a custom NER example." lightbox="media/studio-examples/custom-named-entity-recognition.png":::
- :::column-end:::
- :::column span="":::
- [Custom NER](custom-named-entity-recognition/overview.md) enables you to build custom AI models to extract custom entity categories (labels for words or phrases), using unstructured text that you provide.
- :::column-end:::
-:::row-end:::
+[Question answering](./question-answering/overview.md) is a custom feature that identifies the most suitable answer for user inputs. This feature is typically utilized to develop conversational client applications, including social media platforms, chat bots, and speech-enabled desktop applications.
+:::image type="content" source="media/overview/question-answering.png" alt-text="A screenshot of a question answering example." lightbox="media/overview/question-answering.png":::
-### Conversational language understanding
+### Sentiment analysis and opinion mining
-:::row:::
- :::column span="":::
- :::image type="content" source="media/studio-examples/conversational-language-understanding.png" alt-text="A screenshot of a conversational language understanding example." lightbox="media/studio-examples/conversational-language-understanding.png":::
- :::column-end:::
- :::column span="":::
- [Conversational language understanding (CLU)](./conversational-language-understanding/overview.md) enables users to build custom natural language understanding models to predict the overall intention of an incoming utterance and extract important information from it.
- :::column-end:::
-:::row-end:::
+[Sentiment analysis and opinion mining](./sentiment-opinion-mining/overview.md) preconfigured features that help you understand public perception of your brand or topic. These features analyze text to identify positive or negative sentiments and can link them to specific elements within the text.
-### Orchestration workflow
+:::image type="content" source="media/overview/sentiment-analysis.png" alt-text="A screenshot of sentiment analysis in Foundry." lightbox="media/overview/sentiment-analysis.png":::
-:::row:::
- :::column span="":::
- :::image type="content" source="media/studio-examples/orchestration-workflow.png" alt-text="A screenshot of an orchestration workflow example." lightbox="media/studio-examples/orchestration-workflow.png":::
- :::column-end:::
- :::column span="":::
- [Orchestration workflow](./language-detection/overview.md) is a custom feature that enables you to connect [Conversational Language Understanding (CLU)](./conversational-language-understanding/overview.md), [question answering](./question-answering/overview.md), and [LUIS](../LUIS/what-is-luis.md) applications.
+### Summarization
- :::column-end:::
-:::row-end:::
+[Summarization](./summarization/overview.md) condenses information for text and conversations (chat and transcripts).
-### Question answering
+##### Conversation summarization
+
+Conversation summarization recaps and segments long meetings into timestamped chapters.
+
+:::image type="content" source="media/overview/conversation-summarization.png" alt-text="A screenshot of conversation summarization in Foundry." lightbox="media/overview/conversation-summarization.png":::
+
+##### Call center summarization
+
+Call center summarization summarizes customer issues and resolution.
+
+:::image type="content" source="media/overview/call-center-summarization.png" alt-text="A screenshot of call center summarization in Foundry." lightbox="media/overview/call-center-summarization.png":::
-:::row:::
- :::column span="":::
- :::image type="content" source="media/studio-examples/question-answering.png" alt-text="A screenshot of a question answering example." lightbox="media/studio-examples/question-answering.png":::
- :::column-end:::
- :::column span="":::
- [Question answering](./question-answering/overview.md) is a custom feature that identifies the most suitable answer for user inputs. This feature is typically utilized to develop conversational client applications, including social media platforms, chat bots, and speech-enabled desktop applications.
+##### Text summarization
- :::column-end:::
-:::row-end:::
+Text summarization generates a summary, supporting two approaches:
-## Which Language feature should I use?
+* **Extractive summarization** creates a summary by selecting key sentences from the document and preserving their original positions.
+* **Abstractive summarization** generates a summary by producing new, concise, and coherent sentences or phrases that aren't directly copied from the original document.
-This section helps you decide which Language feature you should use for your application:
+ :::image type="content" source="media/overview/text-summarization.png" alt-text="A screenshot of text summarization in Foundry." lightbox="media/overview/text-summarization.png":::
-|What do you want to do? |Document format |Your best solution | Is this solution customizable?* |
-|---------|---------|---------|---------|
+## Available tools
+
+Azure Language provides specialized tools that enable seamless integration between AI agents and language processing services through standardized protocols.
+
+### Azure Language MCP server
+
+The MCP (Model Context Protocol) server creates a standardized bridge that connects AI agents directly to Azure Language services through industry-standard protocols. This integration enables developers to build sophisticated conversational applications with reliable natural language processing capabilities while ensuring enterprise-grade compliance, data protection, and processing accuracy throughout their AI workflows.
+
+Azure Language provides both remote and local MCP server options:
+
+* **Remote server**: Available through Foundry Tool Catalog for cloud-hosted deployments.
+* **Local server**: Available for developers who prefer to host the server in their own environment.
+
+For more information, *see* [Azure Language MCP server](concepts/foundry-tools-agents.md#azure-language-mcp-server-preview).
+
+## Azure Language agents
+
+Azure Language offers prebuilt agents that handle specific conversational AI scenarios with built-in governance, routing logic, and quality control mechanisms.
+
+### Azure Language Intent Routing agent
+
+The Intent Routing agent intelligently manages conversation flows by understanding user intentions and delivering accurate responses in conversational AI applications. This agent uses predictable decision-making processes combined with controlled response generation to ensure consistent, reliable interactions that organizations can trust and monitor.
+
+For more information, *see* [Azure Language Intent Routing agent](concepts/foundry-tools-agents.md#azure-language-intent-routing-agent-preview).
+
+### Azure Language Exact Question Answering agent
+
+The Exact Question Answering agent provides reliable, word-for-word responses to your most important business questions. This agent automates frequently asked questions while maintaining human oversight and quality control to ensure accuracy and compliance.
+
+For more information, *see* [Azure Language Exact Question Answering agent](concepts/foundry-tools-agents.md#azure-language-exact-question-answering-agent-preview).
+
+## Which core Language feature should I use?
+
+This section helps you decide which core Language feature you should use for your application:
+
+| What do you want to do? | Document format | Your best solution | Is this solution customizable?* |
+| --------- | --------- | --------- | --------- |
| Detect and/or redact sensitive information such as `PII` and `PHI`. | Unstructured text, <br> transcribed conversations | [PII detection](./personally-identifiable-information/overview.md) | |
-| Extract categories of information without creating a custom model. | Unstructured text | The [preconfigured NER feature](./named-entity-recognition/overview.md) | |
+| Extract categories of information without creating a custom model. | Unstructured text | The [preconfigured NER feature](./named-entity-recognition/overview.md) | |
| Extract categories of information using a model specific to your data. | Unstructured text | [Custom NER](./custom-named-entity-recognition/overview.md) | ✓ |
-|Extract main topics and important phrases. | Unstructured text | [Key phrase extraction](./key-phrase-extraction/overview.md) | |
-| Determine the sentiment and opinions expressed in text. | Unstructured text | [Sentiment analysis and opinion mining](./sentiment-opinion-mining/overview.md) | |
+| Extract medical information from clinical/medical documents, without building a model. | Unstructured text | [Text analytics for health](./text-analytics-for-health/overview.md) | |
+
+\* If a feature is customizable, you can train an AI model using our tools to fit your data specifically. Otherwise a feature is preconfigured, meaning the AI models it uses can't be changed. You just send your data, and use the feature's output in your applications.
+
+### Which legacy Language feature should I use?
+
+This section helps you decide which legacy Language feature you should use for your application:
+
+| What do you want to do? | Document format | Your best solution | Is this solution customizable?* |
+| --------- | --------- | --------- | --------- |
+| Extract main topics and important phrases. | Unstructured text | [Key phrase extraction](./key-phrase-extraction/overview.md) | |
+| Determine the sentiment and opinions expressed in text. | Unstructured text | [Sentiment analysis and opinion mining](./sentiment-opinion-mining/overview.md) | |
| Summarize long chunks of text or conversations. | Unstructured text, <br> transcribed conversations. | [Summarization](./summarization/overview.md) | |
| Disambiguate entities and get links to Wikipedia. | Unstructured text | [Entity linking](./entity-linking/overview.md) | |
-| Classify documents into one or more categories. | Unstructured text | [Custom text classification](./custom-text-classification/overview.md) | ✓|
-| Extract medical information from clinical/medical documents, without building a model. | Unstructured text | [Text analytics for health](./text-analytics-for-health/overview.md) | |
-| Build a conversational application that responds to user inputs. | Unstructured user inputs | [Question answering](./question-answering/overview.md) | ✓ |
+| Classify documents into one or more categories. | Unstructured text | [Custom text classification](./custom-text-classification/overview.md) | ✓ |
| Detect the language that a text was written in. | Unstructured text | [Language detection](./language-detection/overview.md) | |
| Predict the intention of user inputs and extract information from them. | Unstructured user inputs | [Conversational language understanding](./conversational-language-understanding/overview.md) | ✓ |
-| Connect apps from conversational language understanding, LUIS, and question answering. | Unstructured user inputs | [Orchestration workflow](./orchestration-workflow/overview.md) | ✓ |
+| Connect apps from conversational language understanding and custom question answering. | Unstructured user inputs | [Orchestration workflow](./orchestration-workflow/overview.md) | ✓ |
+| Build a conversational application that responds to user inputs. | Unstructured user inputs | [Question answering](./question-answering/overview.md) | ✓ |
\* If a feature is customizable, you can train an AI model using our tools to fit your data specifically. Otherwise a feature is preconfigured, meaning the AI models it uses can't be changed. You just send your data, and use the feature's output in your applications.
@@ -258,13 +236,14 @@ You can find more code samples on GitHub for the following languages:
* [Python](https://github.com/Azure/azure-sdk-for-python/tree/main/sdk/textanalytics/azure-ai-textanalytics/samples)
## Deploy on premises using Docker containers
+
Use Language containers to deploy API features on-premises. These Docker containers enable you to bring the service closer to your data for compliance, security, or other operational reasons. The Language offers the following containers:
* [Sentiment analysis](sentiment-opinion-mining/how-to/use-containers.md)
* [Language detection](language-detection/how-to/use-containers.md)
* [Key phrase extraction](key-phrase-extraction/how-to/use-containers.md)
-* [Custom Named Entity Recognition](custom-named-entity-recognition/how-to/use-containers.md)
-* [Text Analytics for health](text-analytics-for-health/how-to/use-containers.md)
+* [Custom named entity recognition](custom-named-entity-recognition/how-to/use-containers.md)
+* [Text analytics for health](text-analytics-for-health/how-to/use-containers.md)
* [Summarization](summarization/how-to/use-containers.md)
## Responsible AI
Summary
{
"modification_type": "breaking change",
"modification_title": "Azure Language サービスのコア機能と推奨内容の更新"
}
Explanation
この変更は、Azure Language サービスの概要ドキュメント(overview.md)に対して行われた重要な更新を示しています。主な変更点は以下の通りです。
ドキュメントの内容が大幅に改訂され、「Available tools」セクションが「Core capabilities」に変更され、Azure Language サービスのコア機能に焦点が当てられるようになりました。これにより、これらの機能が新しいプロジェクトや長期計画において推奨される基盤であることが強調されています。
以前のツールや機能が大幅に再編成され、特に新しい開発プロジェクトに対しては「Core capabilities」が推奨されています。これには言語検出、命名エンティティ認識(NER)、個人を特定できる情報(PII)検出、健康に関するテキスト分析などが含まれています。
引退予定の機能についても明記されており、ユーザーはそれに基づいて新しいプロジェクトの計画を立てやすくなっています。特定の機能(例えば、エンティティリンク)が引退する日付も示され、既存のワークロードの移行がすすめられています。
コンテンツの整合性や可読性を向上させるために、情報が整理され、図や例も追加されました。また、文書内の言葉遣いや構造が更新されており、利用者にとっての明確さが向上しています。
これらの変更により、今後のAzure Language サービスの使用についての戦略的な指針が明確になり、ユーザーが既存のワークフローをどのように移行または設計すべきか理解するのを助けるように図られています。
articles/ai-services/language-service/personally-identifiable-information/includes/quickstarts/azure-ai-foundry.md
Diff
@@ -8,6 +8,7 @@ ms.author: lajanuar
ms.custom: language-service-pii
ai-usage: ai-assisted
---
+
## Prerequisites
> [!TIP]
Summary
{
"modification_type": "minor update",
"modification_title": "クイックスタートに関する前提条件セクションの追加"
}
Explanation
この変更は、Azure AI Foundry に関するクイックスタートガイド(azure-ai-foundry.md)に対して行われた軽微な更新を示しています。具体的には、「Prerequisites」(前提条件)セクションが追加されました。
変更された部分は、ドキュメントの先頭近くに挿入されており、ユーザーがAzure AI Foundryを使用する際に必要な準備や条件についての情報を提供します。この情報は、クイックスタートを利用する前に確認すべき項目を明確にするためのものです。
また、追加された内容は、特定のヒント情報として強調表示されているため、読者が容易に認識しやすい形式になっています。このように、クイックスタートに関する情報が充実することにより、ユーザーの利便性が向上し、導入プロセスがスムーズに行えるようになります。
全体的に見て、今回の変更はドキュメントの明確さを増し、使用者が必要な情報を素早く把握できるようにすることを目的としています。
articles/ai-services/language-service/personally-identifiable-information/overview.md
Diff
@@ -1,20 +1,20 @@
---
-title: What is the Personally Identifying Information (PII) detection feature in Azure Language in Foundry Tools?
+title: What is the Personally Identifying Information (PII) detection feature in Azure Language?
titleSuffix: Foundry Tools
description: An overview of the PII detection feature in Azure Language, which helps you extract entities and sensitive information (PII) in text.
author: laujan
manager: nitinme
ms.service: azure-ai-language
ms.topic: overview
-ms.date: 01/18/2026
+ms.date: 03/30/2026
ms.author: lajanuar
ms.custom: language-service-pii
---
<!-- markdownlint-disable MD025 -->
-# What is Azure Language PII detection?
+# What is PII detection in Azure Language?
-Azure Language in Foundry Tools Personally Identifiable Information (PII) detection is a feature offered by [Azure Language](../overview.md). The PII detection service is a cloud-based API that utilizes machine learning and AI algorithms to help you develop intelligent applications with advanced natural language understanding. Azure Language PII detection uses Named Entity Recognition (NER) to **identify and redact** sensitive information from input data. The service classifies sensitive personal data into predefined categories. These categories include phone numbers, email addresses, and identification documents. This classification helps to efficiently detect and eliminate such information.
+Personally Identifiable Information (PII) detection is an Azure Language [core capability](../overview.md#core-capabilities). The PII detection service is a cloud-based API that uses machine learning to **identify and redact** sensitive information from input data. The service classifies sensitive personal data into predefined categories such as phone numbers, email addresses, and identification documents.
> [!TIP]
> Try PII detection [in Microsoft Foundry portal](https://ai.azure.com/). There you can [utilize a currently existing Language Studio resource or create a new Foundry resource](../../../ai-services/connect-services-foundry-portal.md).
Summary
{
"modification_type": "minor update",
"modification_title": "PII検出機能に関するドキュメントの更新"
}
Explanation
この変更は、Azure Language サービスにおける個人を特定できる情報(PII)検出機能のオーバービュー(overview.md)に対して行われた軽微な更新を示しています。主な変更点は以下の通りです。
ドキュメントのタイトルが変更され、より簡潔で明確な表現に更新されました。「What is the Personally Identifying Information (PII) detection feature in Azure Language in Foundry Tools?」から「What is PII detection in Azure Language?」に変更されました。
最終更新日も更新され、新しい日付(2026年3月30日)が設定されました。これは、技術文書の最新性を保つために重要です。
概要部分の文言も改善され、PII検出機能がAzure Languageの「コア機能」として明示されました。また、拡張性を持つサービスとしての特性が強調されており、機械学習を利用して情報を識別し、消去することができる点が説明されています。
提供される情報においては、事前定義されたカテゴリのリスト(電話番号、メールアドレス、識別書類など)も維持されており、機能の目的と基本的な動作が明確に述べられています。
最後に、読者がMicrosoft Foundryポータルでこの機能を試すことができるという提案が加えられ、実践的な利用への誘導がなされています。
全体として、これらの変更は文章の明確さを向上させ、利用者が必要な情報に迅速にアクセスできるようにしています。また、個人を特定できる情報の扱いに関する重要な機能が、より簡潔に伝えられるようになっています。
articles/ai-services/language-service/question-answering/overview.md
Diff
@@ -7,12 +7,16 @@ author: laujan
ms.author: lajanuar
recommendations: false
ms.topic: overview
-ms.date: 03/06/2026
+ms.date: 03/30/2026
keywords: "low code chat bots, multi-turn conversations"
ms.custom: language-service-question-answering
---
+<!-- markdownlint-disable MD025 -->
# What is custom question answering?
+> [!IMPORTANT]
+> Custom question answering is retiring from Azure Language effective **March 31, 2029**. After this date, the CQA feature is no longer supported. During the support window, we recommend that users migrate existing workloads and direct all new projects to [Microsoft Foundry models](../../../foundry/concepts/foundry-models-overview.md), which offer enhanced capabilities for natural language understanding and can be easily integrated into your applications.
+
Custom question answering (CQA) is a cloud-based Natural Language Processing (NLP) service that creates conversational AI applications over your data. Build knowledge bases from FAQs, manuals, and documents to deliver accurate answers through chat bots, virtual assistants, and interactive interfaces.
## Key capabilities
Summary
{
"modification_type": "minor update",
"modification_title": "カスタム質問応答機能に関する重要情報の追加"
}
Explanation
この変更は、Azure Language サービスのカスタム質問応答機能に関するオーバービュー(overview.md)に加えられた軽微な更新を示しています。主な変更点は以下の通りです。
最終更新日が更新され、2026年3月30日と設定されました。これにより、ドキュメントの最新性が確保されています。
重要なお知らせセクションが追加され、「カスタム質問応答機能(CQA)」が2029年3月31日に退役することが明記されました。この日付以降はCQA機能がサポートされなくなるため、既存の作業負荷を移行することを推奨しています。また、新しいプロジェクトには「Microsoft Foundryモデル」への移行が勧められており、これが自然言語理解の強化された機能を提供し、アプリケーションへの統合も容易であることが伝えられています。
機能説明において、カスタム質問応答(CQA)の目的および機能が明確に述べられています。CQAがどのようなサービスであり、FAQやマニュアル、文書などから知識ベースを構築し、チャットボットやバーチャルアシスタントを通じて正確な回答を提供するものであるかが説明されています。
全体として、これらの変更はドキュメントの明確性を高め、ユーザーがカスタム質問応答機能の将来的な支援終了についてしっかりと理解できるようにしています。また、代替手段であるMicrosoft Foundryモデルへの移行を促すことで、読者に実用的なアドバイスを提供しています。
articles/ai-services/language-service/sentiment-opinion-mining/overview.md
Diff
@@ -6,11 +6,15 @@ author: laujan
manager: nitinme
ms.service: azure-ai-language
ms.topic: overview
-ms.date: 11/18/2025
+ms.date: 03/30/2026
ms.author: lajanuar
ms.custom: language-service-sentiment-opinion-mining
---
-# What is sentiment analysis and opinion mining?
+<!-- markdownlint-disable MD025 -->
+# What are sentiment analysis and opinion mining?
+
+> [!IMPORTANT]
+> Sentiment analysis and opinion mining are retiring from Azure Language effective **March 31, 2029**. After this date, these features are no longer supported. During the support window, we recommend that users migrate existing workloads and direct all new projects to [Microsoft Foundry models](../../../foundry/concepts/foundry-models-overview.md), which offer enhanced capabilities for natural language understanding and can be easily integrated into your applications.
Sentiment analysis and opinion mining are features offered by [Azure Language](../overview.md), a collection of machine learning and AI algorithms in the cloud for developing intelligent applications that involve written language. These features help you discover what people think about your brand or topic by analyzing text for signs of positive or negative sentiment. They can also link these sentiments to specific aspects of the text.
@@ -36,10 +40,10 @@ Opinion mining is a feature of sentiment analysis, also known as aspect-based se
As you use sentiment analysis, see the following reference documentation and samples for Azure Language:
-|Development option / language |Reference documentation |Samples |
-|---------|---------|---------|
-|REST APIs (Authoring) | [REST API documentation](https://aka.ms/ct-authoring-swagger) | |
-|REST APIs (Runtime) | [REST API documentation](https://aka.ms/ct-runtime-swagger) | |
+| Development option / language | Reference documentation | Samples |
+| -- | -- | -- |
+| REST APIs (Authoring) | [REST API documentation](https://aka.ms/ct-authoring-swagger) | |
+| REST APIs (Runtime) | [REST API documentation](https://aka.ms/ct-runtime-swagger) | |
---
Summary
{
"modification_type": "minor update",
"modification_title": "感情分析と意見マイニング機能に関する重要情報の追加"
}
Explanation
この変更は、Azure Language サービスの感情分析と意見マイニングに関するオーバービュー(overview.md)に対して行われた軽微な更新を示しています。主な変更点は以下の通りです。
最終更新日が2026年3月30日に変更され、文書の最新情報が反映されました。
セクションのタイトルが「What is sentiment analysis and opinion mining?」から「What are sentiment analysis and opinion mining?」へと修正され、文の整合性が改善されました。
重要なお知らせセクションが追加され、感情分析および意見マイニングが2029年3月31日に退役することが明記されました。この日以降はこれらの機能がサポートされなくなるため、ユーザーには既存の作業を移行し、新しいプロジェクトでは「Microsoft Foundryモデル」を使用することが推奨されています。このモデルは、自然言語理解の強化機能を提供し、アプリケーションへの統合が容易であることが強調されています。
提供される情報の説明において、感情分析と意見マイニングがどのように機能し、テキストの肯定的または否定的な感情を分析してブランドやトピックについての見解を発見する手助けをするかが詳述されています。
さらに、リファレンスドキュメントとサンプルに関連するテーブルが整然と更新され、各開発オプションに対する文書とサンプルの提供状況が確認できるようになっています。
全体として、これらの変更は読者に対する重要な情報を提供し、将来的なサポートの終了についての明確なガイダンスを示しています。また、文書の整合性と可読性を高めるために必要な変更も行われています。
articles/ai-services/language-service/summarization/includes/regional-availability.md
Diff
@@ -3,16 +3,17 @@ author: laujan
manager: nitinme
ms.service: azure-ai-language
ms.topic: include
-ms.date: 11/18/2025
+ms.date: 03/27/2026
ms.author: lajanuar
ms.custom:
- references_regions
- - ignite-2023
---
+
> [!IMPORTANT]
> Our preview region, Sweden Central, showcases our latest and continually evolving LLM fine tuning techniques based on GPT models. You're welcome to try them out with a Language resource in the Sweden Central region.
>
> Conversation summarization is only available using:
-> - REST API
-> - Python
-> - C#
+>
+> * REST API
+> * Python
+> * C#
Summary
{
"modification_type": "minor update",
"modification_title": "地域の可用性に関する情報の更新"
}
Explanation
この変更は、Azure Language サービスの要約機能に関する地域の可用性情報(regional-availability.md)に対して行われた軽微な更新を示しています。主な変更点は以下の通りです。
最終更新日が2026年3月27日に変更され、文書が最新の情報を反映するようになりました。
重要なお知らせセクションが追加され、スウェーデン中央地域がプレビュー地域として、最新の大規模言語モデル(LLM)のファインチューニング技術を示す場所であることが説明されています。この地域で言語リソースを使用してこれらの技術を試すことができることが強調され、利用者への呼びかけが行われています。
「会話の要約」は利用可能なインターフェースのリストにおいて、マークダウンのリスト形式が変更されました。具体的には、選択肢が箇条書きに整形され、視認性が向上しています。
全体として、これらの変更は利用者に対する重要な最新情報を提供し、新しい地域における機能の利用を促進するために情報を明確にしています。また、文書の可読性と整頓が改善されています。
articles/ai-services/language-service/summarization/overview.md
Diff
@@ -6,13 +6,15 @@ author: laujan
manager: nitinme
ms.service: azure-ai-language
ms.topic: overview
-ms.date: 11/18/2025
+ms.date: 03/30/2026
ms.author: lajanuar
ms.custom: language-service-summarization, build-2024, ignite-2024
---
+<!-- markdownlint-disable MD025 -->
# What is summarization?
-[!INCLUDE [availability](includes/regional-availability.md)]
+> [!IMPORTANT]
+> Summarization is retiring from Azure Language effective **March 31, 2029**. After this date, the summarization feature is no longer supported. During the support window, we recommend that users migrate existing workloads and direct all new projects to [Microsoft Foundry models](../../../foundry/concepts/foundry-models-overview.md), which offer enhanced capabilities for natural language understanding and can be easily integrated into your applications.
Summarization is a feature offered by [Azure Language in Foundry Tools](../overview.md), a combination of generative Large Language models and task-optimized encoder models that offer summarization solutions with higher quality, cost efficiency, and lower latency.
Use this article to learn more about this feature, and how to use it in your applications.
@@ -57,9 +59,10 @@ The text summarization API request is processed upon receipt of the request by c
If we use the preceding example, the API might return these summaries:
**Extractive summarization**:
-- "At Microsoft, we are on a quest to advance AI beyond existing techniques, by taking a more holistic, human-centric approach to learning and understanding."
-- "We believe XYZ-code enables us to fulfill our long-term vision: cross-domain transfer learning, spanning modalities and languages."
-- "The goal is to have pretrained models that can jointly learn representations to support a broad range of downstream AI tasks, much in the way humans do today."
+
+* "At Microsoft, we are on a quest to advance AI beyond existing techniques, by taking a more holistic, human-centric approach to learning and understanding."
+* "We believe XYZ-code enables us to fulfill our long-term vision: cross-domain transfer learning, spanning modalities and languages."
+* "The goal is to have pretrained models that can jointly learn representations to support a broad range of downstream AI tasks, much in the way humans do today."
**Abstractive summarization**:
- "Microsoft is taking a more holistic, human-centric approach to learning and understanding. We believe XYZ-code enables us to fulfill our long-term vision: cross-domain transfer learning, spanning modalities and languages. Over the past five years, we achieved human performance on benchmarks in conversational speech recognition."
@@ -102,8 +105,8 @@ As an example, consider the following example conversation:
Conversation summarization feature would simplify the text as follows:
-|Example summary | Remark | Conversation aspect |
-|---------|----|----|
+| Example summary | Remark | Conversation aspect |
+| ---------| ---- | ---- |
| Customer is unable to set up wifi connection for Smart Brew 300 espresso machine | a customer issue in a customer-and-agent conversation | issue |
| The agent suggested several troubleshooting steps, including checking the wifi connection, checking the Contoso Coffee app, and performing a factory reset. However, none of these steps resolved the issue. The agent then put the customer on hold to look for another solution. | solutions tried in a customer-and-agent conversation | resolution |
| The customer contacted the agent for assistance with setting up a wifi connection for their Smart Brew 300 espresso machine. The agent guided the customer through several troubleshooting steps, including a wifi connection check, checking the power light, and a factory reset. Despite following these steps, the issue persisted. The agent then decided to explore other potential solutions | Summarizes a conversation into one paragraph | recap |
@@ -149,17 +152,17 @@ For more information, *see* [**Summarize native documents**](how-to/document-sum
## Input requirements and service limits
-# [Text summarization](#tab/text-summarization)
+### [Text summarization](#tab/text-summarization)
* Summarization takes text for analysis. For more information, see [Data and service limits](../concepts/data-limits.md) in the how-to guide.
* Summarization works with various written languages. For more information, see [language support](language-support.md?tabs=text-summarization).
-# [Conversation summarization](#tab/conversation-summarization)
+### [Conversation summarization](#tab/conversation-summarization)
* Conversation summarization takes structured text for analysis. For more information, see [data and service limits](../concepts/data-limits.md).
* Conversation summarization works with various spoken languages. For more information, see [language support](language-support.md?tabs=conversation-summarization).
-# [Document summarization](#tab/document-summarization)
+### [Document summarization](#tab/document-summarization)
* Summarization takes text for analysis. For more information, see [Data and service limits](../concepts/data-limits.md) in the how-to guide.
* Summarization works with various written languages. For more information, see [language support](language-support.md?tabs=document-summarization).
Summary
{
"modification_type": "minor update",
"modification_title": "要約機能に関する重要情報の追加と更新"
}
Explanation
この変更は、Azure Language サービスの要約機能に関するオーバービュー(overview.md)に対して行われた軽微な更新を示しています。主な変更点は以下の通りです。
最終更新日が2026年3月30日に変更され、文書が最新の情報を反映するようになりました。
要約機能が2029年3月31日に退役することが明記され、以降はサポートされなくなる旨が強調されています。この日以降のユーザーには、既存の作業の移行や新しいプロジェクトを「Microsoft Foundryモデル」に向けることが推奨されています。このモデルは、自然言語理解の向上に向けた新機能を提供することが示されています。
要約機能は、生成的な大規模言語モデルとタスク最適化されたエンコーダーモデルの組み合わせを使用し、高品質でコスト効率が高く、低待機時間の要約ソリューションを提供する旨が説明されています。
いくつかの形式が改善され、特に要約の例がリスト形式に整形され、視認性が向上しました。
セクションの見出しを「Text summarization」から「### Text summarization」のように変更することで、構造が一貫して整理されました。
全体として、これらの変更は要約機能に関する重要な情報を提供し、ユーザーに対する警告と推奨事項を明確にしています。また、文書の可読性と情報の整った提示が強化されています。
articles/ai-services/language-service/text-analytics-for-health/overview.md
Diff
@@ -1,53 +1,54 @@
---
-title: What is the Text Analytics for health in Azure Language in Foundry Tools?
+title: What is Text analytics for health in Azure Language?
titleSuffix: Foundry Tools
-description: An overview of Text Analytics for health in Azure Language, which helps you extract medical information from unstructured text, like clinical documents.
+description: An overview of Text analytics for health in Azure Language, which helps you extract medical information from unstructured text, like clinical documents.
#services: cognitive-services
author: laujan
manager: nitinme
ms.service: azure-ai-language
ms.topic: overview
-ms.date: 12/15/2025
+ms.date: 03/30/2026
ms.author: lajanuar
ms.custom: language-service-health
---
-# What is Text Analytics for health?
+<!-- markdownlint-disable MD025 -->
+# What is Text analytics for health in Azure Language?
[!INCLUDE [service notice](includes/service-notice.md)]
-Text Analytics for health is one of the prebuilt features offered by [Azure Language in Foundry Tools](../overview.md). Text Analytics for health uses machine learning to identify and label medical information in unstructured text such as doctor's notes, clinical documents, and electronic health records. It extracts key data from sources like discharge summaries to support healthcare analysis.
+Text analytics for health is an Azure Language prebuilt [core capability](../overview.md#core-capabilities). Text analytics for health uses machine learning to identify and label medical information in unstructured text such as doctor's notes, clinical documents, and electronic health records. It extracts key data from sources like discharge summaries to support healthcare analysis.
> [!TIP]
-> Try out Text Analytics for health [in Microsoft Foundry portal](https://ai.azure.com/). There you can [utilize a currently existing Language Studio resource or create a new Foundry resource](../../../ai-services/connect-services-foundry-portal.md) in order to use this service.
+> Try out Text analytics for health [in Microsoft Foundry portal](https://ai.azure.com/). There you can [utilize a currently existing Language Studio resource or create a new Foundry resource](../../../ai-services/connect-services-foundry-portal.md) in order to use this service.
This documentation contains the following types of articles:
+
* The [**quickstart article**](quickstart.md) provides a short tutorial that guides you with making your first request to the service.
* The [**how-to guides**](how-to/call-api.md) contain detailed instructions on how to make calls to the service using the hosted API or using the on-premises Docker container.
* The [**conceptual articles**](concepts/health-entity-categories.md) provide in-depth information on each of the service's features, named entity recognition, relation extraction, entity linking, and assertion detection.
-## Text Analytics for health features
+## Text analytics for health features
-Text Analytics for health performs four key functions, all with a single API call:
+Text analytics for health performs four key functions, all with a single API call:
* Named entity recognition
* Relation extraction
* Entity linking
* Assertion detection
-[!INCLUDE [Text Analytics for health](includes/features.md)]
-
-Text Analytics for health can receive unstructured text in English, German, French, Italian, Spanish, Portuguese, and Hebrew.
-
-Additionally, Text Analytics for health can return the processed output using the Fast Healthcare Interoperability Resources (FHIR) structure that enables the service's integration with other electronic health systems.
+[!INCLUDE [Text analytics for health](includes/features.md)]
+Text analytics for health can receive unstructured text in English, German, French, Italian, Spanish, Portuguese, and Hebrew.
+Additionally, Text analytics for health can return the processed output using the Fast Healthcare Interoperability Resources (FHIR) structure that enables the service's integration with other electronic health systems.
> [!VIDEO https://learn.microsoft.com/Shows/AI-Show/Introducing-Text-Analytics-for-Health/player]
## Usage scenarios
-Text Analytics for health can be used in multiple scenarios across various industries.
-Some common customer motivations for using Text Analytics for health include:
+Text analytics for health can be used in multiple scenarios across various industries.
+Some common customer motivations for using Text analytics for health include:
+
* Assisting and automating the processing of medical documents by proper medical coding to ensure accurate care and billing.
* Increasing the efficiency of analyzing healthcare data to help drive the success of value-based care models similar to Medicare.
* Minimizing healthcare provider effort by automating the aggregation of key patient data for trend and pattern monitoring.
@@ -63,22 +64,20 @@ Some common customer motivations for using Text Analytics for health include:
|Review and report medical information|Potential medical information errors found during quality assurance reviews.|
|Assist with decision support|Enable solutions that provide humans with assistive information relating to patients' medical information for faster and more reliable decisions.|
-## Get started with Text Analytics for health
+## Get started with Text analytics for health
[!INCLUDE [Development options](./includes/development-options.md)]
-
## Input requirements and service limits
-Text Analytics for health is designed to receive unstructured text for analysis. For more information, see [data and service limits](../concepts/data-limits.md).
+Text analytics for health is designed to receive unstructured text for analysis. For more information, see [data and service limits](../concepts/data-limits.md).
-Text Analytics for health works with various input languages. For more information, see [language support](language-support.md).
+Text analytics for health works with various input languages. For more information, see [language support](language-support.md).
[!INCLUDE [Developer reference](../includes/reference-samples-text-analytics.md)]
-
## Responsible use of AI
-An AI system includes the technology, the individuals who operate the system, the people who experience its effects, and the broader environment where the system functions all play a role. Read the [transparency note for Text Analytics for health](/azure/ai-foundry/responsible-ai/language-service/transparency-note-health) to learn about responsible AI use and deployment in your systems.
+An AI system includes the technology, the individuals who operate the system, the people who experience its effects, and the broader environment where the system functions all play a role. Read the [transparency note for Text analytics for health](/azure/ai-foundry/responsible-ai/language-service/transparency-note-health) to learn about responsible AI use and deployment in your systems.
[!INCLUDE [Responsible AI links](../includes/overview-responsible-ai-links.md)]
Summary
{
"modification_type": "minor update",
"modification_title": "テキスト分析機能に関する文書の整理と更新"
}
Explanation
この変更は、Azure Language サービスにおける「テキスト分析 for health」に関するオーバービュー(overview.md)に対して行われた軽微な更新を示しています。主な変更点は以下の通りです。
タイトルが「What is the Text Analytics for health in Azure Language in Foundry Tools?」から「What is Text analytics for health in Azure Language?」に変更され、ブランド名が簡潔に表現されています。
最終更新日が2026年3月30日に変更され、文書が最新の情報を反映するようになりました。
文書の内容が整理され、「テキスト分析 for health」がAzure Languageの「コア機能」として明確に示され、機械学習を用いた医療情報の識別とラベリングの基本的な説明は維持されています。
「試してみてください」というセクションが、形を整えられた状態で維持され、ユーザーがMicrosoft Foundryポータルでこのサービスを試す方法に関するリンクが提供されています。
テキスト分析機能の機能セクションが整理され、最初にノミネートされた4つの機能が強調されています。また、言語のサポートや、FAST Healthcare Interoperability Resources(FHIR)構造に関する情報も更新されました。
一部のセクション見出しが小文字で書き換えられ、文書全体の統一感が向上しています。
AIの責任ある使用に関する情報が、リンクの統一感が保たれたまま維持され、利用者に対する注意喚起が強調されています。
これらの変更により、テキスト分析 for health の文書は、より整理された構造を持つとともに、重要な情報が明確にユーザーに提供されるようになっています。全体として、可読性と一貫性が向上し、利用者が情報を理解しやすくなっています。
articles/ai-services/language-service/toc.yml
Diff
@@ -25,12 +25,262 @@ items:
- name: Configure Azure resources
href: conversational-language-understanding/how-to/configure-azure-resources.md
displayName: configuration, fine-tuning, azure ai foundry, azure portal
- - name: Migrate to Microsoft Foundry
+ - name: Migrate to Microsoft Foundry
href: migration-studio-to-foundry.md
displayName: migrate, foundry, studio, permissions, roles, access, requisites, requirements
-- name: Azure Language in Foundry Tools capabilities
+- name: Core capabilities
items:
+ - name: Language detection
+ items:
+ - name: Overview
+ href: language-detection/overview.md
+ displayName: language detection, language identification, automatic detection
+ - name: Quickstart
+ href: language-detection/quickstart.md
+ - name: Language support
+ href: language-detection/language-support.md
+ - name: Responsible use of AI
+ items:
+ - name: Transparency note for language detection
+ href: ../../ai-foundry/responsible-ai/language-service/transparency-note-language-detection.md
+ displayName: Transparency note for language detection, language detection transparency, Responsible AI, Responsible use of AI
+ - name: Integration and responsible use
+ href: ../../ai-foundry/responsible-ai/language-service/guidance-integration-responsible-use.md
+ displayName: Responsible deployment, Responsible use, Responsible integration, AI deployment, AI use
+ - name: Data, privacy, and security
+ href: ../../ai-foundry/responsible-ai/language-service/data-privacy.md
+ displayName: Data privacy, logging, data retention
+ - name: How-to guides
+ items:
+ - name: Call the API
+ href: language-detection/how-to/call-api.md
+ - name: Use containers
+ items:
+ - name: Use Docker containers
+ href: language-detection/how-to/use-containers.md
+ - name: Configure containers
+ href: concepts/configure-containers.md
+ - name: Use container instances
+ href: ../containers/azure-container-instance-recipe.md?context=/azure/ai-services/language-service/context/context
+ - name: Use containers in disconnected environments
+ href: ../containers/disconnected-containers.md
+ - name: Azure AI containers overview
+ href: ../cognitive-services-container-support.md
+
+ - name: Named Entity Recognition
+ items:
+ - name: Custom named entity recognition (CNER)
+ items:
+ - name: Overview
+ href: custom-named-entity-recognition/overview.md
+ - name: Quickstart
+ href: custom-named-entity-recognition/quickstart.md
+ - name: Language support
+ href: custom-named-entity-recognition/language-support.md
+ - name: FAQ
+ href: custom-named-entity-recognition/faq.md
+ - name: Glossary
+ href: custom-named-entity-recognition/glossary.md
+ - name: How-to guides
+ items:
+ - name: Create projects
+ href: custom-named-entity-recognition/how-to/create-project.md
+ - name: Data selection and schema design
+ href: custom-named-entity-recognition/how-to/design-schema.md
+ - name: Label data
+ href: custom-named-entity-recognition/how-to/tag-data.md
+ - name: Auto label your data (preview)
+ href: custom-named-entity-recognition/how-to/use-autolabeling.md
+ - name: Label data with Azure Machine Learning
+ href: custom/azure-machine-learning-labeling.md
+ - name: Train a model
+ href: custom-named-entity-recognition/how-to/train-model.md
+ - name: Model performance (preview)
+ href: custom-named-entity-recognition/how-to/view-model-evaluation.md
+ - name: Deploy a model
+ href: custom-named-entity-recognition/how-to/deploy-model.md
+ - name: Extract entities from text
+ href: custom-named-entity-recognition/how-to/call-api.md
+ - name: Back up and recover your models
+ href: custom-named-entity-recognition/fail-over.md
+ - name: Use CNER containers
+ items:
+ - name: Use CNER Docker containers
+ href: custom-named-entity-recognition/how-to/use-containers.md
+ - name: Configure containers
+ href: concepts/configure-containers.md
+ - name: Use container instances
+ href: ../containers/azure-container-instance-recipe.md?context=/azure/ai-services/language-service/context/context
+ - name: Azure AI containers overview
+ href: ../cognitive-services-container-support.md
+ - name: Concepts
+ items:
+ - name: Evaluation metrics
+ href: custom-named-entity-recognition/concepts/evaluation-metrics.md
+ - name: Accepted data formats
+ href: custom-named-entity-recognition/concepts/data-formats.md
+ - name: Deploy to multiple regions
+ href: concepts/custom-features/multi-region-deployment.md
+ - name: Project versioning
+ href: concepts/custom-features/project-versioning.md
+
+ - name: Prebuilt named entity recognition (NER)
+ items:
+ - name: Overview
+ href: named-entity-recognition/overview.md
+ displayName: named entity recognition, introduction, entity extraction
+ - name: Quickstart
+ href: named-entity-recognition/quickstart.md
+ - name: Language support
+ href: named-entity-recognition/language-support.md
+ - name: Responsible use of AI
+ items:
+ - name: Transparency note for NER
+ href: ../../ai-foundry/responsible-ai/language-service/transparency-note-named-entity-recognition.md
+ displayName: Transparency note for NER, Named Entity Recognition transparency, Responsible AI, Responsible use of AI
+ - name: Integration and responsible use
+ href: ../../ai-foundry/responsible-ai/language-service/guidance-integration-responsible-use.md
+ displayName: Responsible deployment, Responsible use, Responsible integration, AI deployment, AI use
+ - name: Data, privacy, and security
+ href: ../../ai-foundry/responsible-ai/language-service/data-privacy.md
+ displayName: Data privacy, logging, data retention
+ - name: How-to guides
+ items:
+ - name: Call NER
+ href: named-entity-recognition/how-to-call.md
+ - name: Use skill parameters
+ href: named-entity-recognition/how-to/skill-parameters.md
+ - name: Use containers
+ items:
+ - name: Use Docker containers
+ href: named-entity-recognition/how-to/use-containers.md
+ - name: Configure containers
+ href: concepts/configure-containers.md
+ - name: Use container instances
+ href: ../containers/azure-container-instance-recipe.md?context=/azure/ai-services/language-service/context/context
+ - name: Use containers in disconnected environments
+ href: ../containers/disconnected-containers.md
+ - name: Azure AI containers overview
+ href: ../cognitive-services-container-support.md
+ - name: Concepts
+ items:
+ - name: Recognized entity categories
+ href: named-entity-recognition/concepts/named-entity-categories.md
+ - name: Entity Metadata
+ href: named-entity-recognition/concepts/entity-metadata.md
+ - name: API version mapping
+ href: named-entity-recognition/concepts/ga-preview-mapping.md
+ - name: Tutorials
+ items:
+ - name: Extract information in Excel using Power Automate
+ href: named-entity-recognition/tutorials/extract-excel-information.md
+ displayName: excel integration, power automate, ner automation, extract entities
+
+ - name: Personally identifiable information (PII) recognition
+ items:
+ - name: Overview
+ href: personally-identifiable-information/overview.md
+ displayName: personally identifiable information, document
+ - name: Quickstart
+ href: personally-identifiable-information/quickstart.md
+ - name: Language support
+ href: personally-identifiable-information/language-support.md
+ - name: Responsible use of AI
+ items:
+ - name: Transparency note for PII
+ href: ../../ai-foundry/responsible-ai/language-service/transparency-note-personally-identifiable-information.md
+ displayName: Transparency note for PII, Personally Identifiable Information transparency, Responsible AI, Responsible use of AI
+ - name: Integration and responsible use
+ href: ../../ai-foundry/responsible-ai/language-service/guidance-integration-responsible-use.md
+ displayName: Responsible deployment, Responsible use, Responsible integration, AI deployment, AI use
+ - name: Data, privacy, and security
+ href: ../../ai-foundry/responsible-ai/language-service/data-privacy.md
+ displayName: Data privacy, logging, data retention
+ - name: How-to guides
+ items:
+ - name: Redact PII from text
+ href: personally-identifiable-information/how-to/redact-text-pii.md
+ - name: Redact PII from conversations
+ href: personally-identifiable-information/how-to/redact-conversation-pii.md
+ - name: Redact PII from native documents
+ href: personally-identifiable-information/how-to/redact-document-pii.md
+ - name: Adapt PII to your domain
+ href: personally-identifiable-information/how-to/adapt-to-domain-pii.md
+ - name: Use Docker containers
+ items:
+ - name: Install and run containers
+ href: personally-identifiable-information/how-to/use-containers.md
+ - name: Configure containers
+ href: concepts/configure-containers.md
+ - name: Use container instances
+ href: ../containers/azure-container-instance-recipe.md?context=/azure/ai-services/language-service/context/context
+ - name: Use containers in disconnected environments
+ href: ../containers/disconnected-containers.md
+ - name: Azure AI containers overview
+ href: ../cognitive-services-container-support.md
+ - name: Recognized entity categories
+ items:
+ - name: PII in text
+ items:
+ - name: Extended format
+ href: personally-identifiable-information/concepts/entity-categories.md
+ - name: List format
+ href: personally-identifiable-information/concepts/entity-categories-list.md
+ - name: PII in conversations
+ items:
+ - name: Extended format
+ href: personally-identifiable-information/concepts/conversations-entity-categories.md
+ - name: List format
+ href: personally-identifiable-information/concepts/conversations-entities-list.md
+
+ - name: Text Analytics for health
+ items:
+ - name: Overview
+ href: text-analytics-for-health/overview.md
+ displayName: text analytics for health, healthcare nlp, medical text analysis, clinical text, health entities
+ - name: Quickstart
+ href: text-analytics-for-health/quickstart.md
+ - name: Language support
+ href: text-analytics-for-health/language-support.md
+ - name: Responsible use of AI
+ items:
+ - name: Transparency note for Text Analytics for health
+ href: ../../ai-foundry/responsible-ai/language-service/transparency-note-health.md
+ displayName: Transparency note for Text Analytics health, Text Analytics for health transparency, Responsible AI, Responsible use of AI
+ - name: Integration and responsible use
+ href: ../../ai-foundry/responsible-ai/language-service/guidance-integration-responsible-use.md
+ displayName: Responsible deployment, Responsible use, Responsible integration, AI deployment, AI use
+ - name: Data, privacy, and security
+ href: ../../ai-foundry/responsible-ai/language-service/data-privacy.md
+ displayName: Data privacy, logging, data retention
+ - name: How-to guides
+ items:
+ - name: How to call the API
+ href: text-analytics-for-health/how-to/call-api.md
+ - name: Use containers
+ items:
+ - name: Use Docker containers
+ href: text-analytics-for-health/how-to/use-containers.md
+ - name: Configure Docker containers
+ href: text-analytics-for-health/how-to/configure-containers.md
+ - name: Use container instances
+ href: ../containers/azure-container-instance-recipe.md?context=/azure/ai-services/language-service/context/context
+ - name: Azure AI containers overview
+ href: ../cognitive-services-container-support.md
+ - name: Concepts
+ items:
+ - name: Recognized entity categories
+ href: text-analytics-for-health/concepts/health-entity-categories.md
+ - name: Relation extraction
+ href: text-analytics-for-health/concepts/relation-extraction.md
+ - name: Assertion detection
+ href: text-analytics-for-health/concepts/assertion-detection.md
+ - name: Fast Healthcare Interoperability Resources structuring
+ href: text-analytics-for-health/concepts/fhir.md
+
+- name: Legacy capabilities
+ items:
- name: "Conversational language understanding (CLU)"
items:
- name: Overview
@@ -41,7 +291,7 @@ items:
- name: Get started
href: conversational-language-understanding/quickstart.md
displayName: getting started, tutorial, conversational ai setup
- - name: Try multi-turn conversations
+ - name: Try multi-turn conversations
href: conversational-language-understanding/how-to/quickstart-multi-turn-conversations.md
displayName: slot-filling, intent, entities, entity, association, foundry
- name: Language support
@@ -62,7 +312,7 @@ items:
href: /azure/ai-foundry/responsible-ai/clu/clu-data-privacy-security?context=/azure/ai-services/language-service/context/context
- name: How-to guides
items:
- - name: Build a multi-turn conversation model
+ - name: Build a multi-turn conversation model
href: conversational-language-understanding/how-to/build-multi-turn-model.md
displayName: slot-filling, intent, entities, entity, association, foundry
- name: Use containers
@@ -103,7 +353,7 @@ items:
displayName: disaster recovery, failover, clu
- name: Concepts
items:
- - name: Multi-turn conversations
+ - name: Multi-turn conversations
href: conversational-language-understanding/concepts/multi-turn-conversations.md
displayName: slot-filling, intent, entities, entity, association, foundry
- name: Best practices
@@ -141,7 +391,7 @@ items:
- name: Glossary
href: conversational-language-understanding/glossary.md
- - name: Custom question answering
+ - name: Custom question answering (CQA)
items:
- name: Overview
href: question-answering/overview.md
@@ -166,7 +416,7 @@ items:
- name: Create, test, and deploy a knowledge base
href: question-answering/how-to/create-test-deploy.md
displayName: knowledge base, test deploy
- - name: Deploy a CQA agent
+ - name: Deploy a CQA agent
href: question-answering/how-to/deploy-agent.md
displayName: virtual assistant, chatbot, knowledge base, deployment
- name: Export/import/refresh
@@ -339,42 +589,7 @@ items:
- name: How to call the API
href: entity-linking/how-to/call-api.md
displayName: entity linking, entity recognition
- - name: Language detection
- items:
- - name: Overview
- href: language-detection/overview.md
- displayName: language detection, language identification, automatic detection
- - name: Quickstart
- href: language-detection/quickstart.md
- - name: Language support
- href: language-detection/language-support.md
- - name: Responsible use of AI
- items:
- - name: Transparency note for language detection
- href: ../../ai-foundry/responsible-ai/language-service/transparency-note-language-detection.md
- displayName: Transparency note for language detection, language detection transparency, Responsible AI, Responsible use of AI
- - name: Integration and responsible use
- href: ../../ai-foundry/responsible-ai/language-service/guidance-integration-responsible-use.md
- displayName: Responsible deployment, Responsible use, Responsible integration, AI deployment, AI use
- - name: Data, privacy, and security
- href: ../../ai-foundry/responsible-ai/language-service/data-privacy.md
- displayName: Data privacy, logging, data retention
- - name: How-to guides
- items:
- - name: Call the API
- href: language-detection/how-to/call-api.md
- - name: Use containers
- items:
- - name: Use Docker containers
- href: language-detection/how-to/use-containers.md
- - name: Configure containers
- href: concepts/configure-containers.md
- - name: Use container instances
- href: ../containers/azure-container-instance-recipe.md?context=/azure/ai-services/language-service/context/context
- - name: Use containers in disconnected environments
- href: ../containers/disconnected-containers.md
- - name: Azure AI containers overview
- href: ../cognitive-services-container-support.md
+
- name: Key phrase extraction
items:
@@ -418,112 +633,7 @@ items:
href: key-phrase-extraction/tutorials/integrate-power-bi.md
displayName: business intelligence, data visualization
- - name: Named Entity Recognition (prebuilt)
- items:
- - name: Overview
- href: named-entity-recognition/overview.md
- displayName: named entity recognition, introduction, entity extraction
- - name: Quickstart
- href: named-entity-recognition/quickstart.md
- - name: Language support
- href: named-entity-recognition/language-support.md
- - name: Responsible use of AI
- items:
- - name: Transparency note for NER
- href: ../../ai-foundry/responsible-ai/language-service/transparency-note-named-entity-recognition.md
- displayName: Transparency note for NER, Named Entity Recognition transparency, Responsible AI, Responsible use of AI
- - name: Integration and responsible use
- href: ../../ai-foundry/responsible-ai/language-service/guidance-integration-responsible-use.md
- displayName: Responsible deployment, Responsible use, Responsible integration, AI deployment, AI use
- - name: Data, privacy, and security
- href: ../../ai-foundry/responsible-ai/language-service/data-privacy.md
- displayName: Data privacy, logging, data retention
- - name: How-to guides
- items:
- - name: Call NER
- href: named-entity-recognition/how-to-call.md
- - name: Use skill parameters
- href: named-entity-recognition/how-to/skill-parameters.md
- - name: Use containers
- items:
- - name: Use Docker containers
- href: named-entity-recognition/how-to/use-containers.md
- - name: Configure containers
- href: concepts/configure-containers.md
- - name: Use container instances
- href: ../containers/azure-container-instance-recipe.md?context=/azure/ai-services/language-service/context/context
- - name: Use containers in disconnected environments
- href: ../containers/disconnected-containers.md
- - name: Azure AI containers overview
- href: ../cognitive-services-container-support.md
- - name: Concepts
- items:
- - name: Recognized entity categories
- href: named-entity-recognition/concepts/named-entity-categories.md
- - name: Entity Metadata
- href: named-entity-recognition/concepts/entity-metadata.md
- - name: API version mapping
- href: named-entity-recognition/concepts/ga-preview-mapping.md
- - name: Tutorials
- items:
- - name: Extract information in Excel using Power Automate
- href: named-entity-recognition/tutorials/extract-excel-information.md
- displayName: excel integration, power automate, ner automation, extract entities
- - name: Named Entity Recognition (custom)
- items:
- - name: Overview
- href: custom-named-entity-recognition/overview.md
- - name: Quickstart
- href: custom-named-entity-recognition/quickstart.md
- - name: Language support
- href: custom-named-entity-recognition/language-support.md
- - name: FAQ
- href: custom-named-entity-recognition/faq.md
- - name: Glossary
- href: custom-named-entity-recognition/glossary.md
- - name: How-to guides
- items:
- - name: Create projects
- href: custom-named-entity-recognition/how-to/create-project.md
- - name: Data selection and schema design
- href: custom-named-entity-recognition/how-to/design-schema.md
- - name: Label data
- href: custom-named-entity-recognition/how-to/tag-data.md
- - name: Auto label your data (preview)
- href: custom-named-entity-recognition/how-to/use-autolabeling.md
- - name: Label data with Azure Machine Learning
- href: custom/azure-machine-learning-labeling.md
- - name: Train a model
- href: custom-named-entity-recognition/how-to/train-model.md
- - name: Model performance (preview)
- href: custom-named-entity-recognition/how-to/view-model-evaluation.md
- - name: Deploy a model
- href: custom-named-entity-recognition/how-to/deploy-model.md
- - name: Extract entities from text
- href: custom-named-entity-recognition/how-to/call-api.md
- - name: Back up and recover your models
- href: custom-named-entity-recognition/fail-over.md
- - name: Use Custom NER containers
- items:
- - name: Use Custom NER Docker containers
- href: custom-named-entity-recognition/how-to/use-containers.md
- - name: Configure containers
- href: concepts/configure-containers.md
- - name: Use container instances
- href: ../containers/azure-container-instance-recipe.md?context=/azure/ai-services/language-service/context/context
- - name: Azure AI containers overview
- href: ../cognitive-services-container-support.md
- - name: Concepts
- items:
- - name: Evaluation metrics
- href: custom-named-entity-recognition/concepts/evaluation-metrics.md
- - name: Accepted data formats
- href: custom-named-entity-recognition/concepts/data-formats.md
- - name: Deploy to multiple regions
- href: concepts/custom-features/multi-region-deployment.md
- - name: Project versioning
- href: concepts/custom-features/project-versioning.md
- name: Orchestration workflow
items:
@@ -582,70 +692,15 @@ items:
- name: Glossary
href: orchestration-workflow/glossary.md
- - name: Personally Identifiable Information detection
- items:
- - name: Overview
- href: personally-identifiable-information/overview.md
- displayName: personally identifiable information, document
- - name: Quickstart
- href: personally-identifiable-information/quickstart.md
- - name: Language support
- href: personally-identifiable-information/language-support.md
- - name: Responsible use of AI
- items:
- - name: Transparency note for PII
- href: ../../ai-foundry/responsible-ai/language-service/transparency-note-personally-identifiable-information.md
- displayName: Transparency note for PII, Personally Identifiable Information transparency, Responsible AI, Responsible use of AI
- - name: Integration and responsible use
- href: ../../ai-foundry/responsible-ai/language-service/guidance-integration-responsible-use.md
- displayName: Responsible deployment, Responsible use, Responsible integration, AI deployment, AI use
- - name: Data, privacy, and security
- href: ../../ai-foundry/responsible-ai/language-service/data-privacy.md
- displayName: Data privacy, logging, data retention
- - name: How-to guides
- items:
- - name: Redact PII from text
- href: personally-identifiable-information/how-to/redact-text-pii.md
- - name: Redact PII from conversations
- href: personally-identifiable-information/how-to/redact-conversation-pii.md
- - name: Redact PII from native documents
- href: personally-identifiable-information/how-to/redact-document-pii.md
- - name: Adapt PII to your domain
- href: personally-identifiable-information/how-to/adapt-to-domain-pii.md
- - name: Use Docker containers
- items:
- - name: Install and run containers
- href: personally-identifiable-information/how-to/use-containers.md
- - name: Configure containers
- href: concepts/configure-containers.md
- - name: Use container instances
- href: ../containers/azure-container-instance-recipe.md?context=/azure/ai-services/language-service/context/context
- - name: Use containers in disconnected environments
- href: ../containers/disconnected-containers.md
- - name: Azure AI containers overview
- href: ../cognitive-services-container-support.md
- - name: Recognized entity categories
- items:
- - name: PII in text
- items:
- - name: Extended format
- href: personally-identifiable-information/concepts/entity-categories.md
- - name: List format
- href: personally-identifiable-information/concepts/entity-categories-list.md
- - name: PII in conversations
- items:
- - name: Extended format
- href: personally-identifiable-information/concepts/conversations-entity-categories.md
- - name: List format
- href: personally-identifiable-information/concepts/conversations-entities-list.md
+
- name: Sentiment analysis and opinion mining
items:
- name: Overview
href: sentiment-opinion-mining/overview.md
displayName: sentiment analysis introduction, opinion mining overview, sentiment detection
- name: Quickstart
href: sentiment-opinion-mining/quickstart.md
- - name: language-detection/how-to/use-containers.mdanguage support
+ - name: Language support
href: sentiment-opinion-mining/language-support.md
- name: Responsible use of AI
items:
@@ -723,57 +778,14 @@ items:
href: ../../ai-foundry/responsible-ai/language-service/data-privacy.md
displayName: Data privacy, logging, data retention
- - name: Text Analytics for health
- items:
- - name: Overview
- href: text-analytics-for-health/overview.md
- displayName: text analytics for health, healthcare nlp, medical text analysis, clinical text, health entities
- - name: Quickstart
- href: text-analytics-for-health/quickstart.md
- - name: Language support
- href: text-analytics-for-health/language-support.md
- - name: Responsible use of AI
- items:
- - name: Transparency note for Text Analytics for health
- href: ../../ai-foundry/responsible-ai/language-service/transparency-note-health.md
- displayName: Transparency note for Text Analytics health, Text Analytics for health transparency, Responsible AI, Responsible use of AI
- - name: Integration and responsible use
- href: ../../ai-foundry/responsible-ai/language-service/guidance-integration-responsible-use.md
- displayName: Responsible deployment, Responsible use, Responsible integration, AI deployment, AI use
- - name: Data, privacy, and security
- href: ../../ai-foundry/responsible-ai/language-service/data-privacy.md
- displayName: Data privacy, logging, data retention
- - name: How-to guides
- items:
- - name: How to call the API
- href: text-analytics-for-health/how-to/call-api.md
- - name: Use containers
- items:
- - name: Use Docker containers
- href: text-analytics-for-health/how-to/use-containers.md
- - name: Configure Docker containers
- href: text-analytics-for-health/how-to/configure-containers.md
- - name: Use container instances
- href: ../containers/azure-container-instance-recipe.md?context=/azure/ai-services/language-service/context/context
- - name: Azure AI containers overview
- href: ../cognitive-services-container-support.md
- - name: Concepts
- items:
- - name: Recognized entity categories
- href: text-analytics-for-health/concepts/health-entity-categories.md
- - name: Relation extraction
- href: text-analytics-for-health/concepts/relation-extraction.md
- - name: Assertion detection
- href: text-analytics-for-health/concepts/assertion-detection.md
- - name: Fast Healthcare Interoperability Resources structuring
- href: text-analytics-for-health/concepts/fhir.md
+
- name: Concepts
items:
- name: Developer guide
href: concepts/developer-guide.md
displayName: development, sdk guide, programming
- - name: Azure tools and agents
+ - name: Azure tools and agents
href: concepts/foundry-tools-agents.md
displayName: mcp, exact, question, answering, intent, routing
- name: Role-based-access-control
Summary
{
"modification_type": "minor update",
"modification_title": "言語サービスの目次更新と整理"
}
Explanation
この変更は、Azure AIサービスに関する目次ファイル(toc.yml)に対する軽微な更新を示しています。変更の内容は大きく次のように整理されています。
新しいセクションやサブセクションが追加され、特にテキスト分析や言語検出機能に関する詳細なリストが整備されました。これにより、利用者が目的の情報にすぐにアクセスできるようにナビゲーションが改善されています。
「テキスト分析 for health」や「個人識別情報(PII)認識」などの新しい機能が明示され、それぞれに関連するリソースが含まれています。これにより、特定のニーズに基づいて文書を探しやすくなっています。
各セクションのタイトルが明確に指定されたことで、一貫した表現が保たれ、利用者が情報を見つけやすくなりました。
一部の古いセクションが削除され、新しい機能や役割が強調されています。この更新により、情報がより現行のサービスや機能反映されています。
文書が整理され、各項目に対する短い説明やリソースのリンクも更新されており、利用者が必要な情報を速やかに得られるように工夫されています。
全体として、この変更により、Azure AIサービスの目次がすっきりと整理され、特に新機能や重要なガイドラインに関するアクセスが容易になり、ユーザーエクスペリエンスの向上に寄与しています。