@@ -6,14 +6,17 @@ author: laujan
 manager: nitinme
 ms.service: azure-ai-document-intelligence
 ms.topic: overview
-ms.date: 11/18/2025
+ms.date: 06/02/2026
 ms.author: lajanuar
+ai-usage: ai-assisted
 ---
-
+<!-- markdownlint-disable MD025 -->
 
 # Which model should I choose?
 
-Azure Document Intelligence in Foundry Tools supports a wide variety of models that enable you to add intelligent document processing to your applications and optimize your workflows. Selecting the right model is essential to ensure the success of your enterprise. In this article, we explore the available Document Intelligence models and provide guidance for how to choose the best solution for your projects.
+Azure Document Intelligence in Foundry Tools supports a wide variety of models that enable you to add intelligent document processing to your applications and optimize your workflows. Choosing the right model is essential to the success of your enterprise solution. This article explores the available Document Intelligence models—and how they complement Azure Content Understanding capabilities—to help you select the best approach for your projects.
+
+As part of Azure Content Understanding capabilities, Azure Document Intelligence provides high-accuracy and reliable deterministic extraction from structured documents. Content Understanding also offers LLM-powered analyzers for complex, unstructured, and multimodal content. Together, they make it easier to prepare data for intelligent agents and applications that can read, analyze, and respond to real-world content with precision and speed. To compare both services and determine which best fits your scenario, see [Choose the right Azure AI tool for document processing](../../content-understanding/choosing-right-ai-tool.md).
 
 > [!VIDEO 364078d4-14bc-4b16-995a-526db31ea1ee]
 
@@ -22,13 +25,31 @@ The following decision charts highlight the features of each supported model to
 > [!IMPORTANT]
 > Be sure to check the [**language support**](../language-support/prebuilt.md) page for supported language text and field extraction  by feature.
 
+## Compare Document Intelligence and Content Understanding
+
+Use the following table to determine which service best fits your scenario before selecting a specific Document Intelligence model.
+
+| | Azure Document Intelligence | Azure Content Understanding |
+|---|---|---|
+| **Best for** | High-volume, deterministic extraction from structured and semi-structured documents | Complex, varied, unstructured, or multimodal content processing |
+| **Document types** | Standardized forms, invoices, tax forms, IDs, and receipts | Highly varied templates, unstructured documents, images, audio, and video |
+| **Labeling** | Required for custom models (minimum five labeled samples) | No labeling required to start; label to improve |
+| **Extraction** | Deterministic field extraction with confidence scores and grounding | Extractive and inferred fields, generated metadata, and enrichments |
+| **Generative AI** | No | Yes — inferred fields, reasoning, and post-processing |
+| **Multimodal input** | Documents only | Documents, images, audio, and video |
+| **Latency** | Low | Medium |
+| **Prebuilt coverage** | 20+ models (invoices, tax, IDs, mortgage, and more) | Prebuilt analyzers for common document types |
+| **Multi-file input** | No | Yes (preview) |
+
+If your scenario requires generative AI, multimodal input, or highly varied document templates, see [Choose the right Azure AI tool for document processing](../../content-understanding/choosing-right-ai-tool.md) for full scenario guidance. Otherwise, continue below to select the Document Intelligence model that best fits your structured document processing needs.
+
 ## Pretrained document-analysis models
 
 | Document type | Example| Data to extract | Your best solution |
 | -----------------|-----------|--------|-------------------|
 |**A generic document**. | A contract or letter. |You want to primarily extract written or printed text lines, words, locations, and detected languages.|[**Read OCR model**](../prebuilt/read.md)|
 |**A document that includes structural information**. |A report or study.| In addition to written or printed text, you need to extract structural information like tables, selection marks, paragraphs, titles, headings, and subheadings.| [**Layout analysis model**](../prebuilt/layout.md)|
-|**A structured or semi-structured document that includes content formatted as fields (keys) and values**.|A form or document that is a standardized format commonly used in your business or industry like a credit application or survey. | You want to extract fields and values including ones not covered by the scenario-specific prebuilt models **without having to train a custom model**.| [**Layout analysis model with the optional query string parameter `features=keyValuePairs` enabled **](../prebuilt/layout.md)|
+|**A structured or semi-structured document that includes content formatted as fields (keys) and values**.|A form or document that is a standardized format commonly used in your business or industry like a credit application or survey. | You want to extract fields and values including ones not covered by the scenario-specific prebuilt models **without having to train a custom model**.| [**Layout analysis model with the optional query string parameter `features=keyValuePairs` enabled**](../prebuilt/layout.md)|
 
 ## Pretrained scenario-specific models
 

@@ -6,7 +6,7 @@ author: laujan
 manager: nitinme
 ms.service: azure-ai-document-intelligence
 ms.topic: overview
-ms.date: 05/06/2026
+ms.date: 06/02/2026
 ms.author: lajanuar
 monikerRange: '<=doc-intel-4.0.0'
 ---
@@ -40,6 +40,8 @@ monikerRange: '<=doc-intel-4.0.0'
 
 :::moniker-end
 
+Azure Document Intelligence in Foundry Tools is a cloud-based [Foundry Tools](../../ai-services/index.yml) service that you can use to build intelligent document processing solutions. Massive amounts of data, spanning various data types, are stored in forms and documents. You can use Azure Document Intelligence to effectively manage the speed at which data is collected and processed. Azure Document Intelligence is key to improved operations, informed data-driven decisions, and enlightened innovation. For information on region access, see [Product availability by region](https://azure.microsoft.com/explore/global-infrastructure/products-by-region/table).</br></br>
+
 > [!IMPORTANT]
 >
 > * **Document Intelligence REST API v2.1** reaches end of support on **September 15, 2027**.
@@ -50,6 +52,13 @@ Azure Document Intelligence in Foundry Tools is a cloud-based [Foundry Tools](..
 
 | ✔️ [Document analysis models](#document-analysis-models) | ✔️ [Prebuilt models](#prebuilt-models) | ✔️ [Custom models](#custom-model-overview) |
 
+> [!NOTE]
+>
+> * As part of Azure Content Understanding capabilities, Azure Document Intelligence provides high-accuracy and reliable deterministic extraction from structured documents.
+> * Content Understanding also offers LLM-powered analyzers for complex, unstructured, and multimodal content.
+> * Together, they make it easier to prepare data for intelligent agents and applications that can read, analyze, and respond to real-world content with precision and speed.
+> * To compare both services and determine which best fits your scenario, see [Choose the right Azure AI tool for document processing](../content-understanding/choosing-right-ai-tool.md).
+
 ## Document analysis models
 
 Document analysis (general extraction) models enable text extraction from forms and documents and return structured business-ready content for your organization's action, use, or development.
@@ -66,7 +75,7 @@ Document analysis (general extraction) models enable text extraction from forms
    :::row-end:::
 
 :::moniker-end
- 
+
 :::moniker range="<=doc-intel-3.1.0"
 
  :::row:::

@@ -4,7 +4,7 @@ titleSuffix: Foundry Tools
 description: Release notes and updates for Azure Document Intelligence in Foundry Tools API.
 author: laujan
 manager: nitinme
-ms.service: azure-ai-document-intelligence
+ms.service: azure-document-intelligence-foundry-tools
 ms.topic: reference
 ms.date: 11/18/2025
 ms.author: lajanuar
@@ -30,7 +30,6 @@ Azure Document Intelligence is an innovative a cloud-based service that utilizes
 The Document Intelligence version 3.1 API is now generally available (GA)! The API version corresponds to ```2023-07-31```.
 The v3.1 API introduces new and updated capabilities:
 
-* Document Intelligence APIs are now more modular and with support for optional features. You can now customize the output to specifically include the features you need. Learn more about the [optional parameters](../versioning/v3-1-migration-guide.md).
 * Document classification API for splitting a single file into individual documents. [Learn more](../train/custom-classifier.md) about document classification.
 * [Prebuilt contract model](../prebuilt/contract.md).
 * [Prebuilt US tax form 1098 model](../prebuilt/tax-document.md).

@@ -5,7 +5,7 @@ ms.service: azure-ai-language
 ms.topic: how-to
 author: laujan
 ms.author: lajanuar
-ms.date: 11/18/2025
+ms.date: 06/02/2026
 ms.custom: language-service-question-answering
 ---
 # Configure your environment for Azure AI resources and permissions
@@ -25,7 +25,7 @@ In addition, we show you how to assign the correct roles and permissions within
 Before you can set up your resources, you need:
 
 * **An active Azure subscription**. If you don't have one, you can [create one for free](https://azure.microsoft.com/pricing/purchase-options/azure-account?cid=msft_learn).
-* **Requisite permissions**. Make sure the person establishing the account and project is assigned as the Foundry Account Owner role at the subscription level. Alternatively, having either the **Contributor** or **Cognitive Services Contributor** role at the subscription scope also meets this requirement. For more information, *see* [Role based access control (RBAC)](/azure/ai-foundry/openai/how-to/role-based-access-control#cognitive-services-contributor).
+* **Requisite permissions**. Make sure the person establishing the account and project is assigned as the         **Foundry Account Owner** role at the subscription level. Alternatively, having either the **Contributor** or **Cognitive Services Contributor** role at the subscription scope also meets this requirement. For more information, *see* [Role based access control (RBAC)](/azure/ai-foundry/openai/how-to/role-based-access-control#cognitive-services-contributor).
 
   [!INCLUDE [role-rename-note](../../../foundry/includes/role-rename-note.md)]
 * A [Foundry resource](/azure/ai-services/multi-service-resource) or an [Azure Language resource](https://portal.azure.com/?Microsoft_Azure_PIMCommon=true#create/Microsoft.CognitiveServicesTextAnalytics).

@@ -3,7 +3,7 @@ author: laujan
 manager: nitinme
 ms.service: azure-ai-language
 ms.topic: include
-ms.date: 02/06/2026
+ms.date: 06/02/2026
 ms.author: lajanuar
 ai-usage: ai-assisted
 ---
@@ -24,6 +24,7 @@ ai-usage: ai-assisted
 You can use [Foundry (classic)](https://ai.azure.com/) to:
 
 > [!div class="checklist"]
+>
 > * Detect the language of input text
 > * Review confidence scores and ISO language codes
 > * Configure country/region hints for improved accuracy
@@ -72,27 +73,28 @@ After the operation completes, the **Details** section displays the following fi
 
 Verify that the detected language matches the language of your input text. If the result shows `unknown`, provide a longer text sample or set a **Country/region hint** for better accuracy.
 
-### [Foundry (new)](#tab/foundry-new)
+### [New Foundry](#tab/new-foundry)
 
 > [!NOTE]
-> This content refers to the [Foundry (new)](https://ai.azure.com/) portal, which supports only Foundry projects and provides streamlined access to models, agents, and tools. For more information, see [What is Microsoft Foundry?](../../../../../ai-foundry/what-is-foundry.md). To confirm that you're using Foundry (new), make sure the version toggle in the portal banner is in the **on** position. :::image type="icon" source="../../media/quickstarts/azure-ai-foundry/new-foundry.png" border="false":::
+> This content refers to the [new Foundry](https://ai.azure.com/) portal, which supports only Foundry projects and provides streamlined access to models, agents, and tools. For more information, see [What is Microsoft Foundry?](../../../../../ai-foundry/what-is-foundry.md). To confirm that you're using new Foundry, make sure the version toggle in the portal banner is in the **on** position. :::image type="icon" source="../../media/quickstarts/azure-ai-foundry/new-foundry.png" border="false":::
 
-You can use [Foundry (new)](https://ai.azure.com/) to:
+You can use [new Foundry](https://ai.azure.com/) to:
 
 > [!div class="checklist"]
+>
 > * Detect the language of input text
 > * Review confidence scores and ISO language codes
 > * Configure country/region hints for improved accuracy
 
-## Navigate to the Foundry (new) playground
+## Navigate to the new Foundry playground
 
 The active project appears in the upper-left corner. To create a new project:
 
 1. Open the project drop-down menu.
 1. Enter a project name or select an existing one.
 1. Select **Create project**.
 
-   :::image type="content" source="../../../media/new-foundry-homepage.png" alt-text="Screenshot of the Foundry (new) homepage":::
+   :::image type="content" source="../../../media/new-foundry-homepage.png" alt-text="Screenshot of the new Foundry homepage":::
 
 There are two ways to access the Language Detection interface:
 
@@ -129,4 +131,20 @@ After you make your selections, choose the **Detect** button. Then review the te
   |**Detected script**| The name of the detected script in the text.|
   |**Detected script code**| The ISO 15924 script code for the detected script (writing system).|
 
-Verify that the detected language matches the language of your input text. You can use the **Edit** button to modify the **Configure** parameters and rerun detection as needed.
\ No newline at end of file
+Verify that the detected language matches the language of your input text. You can use the **Edit** button to modify the **Configure** parameters and rerun detection as needed.
+
+## Open in Visual Studio Code 🆕
+
+After validating your scenario in the playground, select **Open in VS Code** to carry your current configuration directly into a development environment—no manual setup required.
+
+1. Configure your scenario in the playground:
+   - Select your API version and model version.
+   - Enter and test your sample input.
+   - Adjust options such as API version, model version, and country/region hint.
+1. Select **Open in VS Code**.
+1. Visual Studio Code opens with a preconfigured code sample that reflects your playground configuration, including your API version, model, and language detection settings.
+
+> [!TIP]
+> Use the playground to compare outputs across API versions—for example, preview versus GA—before exporting your configuration to code.
+
+---
\ No newline at end of file

@@ -6,7 +6,7 @@ author: laujan
 manager: nitinme
 ms.service: azure-ai-language
 ms.topic: concept-article
-ms.date: 02/17/2026
+ms.date: 06/02/2026
 ms.author: lajanuar
 ---
 
@@ -20,14 +20,17 @@ The API categorizes personal details into predefined entity types for precise id
 > [!TIP]
 > Try PII detection in text or conversations using the [Microsoft Foundry](https://ai.azure.com/explore/language) language playground.
 
-### Language Support
+## Language Support
 
 The [PII language support page](../language-support.md) lists all languages available for the PII entities in this article. Any exceptions are noted for specific named entities.
 
-Supported API versions:
+## Supported API versions:
 
-* [**Stable 2024-11-01: Generally Available (GA)**](/rest/api/language/analyze-conversations/operation-groups?view=rest-language-analyze-conversations-2024-11-01&preserve-view=true)
-* [**Preview: 2025-11-15-preview**](/rest/api/language/analyze-conversations/operation-groups?view=rest-language-analyze-conversations-2025-11-15-preview&preserve-view=true)
+* [Stable: **2024-11-01 (GA)**](/rest/api/language/analyze-conversations/operation-groups?view=rest-language-analyze-conversations-2024-11-01&preserve-view=true)
+* [Preview: **2025-11-15-preview**](/rest/api/language/analyze-conversations/operation-groups?view=rest-language-analyze-conversations-2025-11-15-preview&preserve-view=true)
+
+> [!IMPORTANT]
+> **Conversation PII API** (2025-11-15-preview) and **Conversation PII model** (2026-04-15-preview) are licensed to you as part of your Azure subscription and are subject to terms applicable  terms for "Previews" in the [Microsoft Product Terms](https://www.microsoft.com/licensing/terms/welcome/welcomepage) 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), as well as the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms).
 
 The following entities are currently in preview:
 

@@ -6,53 +6,55 @@ author: laujan
 manager: nitinme
 ms.service: azure-ai-language
 ms.topic: concept-article
-ms.date: 11/18/2025
+ms.date: 06/02/2026
 ms.author: lajanuar
 ms.custom:
   - language-service-pii
   - sfi-ropc-nochange
 ---
+<!-- markdownlint-disable MD025 -->
 # Recognized **PII** and **PHI** entities
 
 The Personally Identifiable Information (PII) and Protected Health Information (PHI) detection APIs are cloud-based solutions that use artificial intelligence (AI) and machine learning to help you create smart applications with advanced natural language processing. The **PII** and **PHI** APIs effectively detect and removes sensitive information from input data by categorizing personal details into specific, predefined entity types. This comprehensive approach not only safeguards sensitive data to ensure full compliance with privacy regulations, but also enables applications to process and utilize information with enhanced security, reliability, and efficiency.
 
 > [!TIP]
 > Try PII detection in text or conversations using the [Microsoft Foundry](https://ai.azure.com/explore/language) language playground.
 
-### Language Support
+## Language Support
 
 The [PII language support page](../language-support.md) lists all languages available for the PII entities in this article. Any exceptions are noted for specific named entities.
 
-Supported API versions:
+## Supported API versions:
 
-* [**Stable 2025-11-01: Generally Available (GA)**](/rest/api/language/analyze-text/analyze-text/analyze-text?view=rest-language-analyze-text-2025-11-01&preserve-view=true&tabs=HTTP)
-* [**Preview: 2025-11-15-preview**](/rest/api/language/analyze-text/analyze-text/analyze-text?view=rest-language-analyze-text-2025-11-15-preview&preserve-view=true&tabs=HTTP). 
+* [Stable: **2026-05-01 (GA)**](/rest/api/language/analyze-text/analyze-text/analyze-text?view=rest-language-analyze-text-2025-11-01&preserve-view=true&tabs=HTTP)
+* [Preview: **2026-05-15-preview**](/rest/api/language/analyze-text/analyze-text/analyze-text?view=rest-language-analyze-text-2025-11-15-preview&preserve-view=true&tabs=HTTP).
 
-The following entities are currently in preview:
+   > [!IMPORTANT]
+   > **Text PII API** (2026-05-15-preview) is licensed to you as part of your Azure subscription and is subject to terms applicable to "Previews" in the [Microsoft Product Terms](https://www.microsoft.com/licensing/terms/welcome/welcomepage) 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), as well as the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms).
 
 The following entities are currently in preview:
 
-  * [Airport](#type-airport-preview)
-  * [DateOfBirth](#type-date-of-birth-preview)
-  * [BankAccountNumber](#type-bank-account-number-preview)
-  * [CASocialIdentificationNumber](#type-canada-social-identification-number-preview)
-  * [CVV (Card Verification Value )](#type-card-verification-value-cvv-preview)
-  * [City](#type-city-preview)
-  * [PassportNumber](#type-passport-number-preview)
-  * [DriversLicenseNumber](#type-drivers-license-number-preview)
-  * [ExpirationDate](#type-expiration-date-preview)
-  * [Geopolitical Entity](#type-geopolitical-entity-gpe-preview)
-  * [KRDriversLicenseNumber](#type-south-korea-drivers-license-number-preview)
-  * [KRPassportNumber ](#type-south-korea-passport-number-preview)
-  * [KRSocialSecurityNumber ](#type-south-korea-social-security-number-preview)
-  * [LicensePlate](#type-license-plate-preview)
-  * [Location](#type-location-preview)
-  * [Password](#type-password-preview)
-  * [SortCode](#type-sort-code-preview)
-  * [State](#type-state-preview)
-  * [USMedicareBeneficiaryId](#type-united-states-medicare-beneficiary-identification-preview)
-  * [VIN (vehicle identification number)](#type-vin-preview)
-  * [ZipCode](#type-zipcode-preview)
+* [Airport](#type-airport-preview)
+* [DateOfBirth](#type-date-of-birth-preview)
+* [BankAccountNumber](#type-bank-account-number-preview)
+* [CASocialIdentificationNumber](#type-canada-social-identification-number-preview)
+* [CVV (Card Verification Value )](#type-card-verification-value-cvv-preview)
+* [City](#type-city-preview)
+* [PassportNumber](#type-passport-number-preview)
+* [DriversLicenseNumber](#type-drivers-license-number-preview)
+* [ExpirationDate](#type-expiration-date-preview)
+* [Geopolitical Entity](#type-geopolitical-entity-gpe-preview)
+* [KRDriversLicenseNumber](#type-south-korea-drivers-license-number-preview)
+* [KRPassportNumber ](#type-south-korea-passport-number-preview)
+* [KRSocialSecurityNumber ](#type-south-korea-social-security-number-preview)
+* [LicensePlate](#type-license-plate-preview)
+* [Location](#type-location-preview)
+* [Password](#type-password-preview)
+* [SortCode](#type-sort-code-preview)
+* [State](#type-state-preview)
+* [USMedicareBeneficiaryId](#type-united-states-medicare-beneficiary-identification-preview)
+* [VIN (vehicle identification number)](#type-vin-preview)
+* [ZipCode](#type-zipcode-preview)
 
 > [!NOTE]
 > Beginning with the GA API (released `2024-11-01`), the **Subtype** field is no longer supported. All entity classifications now use the **type** field.
@@ -188,7 +190,7 @@ Any data, collected or stored, that can be used to identify or contact a specifi
 
 ## Financial
 
-Any financial information is connected to a particular individual that can, through identifying details, be traced back to that person. 
+Any financial information is connected to a particular individual that can, through identifying details, be traced back to that person.
 
 
 ### Type: American Bankers Association Routing Number
@@ -197,7 +199,7 @@ Any financial information is connected to a particular individual that can, thro
 |---|---|
 |To retrieve this entity type, specify **ABARoutingNumber** in the **piiCategories** request parameter. If detected, the entity appears in the **PII** response payload.|[**ABARoutingNumber**]|
 
-### Type: Bank Account Number (preview) 
+### Type: Bank Account Number (preview)
 
 |Details|Tag|
 |---|---|
@@ -229,7 +231,7 @@ Any financial information is connected to a particular individual that can, thro
 
 ## Organization
 
-Any data that an organization collects, stores, or processes that can be used to identify a specific individual, either directly or indirectly. 
+Any data that an organization collects, stores, or processes that can be used to identify a specific individual, either directly or indirectly.
 
 ### Type: Organization
 
@@ -1201,7 +1203,6 @@ Any government-issued identification that can be used along or combined with oth
 |---|---|
 |To retrieve this entity type, specify **ZipCode** in the **piiCategories** request parameter. If detected, the entity appears in the **PII** response payload.|[**USUKPassportNumber**]|
 
-
 ## Related content
 
 [PII entity categories list](entity-categories-list.md)

@@ -6,7 +6,7 @@ author: laujan
 manager: nitinme
 ms.service: azure-ai-language
 ms.topic: overview
-ms.date: 04/16/2026
+ms.date: 06/02/2026
 ms.author: lajanuar
 ms.custom: language-service-pii
 ---
@@ -18,6 +18,9 @@ Conversation PII redaction in Azure AI Language helps you detect and redact sens
 
 Conversation PII is optimized for asynchronous conversation jobs and conversation-level context, so you can redact sensitive data across multiple speakers and turns.
 
+> [!IMPORTANT]
+> **Conversation PII API** (2026-11-15-preview) and **Conversation PII model** (2026-04-15-preview) are licensed to you as part part of your Azure subscrition and are subject to terms applicable to "Previews" in the [Microsoft Product Terms](https://www.microsoft.com/licensing/terms/welcome/welcomepage) 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), as well as the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms).
+
 ## At a glance
 
 Conversation PII provides the following capabilities:

@@ -0,0 +1,138 @@
+---
+title: Use the conversation PII playground in Microsoft Foundry
+FoundrytitleSuffix: Azure AI Language
+description: Test conversation PII detection and redaction interactively in the Azure AI Foundry playground without writing code.
+author: laujan
+manager: nitinme
+ms.service: azure-ai-language
+ms.topic: quickstart
+ms.date: 05/18/2026
+ms.author: lajanuar
+ms.custom: language-service-pii
+---
+
+<!-- markdownlint-disable MD025 -->
+# Use the conversation PII playground in Microsoft Foundry
+
+> [!NOTE]
+> This content refers to the [new Foundry](https://ai.azure.com/) portal, which supports only [Foundry projects](../../../ai-foundry/what-is-foundry.md) and provides streamlined access to models, agents, and tools. To confirm that you're using new Foundry, make sure the version toggle in the portal banner is in the **on** position. :::image type="icon" source="media/quickstarts/azure-ai-foundry/new-foundry.png" border="false":::
+
+The conversation PII playground in Azure AI Foundry lets you detect and redact personally identifiable information (PII) in conversational text interactively, without writing code. You can submit transcript-style input, configure redaction options, and review detected entities before integrating the feature into your application.
+
+* [Stable: **2024-11-01 (GA)**](/rest/api/language/analyze-conversations/operation-groups?view=rest-language-analyze-conversations-2024-11-01&preserve-view=true)
+* [Preview: **2025-11-15-preview**](/rest/api/language/analyze-conversations/operation-groups?view=rest-language-analyze-conversations-2025-11-15-preview&preserve-view=true)
+
+> [!IMPORTANT]
+> **Conversation PII API** (2025-11-15-preview) and **Conversation PII model** (2026-04-15-preview) are licensed to you as part of your Azure subscription and are subject to terms applicable  to "Previews" in the [Microsoft Product Terms](https://www.microsoft.com/licensing/terms/welcome/welcomepage) 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), as well as the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms).
+
+## Prerequisites
+
+> [!TIP]
+>
+> * If you already have an Azure Language in Foundry Tools or multi-service resource—whether used on its own or through Language Studio—you can continue to use those existing Language resources within the Microsoft Foundry portal.
+> * For more information, see [Connect services in the Microsoft Foundry portal](../../connect-services-foundry-portal.md).
+> * Consider using a Foundry resource for the best experience. You can also follow these instructions with a Language resource.
+
+* **Azure subscription**. If you don't have one, you can [create one for free](https://azure.microsoft.com/pricing/purchase-options/azure-account?cid=msft_learn).
+* **Requisite permissions**. Make sure the person establishing the account and project is assigned as the **Foundry Account Owner** role at the subscription level. Alternatively, having either the **Contributor** or **Cognitive Services Contributor** role at the subscription scope also meets this requirement. For more information, see [Role based access control (RBAC)](../../../ai-foundry/openai/how-to/role-based-access-control.md#cognitive-services-contributor).
+* **Foundry resource**. Create a [Foundry resource](../../multi-service-resource.md) or see [Configure a Foundry resource](../concepts/configure-azure-resources.md). Alternatively, you can use a [Language resource](https://portal.azure.com/?Microsoft_Azure_PIMCommon=true#create/Microsoft.CognitiveServicesTextAnalytics).
+* **A Foundry project**. For more information, see [Create a Foundry project](../../../ai-foundry/how-to/create-projects.md).
+
+## Role-based access control (RBAC) requirements
+
+Assign the correct roles to your user principal and project managed identity to access the conversation PII playground. Microsoft recommends using Microsoft Entra ID authentication, which enforces role-based restrictions. Key-based authentication grants full access without role checks and should be avoided in production environments.
+
+> [!IMPORTANT]
+> The Foundry RBAC roles were recently renamed. **Foundry User**, **Foundry Owner**, **Foundry Account Owner**, and **Foundry Project Manager** were previously named Azure AI User, Azure AI Owner, Azure AI Account Owner, and Azure AI Project Manager. You might still see the previous names in some places while the rename rolls out. The role IDs and core permissions are unchanged.
+
+* Assign the minimum required roles to both your user principal and project managed identity so they can access Foundry features.
+
+* Verify current assignments using [Check access for a user to a single Azure resource](/azure/role-based-access-control/check-access).
+
+
+## Navigate to the playground
+
+The active project appears in the upper-left corner. To create a new project:
+
+1. Open the project drop-down menu.
+1. Enter a project name or select an existing one.
+1. Select **Create project**.
+
+   :::image type="content" source="../media/new-foundry-homepage.png" alt-text="Screenshot of the new Foundry homepage.":::
+
+There are two ways to access the conversation PII interface:
+
+* Select the **Discover** tab from the upper-right navigation bar:
+  1. In the search bar, enter **Azure** and press **Enter**.
+  1. Select **Azure-Language-Conversational-PII redaction** from the results.
+  1. Select **Open in Playground**.
+
+* Select the **Build** tab from the upper-right navigation bar:
+  1. From the left navigation bar, select **Models**.
+  1. Select the **AI services** tab.
+  1. Select **Azure-Language-Conversational-PII redaction** to go directly to the playground.
+
+## Extract PII from conversations
+
+The **extract PII from conversations** feature detects and masks personally identifying information in conversational text. This feature is designed to handle the unique structure and context of conversations, such as dialogues or chat logs.
+
+1. On the **Playground** tab, select **Azure Language—Conversational PII redaction** from the drop-down menu.
+
+1. Select a sample transcript, use the paperclip icon to upload your transcript, or enter conversation turn text.
+
+1. Format your conversation with each turn on a new line and include speaker labels if possible. Inconsistent use of participant ID, colon, message, or new line may produce unexpected output. Here's an example of well-formatted conversation text:
+
+    ```text
+    Speaker 1: Hello, how are you?
+    Speaker 2: I'm good, thank you! How about you?
+    Speaker 1: I'm doing well, thanks for asking.
+    ```
+
+   > [!TIP]
+   > You can use built-in formatting assistant (**Format for me**) in the playground to ensure your input meets expected conversation structure.
+
+1. In the **Configure** pane, set the following options:
+
+    | Option | Description |
+    | --- | --- |
+    | **API version** | Select the API version that you prefer to use. |
+    | **Model version** | Select the model version that you prefer to use. |
+    | **Language** | Select the language in which your source text is written. |
+    | **Select types to include** | Select the PII types you want to redact. |
+    | **Specify redaction character** | Choose the character used to mask sensitive text. |
+
+1. Select **Detect**. Detected entities are highlighted in the text, and you can review the accompanying details in formatted text or as a JSON response.
+
+    :::image type="content" source="media/quickstarts/azure-ai-foundry/new-foundry-conversation-detection.png" alt-text="Screenshot of PII conversation detection output in the Foundry playground." lightbox="media/quickstarts/azure-ai-foundry/new-foundry-conversation-detection.png":::
+
+    | Field | Description |
+    | --- | --- |
+    | **Type** | The detected entity type. |
+    | **Confidence** | The model's level of certainty that it correctly identified the entity type. |
+    | **Offset** | The number of characters from the beginning of the text to the entity. |
+    | **Length** | The character length of the entity. |
+
+Verify that the detected entities match the PII in your input conversation. Select **Edit** to modify the **Configure** settings and rerun detection as needed.
+
+## Open in Visual Studio Code 🆕
+
+After validating your scenario in the playground, select **Open in VS Code** to carry your current configuration directly into a development environment—no manual setup required.
+
+1. Configure your scenario in the playground:
+   - Select your API version and model version.
+   - Enter and test your sample input.
+   - Adjust options such as entity types, redaction character, and language.
+1. Select **Open in VS Code**.
+1. Visual Studio Code opens with a preconfigured code sample that reflects your playground configuration, including your API version, model, and redaction settings.
+
+> [!TIP]
+> Use the playground to compare outputs across API versions, for example, preview versus GA—before exporting your configuration to code.
+
+## Next steps
+
+After opening in Visual Studio Code:
+
+1. Add your authentication credentials.
+1. Replace the sample input with your production data.
+1. Run and validate the request.
+1. Integrate the code into your application workflow.
\ No newline at end of file

@@ -65,7 +65,7 @@ Document-based PII uses an asynchronous workflow:
 1. Poll the job status by using the operation location.
 1. Retrieve output artifacts from your target storage location.
 
-:::image type="content" source="media/document-pii-workflow.png" alt-text="Diagram showing the asynchronous workflow for document-based PII detection.":::
+:::image type="content" source="media/document-pii-api-call.png" alt-text="Diagram showing the asynchronous workflow for document-based PII detection.":::
 
 For implementation details and request samples, see [Detect and redact Personally Identifiable Information in native documents](how-to/redact-document-pii.md).
 

@@ -0,0 +1,99 @@
+---
+title: Use the document PII playground in Microsoft 
+FoundrytitleSuffix: Azure AI Language
+description: Test document-based PII detection and redaction interactively in the Azure AI Foundry playground without writing code.
+author: laujan
+manager: nitinme
+ms.service: azure-ai-language
+ms.topic: quickstart
+ms.date: 05/18/2026
+ms.author: lajanuar
+ms.custom: language-service-pii
+---
+
+<!-- markdownlint-disable MD025 -->
+# Use the document PII playground in Microsoft Foundry
+
+> [!NOTE]
+> This content refers to the [new Foundry](https://ai.azure.com/) portal, which supports only [Foundry projects](../../../ai-foundry/what-is-foundry.md) and provides streamlined access to models, agents, and tools. To confirm that you're using new Foundry, make sure the version toggle in the portal banner is in the **on** position. :::image type="icon" source="media/quickstarts/azure-ai-foundry/new-foundry.png" border="false":::
+
+The document PII playground in Azure AI Foundry lets you detect and redact personally identifiable information (PII) in native documents interactively, without writing code. You can upload document files, configure redaction options, and review redacted output before integrating the feature into your application.
+
+> [!IMPORTANT]
+> Document-based PII is currently in preview and may change before general availability (GA).
+
+## Prerequisites
+
+> [!TIP]
+>
+> * If you already have an Azure Language in Foundry Tools or multi-service resource—whether used on its own or through Language Studio—you can continue to use those existing Language resources within the Microsoft Foundry portal.
+> * For more information, see [Connect services in the Microsoft Foundry portal](../../connect-services-foundry-portal.md).
+> * Consider using a Foundry resource for the best experience. You can also follow these instructions with a Language resource.
+
+* **Azure subscription**. If you don't have one, you can [create one for free](https://azure.microsoft.com/pricing/purchase-options/azure-account?cid=msft_learn).
+* **Requisite permissions**. Make sure the person establishing the account and project is assigned as the **Foundry Account Owner** role at the subscription level. Alternatively, having either the **Contributor** or **Cognitive Services Contributor** role at the subscription scope also meets this requirement. For more information, see [Role based access control (RBAC)](../../../ai-foundry/openai/how-to/role-based-access-control.md#cognitive-services-contributor).
+* **Foundry resource**. Create a [Foundry resource](../../multi-service-resource.md) or see [Configure a Foundry resource](../concepts/configure-azure-resources.md). Alternatively, you can use a [Language resource](https://portal.azure.com/?Microsoft_Azure_PIMCommon=true#create/Microsoft.CognitiveServicesTextAnalytics).
+* **A Foundry project**. For more information, see [Create a Foundry project](../../../ai-foundry/how-to/create-projects.md).
+
+## Role-based access control (RBAC) requirements
+
+Assign the correct roles to your user principal and project managed identity to access the document PII playground. Microsoft recommends using Microsoft Entra ID authentication, which enforces role-based restrictions. Key-based authentication grants full access without role checks and should be avoided in production environments.
+
+> [!IMPORTANT]
+> The Foundry RBAC roles were recently renamed. **Foundry User**, **Foundry Owner**, **Foundry Account Owner**, and **Foundry Project Manager** were previously named Azure AI User, Azure AI Owner, Azure AI Account Owner, and Azure AI Project Manager. You might still see the previous names in some places while the rename rolls out. The role IDs and core permissions are unchanged.
+
+* Assign the minimum required roles to both your user principal and project managed identity so they can access Foundry features.
+
+* Verify current assignments using [Check access for a user to a single Azure resource](/azure/role-based-access-control/check-access).
+
+
+## Navigate to the playground
+
+The active project appears in the upper-left corner. To create a new project:
+
+1. Open the project drop-down menu.
+1. Enter a project name or select an existing one.
+1. Select **Create project**.
+
+   :::image type="content" source="../media/new-foundry-homepage.png" alt-text="Screenshot of the new Foundry homepage.":::
+
+There are two ways to access the document PII interface:
+
+* Select the **Discover** tab from the upper-right navigation bar:
+  1. In the search bar, enter **Azure** and press **Enter**.
+  1. Select **Azure-Language-Document-PII redaction** from the results.
+  1. Select **Open in Playground**.
+
+* Select the **Build** tab from the upper-right navigation bar:
+  1. From the left navigation bar, select **Models**.
+  1. Select the **AI services** tab.
+  1. Select **Azure-Language-Document-PII redaction** to go directly to the playground.
+
+## Redact PII from documents
+
+The **Azure-Language-Document-PII redaction** model identifies and redacts personally identifiable information in native document files, including `.pdf`, `.docx`, and `.txt` files. The playground preserves document layout and formatting in the redacted output.
+
+1. On the **Playground** tab, select **Azure Language—Document PII redaction** from the drop-down menu.
+
+1. Use the paperclip icon to upload a `.pdf`, `.docx`, or `.txt` document.
+
+1. In the **Configure** pane, set the following options:
+
+    | Option | Description |
+    | --- | --- |
+    | **API version** | Select the API version that you prefer to use. |
+    | **Model version** | Select the model version that you prefer to use. |
+    | **Language** | Select the language in which your document is written. |
+    | **Select types to include** | Select the PII types you want to redact. |
+    | **Policy type** | Choose the type of redaction policy to apply (character mask, entity mask, or no mask). |
+
+1. Select **Detect**. After processing completes, the redacted document is displayed and you can review the detected entities in the **Details** pane.
+
+    | Field | Description |
+    | --- | --- |
+    | **Type** | The detected entity type. |
+    | **Confidence** | The model's level of certainty regarding whether it correctly identified an entity type. |
+    | **Offset** | The position of the entity within the document. |
+    | **Length** | The character length of the entity. |
+
+Verify that the detected entities match the PII in your input document. Use the **Edit** button to modify **Configure** parameters and resubmit the document as needed.
\ No newline at end of file

@@ -6,14 +6,17 @@ author: laujan
 manager: nitinme
 ms.service: azure-ai-language
 ms.topic: how-to
-ms.date: 04/03/2026
+ms.date: 06/02/2026
 ms.author: lajanuar
 ms.custom: language-service-pii
 ---
 # Detect and redact Personally Identifiable Information in conversations
 
 Azure Language in Foundry Tools conversation PII API analyzes audio discourse to identify and redact sensitive information (PII) using various predefined categories. This API works on both transcribed text (referred to as transcripts) and chats. For transcripts, it also facilitates the redaction of audio segments containing PII by providing the timing information for those segments.
 
+> [!IMPORTANT]
+> **Conversation PII API** (2026-11-15-preview) and **Conversation PII model** (2026-04-15-preview) are licensed to you as part of your Azure subscription and are subject to terms applicable to "Previews" in the [Microsoft Product Terms](https://www.microsoft.com/licensing/terms/welcome/welcomepage) 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), as well as the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms).
+
 ## Determine how to process the data (optional)
 
 ### Specify the PII detection model

@@ -6,7 +6,7 @@ author: laujan
 manager: nitinme
 ms.service: azure-ai-language
 ms.topic: how-to
-ms.date: 03/17/2026
+ms.date: 06/02/2026
 ms.author: lajanuar
 ms.custom: language-service-pii
 ---
@@ -15,6 +15,12 @@ ms.custom: language-service-pii
 
 Azure Language in Foundry Tools is a cloud-based service that applies Natural Language Processing (NLP) features to text-based data. The PII feature can evaluate unstructured text, extract, and redact sensitive information (PII) and health information (PHI) in text across several [predefined categories](../concepts/entity-categories.md).
 
+* [**Stable 2026-05-01: Generally Available (GA)**](/rest/api/language/analyze-text/analyze-text/analyze-text?view=rest-language-analyze-text-2025-11-01&preserve-view=true&tabs=HTTP)
+* [**Preview: 2026-05-15-preview**](/rest/api/language/analyze-text/analyze-text/analyze-text?view=rest-language-analyze-text-2025-11-15-preview&preserve-view=true&tabs=HTTP).
+
+   > [!IMPORTANT]
+   > **Text PII API** (2026-05-15-preview) is licensed to you as part of your Azure subscription and is subject to terms applicable to "Previews" in the [Microsoft Product Terms](https://www.microsoft.com/licensing/terms/welcome/welcomepage) 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), as well as the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms).
+
 ## Development options
 
 [!INCLUDE [development options](../includes/development-options.md)]

@@ -3,11 +3,11 @@ author: laujan
 manager: nitinme
 ms.service: azure-ai-language
 ms.topic: include
-ms.date: 04/27/2026
+ms.date: 06/02/2026
 ms.author: lajanuar
 ms.custom: doc-kit-assisted
 ---
-
+<!-- markdownlint-disable MD041 -->
 ## Prerequisites
 
 > [!TIP]
@@ -17,118 +17,91 @@ ms.custom: doc-kit-assisted
 > * Consider using a Foundry resource for the best experience. You can also follow these instructions with a Language resource.
 
 * **Azure subscription**. If you don't have one, you can [create one for free](https://azure.microsoft.com/pricing/purchase-options/azure-account?cid=msft_learn).
-* **Requisite permissions**. Make sure the person establishing the account and project is assigned as the Foundry Account Owner role at the subscription level. Alternatively, having either the **Contributor** or **Cognitive Services Contributor** role at the subscription scope also meets this requirement. For more information, see [Role based access control (RBAC)](../../../../../ai-foundry/openai/how-to/role-based-access-control.md#cognitive-services-contributor).
-
-  [!INCLUDE [role-rename-note](../../../../../foundry/includes/role-rename-note.md)]
+* **Requisite permissions**. Make sure the person establishing the account and project is assigned as the **Foundry Account Owner** role at the subscription level. Alternatively, having either the **Contributor** or **Cognitive Services Contributor** role at the subscription scope also meets this requirement. For more information, see [Role based access control (RBAC)](../../../../../ai-foundry/openai/how-to/role-based-access-control.md#cognitive-services-contributor).
 * **Foundry resource**. Create a [Foundry resource](../../../../multi-service-resource.md) or see [Configure a Foundry resource](../../../concepts/configure-azure-resources.md). Alternatively, you can use a [Language resource](https://portal.azure.com/?Microsoft_Azure_PIMCommon=true#create/Microsoft.CognitiveServicesTextAnalytics).
 * **A Foundry project**. For more information, see [Create a Foundry project](../../../../../ai-foundry/how-to/create-projects.md).
 
-### [Foundry (new)](#tab/foundry-new)
+## Role-based access control (RBAC) requirements
+
+Assign the correct roles to your user principal and project managed identity to access PII playgrounds. Microsoft recommends using Microsoft Entra ID authentication, which enforces role-based restrictions. Key-based authentication grants full access without role checks and should be avoided in production environments.
+
+> [!IMPORTANT]
+> The Foundry RBAC roles were recently renamed. **Foundry User**, **Foundry Owner**, **Foundry Account Owner**, and **Foundry Project Manager** were previously named Azure AI User, Azure AI Owner, Azure AI Account Owner, and Azure AI Project Manager. You might still see the previous names in some places while the rename rolls out. The role IDs and core permissions are unchanged.
+
+* Assign the minimum required roles to both your user principal and project managed identity so they can access Foundry features.
+
+* Verify current assignments using [Check access for a user to a single Azure resource](/azure/role-based-access-control/check-access).
+
+### [New Foundry](#tab/new-foundry)
 
 > [!NOTE]
-> This content refers to the [Foundry (new)](https://ai.azure.com/) portal, which supports only [Foundry projects](../../../../../ai-foundry/what-is-foundry.md) and provides streamlined access to models, agents, and tools. To confirm that you're using Foundry (new), make sure the version toggle in the portal banner is in the **on** position. :::image type="icon" source="../../media/quickstarts/azure-ai-foundry/new-foundry.png" border="false":::
+> This content refers to the [new Foundry](https://ai.azure.com/) portal, which supports only [Foundry projects](../../../../../ai-foundry/what-is-foundry.md) and provides streamlined access to models, agents, and tools. To confirm that you're using new Foundry, make sure the version toggle in the portal banner is in the **on** position. :::image type="icon" source="../../media/quickstarts/azure-ai-foundry/new-foundry.png" border="false":::
 
-You can use [Foundry (new)](https://ai.azure.com/) to:
+You can use [new Foundry playground](https://ai.azure.com/) to:
 
 > [!div class="checklist"]
 >
-> * Extract personally identifiable information (PII) from text
-> * Configure redaction policies and excluded values
+> * Detect and redact PII from text, conversations, or documents
+> * Configure redaction policies, entity filters, and excluded values
 > * Review detected entities and confidence scores
 
-## Navigate to the Foundry (new) playground
+## Navigate to the new Foundry playground
 
 The active project appears in the upper-left corner. To create a new project:
 
 1. Open the project drop-down menu.
 1. Enter a project name or select an existing one.
 1. Select **Create project**.
 
-   :::image type="content" source="../../../media/new-foundry-homepage.png" alt-text="Screenshot of the Foundry (new) homepage.":::
+   :::image type="content" source="../../../media/new-foundry-homepage.png" alt-text="Screenshot of the new Foundry homepage.":::
 
-There are two ways to access the personally identifiable information (PII) interface:
+There are two ways to access the PII playground:
 
 1. Select the **Discover** tab from the upper right navigation bar to go to the **Models** page.
    * In the search bar under models, enter **Azure** and press enter.
-   * Next, select **Azure-Language-Text-PII redaction** from the search results.
-   * Finally, select the **Open in Playground** button.
+   * Select your PII capability model from the search results.
+   * Select the **Open in Playground** button.
 
-1. Select the  **Build** tab from the upper right navigation bar.
-   * From the left navigation bar, select  **Models**.
+1. Select the **Build** tab from the upper right navigation bar.
+   * From the left navigation bar, select **Models**.
    * Select the **AI services** tab.
-   * Next, select **Azure-Language-Text-PII redaction** to go to the playground.
+   * Select your PII capability model to go to the playground.
 
-## Extract  PII from text
+## Detect PII in the new Foundry playground
 
-The **Azure-Language-Text-PII redaction** model is used to identify and redact personally identifiable information in text. The interface provides configuration options to customize your detection and redaction preferences, as well as detailed output to review the detected entities and their confidence scores.
+Each PII capability uses a dedicated model. On the **Playground** tab, select your capability from the drop-down menu:
 
-1. On the **Playground** tab, select **Azure Language—Text PII redaction** from the drop-down menu.
+| Capability | Model name |
+| --- | --- |
+| Text PII redaction | **Azure Language—Text PII redaction** |
+| Conversation PII redaction | **Azure Language—Conversational PII redaction** |
+| Document PII redaction | **Azure Language—Document PII redaction** |
 
-1. Select the sample text, use the paperclip icon to upload your text, or enter your own text.
+1. Select sample input, use the paperclip icon to upload a file, or enter your own input data.
 
-1. In the **Configure** side panel, you can set the following options:
+1. In the **Configure** side panel, set your preferred options. Available options vary by capability:
 
     | Option | Description |
     | --- | --- |
     | **API version** | Select the API version that you prefer to use. |
     | **Model version** | Select the model version that you prefer to use. |
-    | **Language** | Select the language in which your source text is written. |
-    | **Select types to include** | Select the PII types you want to redact. |
-    | **Value to exclude** | Specify values that you want to exclude from detection. For example, if you want to redact email addresses but want to exclude ones from a specific domain, you can enter that domain as an excluded value. |
-    | **Synonyms** | Provide alternative names for specific entity types. For example, if you select enter "Microsoft" as an excluded value, you can also specify specific synonyms such as `MSFT` and `Microsoft Corporation`. |
+    | **Language** | Select the language of your input. |
+    | **Select types to include** | Select the PII types you want to detect or redact. |
+    | **Value to exclude** | Specify values you want to exclude from detection. |
+    | **Synonyms** | Provide alternative names for specific entity types. |
     | **Policy type** | Choose the type of redaction policy to apply (character mask, entity mask, or no mask). |
+    | **Specify redaction character** | Choose the character used to mask sensitive text. Available with the **CharacterMask** policy. |
 
-1. After you make your selections, choose the **Detect** button. Detected entities are highlighted in the text and you can review the accompanying details in formatted text or as a JSON response.
-
-    :::image type="content" source="../../media/quickstarts/azure-ai-foundry/new-foundry-text-detection.png" alt-text="Screenshot of PII text detection output in the Foundry playground." lightbox="../../media/quickstarts/azure-ai-foundry/new-foundry-text-detection.png":::
-
-    | Field | Description |
-    | --- | --- |
-    | **Type** | The detected type. |
-    | **Confidence** | The model's level of certainty regarding whether it correctly identified an entity type. |
-    | **Offset** | The number of characters that the entity was detected from the beginning of the text. |
-    | **Length** | The character length of the entity. |
-
-Verify that the detected entities match the PII in your input text. You can use the **Edit** button to modify the **Configure** parameters and rerun detection as needed.
-
-## Extract  PII from conversations 🆕
-
-The **extract PII from conversations** feature detects and masks personally identifying information within conversational text. This feature is designed to handle the unique structure and context of conversations, such as dialogues or chat logs.
-
-1. On the **Playground** tab, select **Azure Language—Conversational PII redaction** from the drop-down menu.
-
-1. Select a sample transcript, use the paperclip icon to upload your transcript, or input conversation turn text.
-
-1. Format your conversation with each turn on a new line and include speaker labels if possible. If participant ID, colon, message, or new line are not used consistently, the output may be unexpected. Here's an example of well-formatted conversation text:
-
-    ```text
-    Speaker 1: Hello, how are you?
-    Speaker 2: I'm good, thank you! How about you?
-    Speaker 1: I'm doing well, thanks for asking.
-    ```
-
-1. In the **Configure** side panel, set your preferred options for API version, model version, language, types, redaction policy, and excluded values.
-
-    | Option | Description |
-    | --- | --- |
-    | **API version** | Select the API version that you prefer to use. |
-    | **Model version** | Select the model version that you prefer to use. |
-    | **Language** | Select the language in which your source text is written. |
-    | **Select types to include** | Select the PII types you want to redact. |
-    | **Specify redaction character** | Choose the character used to mask sensitive text. |
-
-1. After you make your selections, choose the **Detect** button. Detected entities are highlighted in the text and you can review the accompanying details in formatted text or as a JSON response.
-
-    :::image type="content" source="../../media/quickstarts/azure-ai-foundry/new-foundry-conversation-detection.png" alt-text="Screenshot of PII conversation detection output in the Foundry playground." lightbox="../../media/quickstarts/azure-ai-foundry/new-foundry-conversation-detection.png":::
+1. Select **Detect**. Detected entities are highlighted in the input and you can review the accompanying details in formatted text or as a JSON response.
 
     | Field | Description |
     | --- | --- |
-    | **Type** | The detected type. |
+    | **Type** | The detected entity type. |
     | **Confidence** | The model's level of certainty regarding whether it correctly identified an entity type. |
-    | **Offset** | The number of characters that the entity was detected from the beginning of the text. |
+    | **Offset** | The number of characters from the beginning of the input to the entity. |
     | **Length** | The character length of the entity. |
 
-Verify that the detected entities match the PII in your input conversation. You can use the **Edit** button to modify the **Configure** parameters and rerun detection as needed.
+Verify that the detected entities match the PII in your input. You can use the **Edit** button to modify the **Configure** parameters and rerun detection as needed.
 
 ### [Foundry (classic)](#tab/foundry-classic)
 
@@ -139,8 +112,7 @@ You can use [Foundry (classic)](https://ai.azure.com/) to:
 
 > [!div class="checklist"]
 >
-> * Extract PII from conversations
-> * Extract PII from text
+> * Detect and redact PII from conversations and text
 > * Configure redaction policies
 > * Review detected entities and confidence scores
 
@@ -151,30 +123,26 @@ You can use [Foundry (classic)](https://ai.azure.com/) to:
 
 :::image type="content" source="../../media/quickstarts/azure-ai-foundry/foundry-playground-navigation.png" alt-text="Screenshot showing the Playgrounds navigation and the Try Azure Language Playground button in Foundry (classic)." lightbox="../../media/quickstarts/azure-ai-foundry/foundry-playground-navigation.png":::
 
-## Detect  PII in the Foundry playground
+## Detect PII in the Foundry (classic) playground
 
 The **Language Playground** consists of four sections:
 
 | Section | Purpose |
 | --- | --- |
-| **Top banner** | Select the input language and choose a  PII detection capability. |
+| **Top banner** | Select the input language and choose a PII detection capability. |
 | **Left pane** | Set **Configuration** options such as API version, model version, and redaction policy. |
-| **Center pane** | Enter text for processing and review highlighted results. |
+| **Center pane** | Enter text or conversation data for processing and review highlighted results. |
 | **Right pane** | View **Details** for each detected entity. |
 
-Select either **Extract PII from conversation** or **Extract PII from text** from the top banner tiles. Each capability targets a different scenario.
-
-### Extract  PII text
-
-**Extract PII from text** is designed to identify and mask personally identifying information in text.
+Select your PII capability from the top banner tiles. Each capability targets a different scenario.
 
 In **Configuration** you can select from the following options:
 
 | Option | Description |
 | --- | --- |
 | Select API version | Select which version of the API to use. |
 | Select model version | Select which version of the model to use. |
-| Select text language | Select the language of your input text. |
+| Select text language | Select the language of your input. |
 | Select types to include | Select the types of information you want to redact. |
 | Specify redaction policy | Select the method of redaction. |
 | Specify redaction character | Select the character used for redaction. Only available with the **CharacterMask** redaction policy. |
@@ -192,41 +160,6 @@ The **Details** section contains the following fields for each entity:
 | Confidence | The model's level of certainty that the entity type is correct. |
 | Tags | The model's confidence scores for each identified entity subtype. |
 
-:::image type="content" source="../../media/quickstarts/azure-ai-foundry/text-pii.png" alt-text="A screenshot showing detected PII entities in text displayed in the Foundry portal." lightbox="../../media/quickstarts/azure-ai-foundry/text-pii.png":::
-
-Verify that each PII entity appears highlighted with the correct category label. The **Tags** column shows subcategory confidence scores when applicable.
-
-### Extract  PII conversations
-
-**Extract PII from conversation** is designed to identify and mask personally identifying information in conversational text.
-
-In **Configuration** there are the following options:
-
-| Option | Description |
-| --- | --- |
-| Select API version | Select which version of the API to use. |
-| Select model version | Select which version of the model to use. |
-| Select text language | Select the language of your input text. |
-| Select types to include | Select the types of information you want to redact. |
-| Specify redaction policy | Select the method of redaction. |
-| Specify redaction character | Select the character used for redaction. Only available with the **CharacterMask** redaction policy. |
-
-After the operation completes, each detected entity is highlighted in the center pane with its type label displayed beneath it.
-
-The **Details** section contains the following fields for each entity:
+Verify that each PII entity appears highlighted with the correct category label. If no entities appear, check that the input contains recognizable PII patterns and that the **Types** filter includes the expected categories.
 
-| Field | Description |
-| --- | --- |
-| Entity | The detected entity. |
-| Category | The entity type that was detected. |
-| Offset | The number of characters from the beginning of the line to the entity. |
-| Length | The character length of the entity. |
-| Confidence | The model's level of certainty that the entity type is correct. |
-
-:::image type="content" source="../../media/quickstarts/azure-ai-foundry/conversation-pii.png" alt-text="A screenshot showing detected PII entities highlighted in a conversation with entity details displayed in the right pane of the Foundry portal." lightbox="../../media/quickstarts/azure-ai-foundry/conversation-pii.png":::
-
-Verify that each PII entity appears highlighted with the correct category label. If no entities appear, check that the input text contains recognizable PII patterns and that the **Types** filter includes the expected categories.
-
-
-
----
+---
\ No newline at end of file

@@ -6,7 +6,7 @@ author: laujan
 manager: nitinme
 ms.service: azure-ai-language
 ms.topic: overview
-ms.date: 04/16/2026
+ms.date: 06/02/2026
 ms.author: lajanuar
 ms.custom: language-service-pii
 ---
@@ -101,6 +101,9 @@ All feature types use predefined entity categories and return confidence-scored
 
 ## GA and preview guidance
 
+> [!IMPORTANT]
+> Text PII API (2026-05-15-preview) and Conversation PII API (2026-11-15-preview) and **Conversation PII model** (2026-04-15-preview) are licensed to you as part of your Azure subscription and are subject to terms applicable to "Previews" in the [Microsoft Product Terms](https://www.microsoft.com/licensing/terms/welcome/welcomepage) 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), as well as the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
+
 To avoid integration issues, use API versions and features that match your deployment target:
 
 * Use generally available (GA) API versions for production workloads.

@@ -0,0 +1,131 @@
+---
+title: Use the text PII playground in Microsoft 
+FoundrytitleSuffix: Azure AI Language
+description: Test text PII detection and redaction interactively in the Azure AI Foundry playground without writing code.
+author: laujan
+manager: nitinme
+ms.service: azure-ai-language
+ms.topic: quickstart
+ms.date: 05/18/2026
+ms.author: lajanuar
+ms.custom: language-service-pii
+---
+
+<!-- markdownlint-disable MD025 -->
+# Use the text PII playground in Microsoft Foundry
+
+> [!NOTE]
+> This content refers to the [new Foundry](https://ai.azure.com/) portal, which supports only [Foundry projects](../../../ai-foundry/what-is-foundry.md) and provides streamlined access to models, agents, and tools. To confirm that you're using new Foundry, make sure the version toggle in the portal banner is in the **on** position. :::image type="icon" source="media/quickstarts/azure-ai-foundry/new-foundry.png" border="false":::
+
+The text PII playground in Azure AI Foundry lets you detect and redact personally identifiable information (PII) from raw text interactively, without writing code. You can submit sample text, configure detection and redaction options, and review detected entities before integrating the feature into your application.
+
+* [Stable: **2026-05-01 (GA)**](/rest/api/language/analyze-text/analyze-text/analyze-text?view=rest-language-analyze-text-2025-11-01&preserve-view=true&tabs=HTTP)
+* [Preview: **2026-05-15-preview**](/rest/api/language/analyze-text/analyze-text/analyze-text?view=rest-language-analyze-text-2025-11-15-preview&preserve-view=true&tabs=HTTP).
+
+   > [!IMPORTANT]
+   > **Text PII API** (2026-05-15-preview) is licensed to you as part of your Azure subscription and is subject to terms applicable to "Previews" in the [Microsoft Product Terms](https://www.microsoft.com/licensing/terms/welcome/welcomepage) 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), as well as the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms).
+
+## Prerequisites
+
+> [!TIP]
+>
+> * If you already have an Azure Language in Foundry Tools or multi-service resource—whether used on its own or through Language Studio—you can continue to use those existing Language resources within the Microsoft Foundry portal.
+> * For more information, see [Connect services in the Microsoft Foundry portal](../../connect-services-foundry-portal.md).
+> * Consider using a Foundry resource for the best experience. You can also follow these instructions with a Language resource.
+
+* **Azure subscription**. If you don't have one, you can [create one for free](https://azure.microsoft.com/pricing/purchase-options/azure-account?cid=msft_learn).
+* **Requisite permissions**. Make sure the person establishing the account and project is assigned as the **Foundry Account Owner** role at the subscription level. Alternatively, having either the **Contributor** or **Cognitive Services Contributor** role at the subscription scope also meets this requirement. For more information, see [Role based access control (RBAC)](../../../ai-foundry/openai/how-to/role-based-access-control.md#cognitive-services-contributor).
+* **Foundry resource**. Create a [Foundry resource](../../multi-service-resource.md) or see [Configure a Foundry resource](../concepts/configure-azure-resources.md). Alternatively, you can use a [Language resource](https://portal.azure.com/?Microsoft_Azure_PIMCommon=true#create/Microsoft.CognitiveServicesTextAnalytics).
+* **A Foundry project**. For more information, see [Create a Foundry project](../../../ai-foundry/how-to/create-projects.md).
+
+## Role-based access control (RBAC) requirements
+
+Assign the correct roles to your user principal and project managed identity to access the text PII playground. Microsoft recommends using Microsoft Entra ID authentication, which enforces role-based restrictions. Key-based authentication grants full access without role checks and should be avoided in production environments.
+
+> [!IMPORTANT]
+> The Foundry RBAC roles were recently renamed. **Foundry User**, **Foundry Owner**, **Foundry Account Owner**, and **Foundry Project Manager** were previously named Azure AI User, Azure AI Owner, Azure AI Account Owner, and Azure AI Project Manager. You might still see the previous names in some places while the rename rolls out. The role IDs and core permissions are unchanged.
+
+* Assign the minimum required roles to both your user principal and project managed identity so they can access Foundry features.
+
+* Verify current assignments using [Check access for a user to a single Azure resource](/azure/role-based-access-control/check-access).
+
+
+## Navigate to the playground
+
+The active project appears in the upper-left corner. To create a new project:
+
+1. Open the project drop-down menu.
+1. Enter a project name or select an existing one.
+1. Select **Create project**.
+
+   :::image type="content" source="../media/new-foundry-homepage.png" alt-text="Screenshot of the new Foundry homepage.":::
+
+There are two ways to access the text PII interface:
+
+* Select the **Discover** tab from the upper-right navigation bar:
+  1. In the search bar, enter **Azure** and press **Enter**.
+  1. Select **Azure-Language-Text-PII redaction** from the results.
+  1. Select **Open in Playground**.
+
+* Select the **Build** tab from the upper-right navigation bar:
+  1. From the left navigation bar, select **Models**.
+  1. Select the **AI services** tab.
+  1. Select **Azure-Language-Text-PII redaction** to go directly to the playground.
+
+## Extract PII from text
+
+
+
+The **Azure-Language-Text-PII redaction** model identifies and redacts personally identifiable information in text. The playground provides configuration options to customize detection and redaction preferences, and detailed output to review detected entities and confidence scores.
+
+1. On the **Playground** tab, select **Azure Language—Text PII redaction** from the drop-down menu.
+
+1. Select the sample text, use the paperclip icon to upload your text, or enter your own text.
+
+1. In the **Configure** pane, set the following options:
+
+    | Option | Description |
+    | --- | --- |
+    | **API version** | Select the API version that you prefer to use. |
+    | **Model version** | Select the model version that you prefer to use. |
+    | **Language** | Select the language in which your source text is written. |
+    | **Select types to include** | Select the PII types you want to redact. |
+    | **Value to exclude** | Specify values you want to exclude from detection. For example, to redact email addresses but exclude a specific domain, enter that domain as an excluded value. |
+    | **Synonyms** | Provide alternative names for specific entity types. For example, if you enter "Microsoft" as an excluded value, you can also specify synonyms such as `MSFT` and `Microsoft Corporation`. |
+    | **Policy type** | Choose the type of redaction policy to apply (character mask, entity mask, or no mask). |
+
+1. Select **Detect**. Detected entities are highlighted in the text, and you can review the accompanying details in formatted text or as a JSON response.
+
+    :::image type="content" source="media/quickstarts/azure-ai-foundry/new-foundry-text-detection.png" alt-text="Screenshot of PII text detection output in the Foundry playground." lightbox="media/quickstarts/azure-ai-foundry/new-foundry-text-detection.png":::
+
+    | Field | Description |
+    | --- | --- |
+    | **Type** | The detected entity type. |
+    | **Confidence** | The model's level of certainty regarding whether it correctly identified an entity type. |
+    | **Offset** | The number of characters from the beginning of the text to the entity. |
+    | **Length** | The character length of the entity. |
+
+Verify that the detected entities match the PII in your input text. Use the **Edit** button to modify **Configure** parameters and rerun detection as needed.
+
+## Open in Visual Studio Code 🆕
+
+After validating your scenario in the playground, select **Open in VS Code** to carry your current configuration directly into a development environment—no manual setup required.
+
+1. Configure your scenario in the playground:
+   - Select your API version and model version.
+   - Enter and test your sample input.
+   - Adjust options such as entity types, redaction policy, and excluded values.
+1. Select **Open in VS Code**.
+1. Visual Studio Code opens with a preconfigured code sample that reflects your playground configuration, including your API version, model, and redaction settings.
+
+> [!TIP]
+> Use the playground to compare outputs across API versions—for example, preview versus GA—before exporting your configuration to code.
+
+## Next steps
+
+After opening in Visual Studio Code:
+
+1. Add your authentication credentials.
+1. Replace the sample input with your production data.
+1. Run and validate the request.
+1. Integrate the code into your application workflow.
\ No newline at end of file

@@ -1,51 +1,167 @@
----
+---
 author: laujan
 manager: nitinme
 ms.service: azure-ai-language
 ms.topic: include
-ms.date: 11/18/2025
+ms.date: 06/02/2026
 ms.author: lajanuar
+ms.custom: doc-kit-assisted
 ---
+<!-- markdownlint-disable MD041 -->
 ## Prerequisites
 
-* [Create a Project in Foundry in the Microsoft Foundry portal](../../../../../ai-foundry/how-to/create-projects.md)
+> [!TIP]
+>
+> * If you already have an Azure Language in Foundry Tools or multi-service resource—whether used on its own or through Language Studio—you can continue to use those existing Language resources within the Microsoft Foundry portal.
+> * For more information, see [Connect services in the Microsoft Foundry portal](../../../../connect-services-foundry-portal.md).
+> * Consider using a Foundry resource for the best experience. You can also follow these instructions with a Language resource.
 
-## Navigate to the Foundry Playground
+* **Azure subscription**. If you don't have one, you can [create one for free](https://azure.microsoft.com/pricing/purchase-options/azure-account?cid=msft_learn).
+* **Requisite permissions**. Make sure the person establishing the account and project is assigned as the **Foundry Account Owner** role at the subscription level. Alternatively, having either the **Contributor** or **Cognitive Services Contributor** role at the subscription scope also meets this requirement. For more information, see [Role based access control (RBAC)](../../../../../ai-foundry/openai/how-to/role-based-access-control.md#cognitive-services-contributor).
+* **Foundry resource**. Create a [Foundry resource](../../../../multi-service-resource.md). Alternatively, you can use a [Language resource](https://portal.azure.com/?Microsoft_Azure_PIMCommon=true#create/Microsoft.CognitiveServicesTextAnalytics).
+* **A Foundry project**. For more information, see [Create a Foundry project](../../../../../ai-foundry/how-to/create-projects.md).
 
-Using the left side pane, select **Playgrounds**. Then select the **Try Azure Language Playground** button.
+## Role-based access control (RBAC) requirements
 
-:::image type="content" source="../../media/quickstarts/azure-ai-foundry/foundry-playground-navigation.png" alt-text="The development lifecycle" lightbox="../../media/quickstarts/azure-ai-foundry/foundry-playground-navigation.png":::
+Assign the correct roles to your user principal and project managed identity to access the Text Analytics for Health playground. Microsoft recommends using Microsoft Entra ID authentication, which enforces role-based restrictions. Key-based authentication grants full access without role checks and should be avoided in production environments.
 
-## Use Text Analytics for Health in the Foundry Playground
+> [!IMPORTANT]
+> The Foundry RBAC roles were recently renamed. **Foundry User**, **Foundry Owner**, **Foundry Account Owner**, and **Foundry Project Manager** were previously named Azure AI User, Azure AI Owner, Azure AI Account Owner, and Azure AI Project Manager. You might still see the previous names in some places while the rename rolls out. The role IDs and core permissions are unchanged.
 
-The **Language Playground** consists of four sections:
+* Assign the minimum required roles to both your user principal and project managed identity so they can access Foundry features.
+
+* Verify current assignments using [Check access for a user to a single Azure resource](/azure/role-based-access-control/check-access).
+
+### [New Foundry](#tab/new-foundry)
+
+> [!NOTE]
+> This content refers to the [new Foundry](https://ai.azure.com/) portal, which supports only [Foundry projects](../../../../../ai-foundry/what-is-foundry.md) and provides streamlined access to models, agents, and tools. To confirm that you're using new Foundry, make sure the version toggle in the portal banner is in the **on** position. :::image type="icon" source="../../media/quickstarts/azure-ai-foundry/new-foundry.png" border="false":::
+
+You can use [new Foundry playground](https://ai.azure.com/) to:
+
+> [!div class="checklist"]
+>
+> * Extract health entities from clinical text
+> * Review detected entities, categories, and confidence scores
+> * Return structured output in FHIR format
+
+## Navigate to the new Foundry playground
+
+The active project appears in the upper-left corner. To create a new project:
+
+1. Open the project drop-down menu.
+1. Enter a project name or select an existing one.
+1. Select **Create project**.
+
+   :::image type="content" source="../../../media/new-foundry-homepage.png" alt-text="Screenshot of the new Foundry homepage.":::
+
+There are two ways to access the Text Analytics for Health interface:
+
+1. Select the **Discover** tab from the upper right navigation bar to go to the **Models** page.
+   * In the search bar under models, enter **Azure** and press enter.
+   * Select **Text Analytics for Health** from the search results.
+   * Select the **Open in Playground** button.
+
+1. Select the **Build** tab from the upper right navigation bar.
+   * From the left navigation bar, select **Models**.
+   * Select the **AI services** tab.
+   * Select **Text Analytics for Health** to go to the playground.
+
+## Extract health information
+
+The **Text Analytics for Health** model identifies and extracts health-related entities and relationships from clinical and biomedical text. The playground provides configuration options to customize your preferences and detailed output to review detected entities and their confidence scores.
+
+1. On the **Playground** tab, select **Azure Language—Text Analytics for Health** from the drop-down menu.
+
+1. Select the sample text, use the paperclip icon to upload your text, or enter your own clinical text.
+
+1. In the **Configure** side panel, you can set the following options:
 
-* Top banner: You can select any of the currently available Languages here.
-* Right pane: This pane is where you can find the **Configuration** options for the service, such as the API and model version, along with features specific to the service.
-* Center pane: This pane is where you enter your text for processing. After the operation is run, some results are shown here.
-* Right pane: This pane is where **Details** of the run operation are shown.
+    | Option | Description |
+    | --- | --- |
+    | **API version** | Select the API version that you prefer to use. |
+    | **Model version** | Select the model version that you prefer to use. |
+    | **Language** | Select the language in which your source text is written. |
+    | **Return output in FHIR structure** | Returns the output in the Fast Healthcare Interoperability Resources (FHIR) structure. |
 
-Here you can select the Text Analytics for Health capability by choosing the top banner tile, **Extract health information**.
+1. After you make your selections, choose the **Detect** button. Detected entities are highlighted in the text and you can review the accompanying details in formatted text or as a JSON response.
 
-## Use Extract health information
+    | Field | Description |
+    | --- | --- |
+    | **Entity** | The detected entity. |
+    | **Category** | The type of entity that was detected. |
+    | **Confidence** | The model's level of certainty regarding whether it correctly identified an entity type. |
 
-**Extract health information** is designed to identify and extract health information in text.
+Verify that the detected entities match the health information in your input text. You can use the **Edit** button to modify the **Configure** parameters and rerun detection as needed.
 
-In **Configuration** there are the following options:
+### [Foundry (classic)](#tab/foundry-classic)
 
-|Option              |Description                              |
-|--------------------|-----------------------------------------|
-|Select API version  | Select which version of the API to use.    |
-|Select model version| Select which version of the model to use.|
-|Select text language| Select which language the language is input in.|
-|Return output in FHIR structure| Returns the output in the Fast Healthcare Interoperability Resources (FHIR) structure.|
+> [!NOTE]
+> This content refers to the [Foundry (classic)](https://ai.azure.com/) portal, which supports hub-based projects and other resource types. To confirm that you're using Foundry (classic), make sure the version toggle in the portal banner is in the **off** position. :::image type="icon" source="../../media/quickstarts/azure-ai-foundry/classic-foundry.png" border="false":::
 
-After your operation is completed, the type of entity is displayed beneath each entity in the center pane and the **Details** section contains the following fields for each entity:
+You can use [Foundry (classic)](https://ai.azure.com/) to:
 
-|Field | Description                |
-|------|----------------------------|
-|Entity|The detected entity.|
-|Category| The type of entity that was detected.|
-|Confidence| How confident the model is in the correctness of identification of entity's type.|
+> [!div class="checklist"]
+>
+> * Extract health entities from clinical text
+> * Review detected entities, categories, and confidence scores
+> * Return structured output in FHIR format
+
+## Navigate to the Foundry (classic) playground
+
+1. In the left pane, select **Playgrounds**.
+1. Select the **Try Azure Language Playground** button.
+
+:::image type="content" source="../../media/quickstarts/azure-ai-foundry/foundry-playground-navigation.png" alt-text="Screenshot showing the Playgrounds navigation and the Try Azure Language Playground button in Foundry (classic)." lightbox="../../media/quickstarts/azure-ai-foundry/foundry-playground-navigation.png":::
+
+## Extract health information in the Foundry (classic) playground
+
+The **Language Playground** consists of four sections:
+
+| Section | Purpose |
+| --- | --- |
+| **Top banner** | Select the input language and choose a Language capability. |
+| **Left pane** | Set **Configuration** options such as API version, model version, and output format. |
+| **Center pane** | Enter text for processing and review highlighted results. |
+| **Right pane** | View **Details** for each detected entity. |
+
+Select **Extract health information** from the top banner tiles to get started.
+
+In **Configuration** you can select from the following options:
+
+| Option | Description |
+| --- | --- |
+| Select API version | Select which version of the API to use. |
+| Select model version | Select which version of the model to use. |
+| Select text language | Select the language of your input text. |
+| Return output in FHIR structure | Returns the output in the Fast Healthcare Interoperability Resources (FHIR) structure. |
+
+After the operation completes, the type of entity is displayed beneath each entity in the center pane.
+
+The **Details** section contains the following fields for each entity:
+
+| Field | Description |
+| --- | --- |
+| Entity | The detected entity. |
+| Category | The type of entity that was detected. |
+| Confidence | The model's level of certainty that the entity type is correct. |
 
 :::image type="content" source="../../media/quickstarts/azure-ai-foundry/text-analytics-for-health.png" alt-text="A screenshot of an example of extract health information in Foundry portal." lightbox="../../media/quickstarts/azure-ai-foundry/text-analytics-for-health.png":::
+
+Verify that each health entity appears highlighted with the correct category label. If no entities appear, check that the input text contains recognizable health terminology and that the correct API version is selected.
+
+## Open in Visual Studio Code
+
+After validating your scenario in the playground, select **Open in VS Code** to carry your current configuration directly into a development environment—no manual setup required.
+
+1. Configure your scenario in the playground:
+   - Select your API version and model version.
+   - Enter and test your sample input.
+   - Adjust options such as entity types and FHIR output format.
+1. Select **Open in VS Code**.
+1. Visual Studio Code opens with a preconfigured code sample that reflects your playground configuration, including your API version, model, and health detection settings.
+
+> [!TIP]
+> Use the playground to compare outputs across API versions—for example, preview versus GA—before exporting your configuration to code.
+
+---
\ No newline at end of file

@@ -45,6 +45,8 @@ items:
       items:
       - name: Overview
         href: personally-identifiable-information/text-pii-overview.md
+      - name: Quickstart
+        href: personally-identifiable-information/text-pii-playground.md  
       - name: How-to guides
         items:
         - name: Detect and redact PII in text
@@ -74,6 +76,8 @@ items:
       items:
       - name: Overview
         href: personally-identifiable-information/conversation-pii-overview.md
+      - name: Quickstart
+        href: personally-identifiable-information/conversation-pii-playground.md  
       - name: How-to guides
         items:
         - name: Detect and redact PII in conversations
@@ -89,6 +93,8 @@ items:
       items:
       - name: Overview
         href: personally-identifiable-information/document-based-pii-overview.md
+      - name: Quickstart
+        href: personally-identifiable-information/document-based-pii-playground.md
       - name: How-to guides
         items:
         - name: Detect and redact PII in native documents
@@ -969,4 +975,4 @@ items:
       href: reference/migrate-language-service-latest.md
     - name: Azure Language release history
       displayName: changelog, release notes
-      href: reference/release-history.md
+      href: reference/release-history.md
\ No newline at end of file

@@ -6,14 +6,39 @@ author: laujan
 manager: nitinme
 ms.service: azure-ai-language
 ms.topic: whats-new
-ms.date: 03/17/2026
+ms.date: 05/19/2026
 ms.author: lajanuar
 ---
 <!-- markdownlint-disable MD025 -->
 # What's new in Azure Language in Foundry Tools?
 
 Stay informed about recent releases and enhancements designed to help you get the most out of Azure Language capabilities. Azure Language in Foundry Tools is updated on an ongoing basis. Bookmark this page and stay up to date with release notes, feature enhancements, and our newest documentation.
 
+## June 2026
+
+* **Text PII detection generally available (`2026-05-01`)**. The GA API delivers quality improvements across common entity types. The following capabilities, previously in preview, are now generally available:
+
+  * **Anonymization**. The `syntheticReplacement` [redaction policy](personally-identifiable-information/how-to/redact-text-pii.md#redaction-policies) masks detected entities with synthetic replacement values.
+  * **Disable type-validation enforcement**. Bypass strict [entity type validation](personally-identifiable-information/how-to/redact-text-pii.md#disableentityvalidation) when operational efficiency takes priority.
+  * **Confidence threshold score**. Set a minimum [confidence score](personally-identifiable-information/how-to/redact-text-pii.md#confidencescorethreshold) to filter output by detection confidence.
+  * **Exclude values** from PII output and use **entity synonyms** for tailored detection.
+
+* **New Text PII preview entities (`2026-04-15-preview`)**. The preview API adds support for Password, PIN code, Zip code, and Airport code entity types. For a full list, see [entity categories](personally-identifiable-information/concepts/entity-categories.md).
+
+* **Conversation PII improvements (`2026-04-15-preview`)**. A new preview model delivers quality improvements and expanded entity recognition, optimized for spoken-language patterns—including interruptions, filler words, and speaker turns common in transcripts and call recordings.
+
+* **PII detection capabilities available in new Foundry playgrounds**. Text PII detection, conversation PII detection, and document PII detection (preview) are now available in [new Foundry](https://ai.azure.com/). For more information, see:
+
+  * [Text PII detection](personally-identifiable-information/text-pii-playground.md)
+  * [Conversation PII detection](personally-identifiable-information/conversation-pii-playground.md)
+  * [Document PII detection](personally-identifiable-information/document-based-pii-playground.md) (preview)
+
+* **Text Analytics for Health available in new Foundry**. The Text Analytics for Health playground is now available in [new Foundry](https://ai.azure.com/). For more information, see the [Text Analytics for Health quickstart](text-analytics-for-health/quickstart.md).
+
+* **Language detection available in new Foundry**. The language detection playground is now available in [new Foundry](https://ai.azure.com/). For more information, see the [Language detection quickstart](language-detection/quickstart.md).
+
+* **Open in Visual Studio Code**. new Foundry playgrounds for language detection, text PII detection, conversation PII detection, and Text Analytics for Health now support **Open in VS Code**. Select the option in the playground to export your current configuration directly to a preconfigured code sample in Visual Studio Code.
+
 ## February 2026
 
 * **Text PII detection quality improvement**. Backend validation for the Phone Number entity type is updated to broaden detection coverage, resulting in improved recall across supported languages. This change is applied at the service level and requires no updates to your API calls or request parameters.