Merge pull request #1831 from MicrosoftDocs/main

12/4/2024 PM Publish

Author: Taojunshen

articles/ai-services/language-service/personally-identifiable-information/overview.md

@@ -14,11 +14,16 @@ ms.custom: language-service-pii, build-2024, ignite-2024
 
 # What is Personally Identifiable Information (PII) detection in Azure AI Language?
 
-As of June 2024, we now provide General Availability support for the Conversational PII service (English-language only).
-Customers can now redact transcripts, chats, and other text written in a conversational style (i.e. text with “um”s, “ah”s, multiple speakers, and the spelling out of words for more clarity) with better confidence in AI quality, Azure SLA support and production environment support, and enterprise-grade security in mind.
-
 PII detection is one of the features offered by [Azure AI Language](../overview.md), a collection of machine learning and AI algorithms in the cloud for developing intelligent applications that involve written language. The PII detection feature can **identify, categorize, and redact** sensitive information in unstructured text. For example: phone numbers, email addresses, and forms of identification. Azure AI Language supports general text PII redaction, as well as [Conversational PII](how-to-call-for-conversations.md), a specialized model for handling speech transcriptions and the more informal, conversational tone of meeting and call transcripts. The service also supports [Native Document PII redaction](#native-document-support), where the input and output are structured document files.
 
+## What's new
+
+The Text PII and Conversational PII detection preview API (version `2024-11-15-preview`) now supports the option to mask detected sensitive entities with a label beyond just redaction characters. Customers have the option to specify if personally identifiable information content such as names and phone numbers, i.e. `“John Doe received a call from 424-878-9192”`, are masked with a redaction character, i.e. `“******** received a call from ************”`, or masked with an entity label, i.e. `“[PERSON_1] received a call from [PHONENUMBER_1]”`. More on how to specify the redaction policy style for your outputs can be found in our [how-to guides](how-to-call.md). 
+
+The Conversational PII detection models (both version `2024-11-01-preview` and `GA`) have been updated to provide enhanced AI quality and accuracy. The numeric identifier entity type now also includes Drivers License and Medicare Beneficiary Identifier.
+
+As of June 2024, we now provide General Availability support for the Conversational PII service (English-language only). Customers can now redact transcripts, chats, and other text written in a conversational style (i.e. text with “um”s, “ah”s, multiple speakers, and the spelling out of words for more clarity) with better confidence in AI quality, Azure SLA support and production environment support, and enterprise-grade security in mind.
+
 > [!TIP]
 > Try out PII detection [in AI Foundry portal](https://ai.azure.com/explore/language), where you can [utilize a currently existing Language Studio resource or create a new AI Foundry resource](../../../ai-studio/ai-services/connect-ai-services.md)
 

articles/ai-services/language-service/summarization/region-support.md

@@ -22,28 +22,28 @@ Some summarization features are only available in limited regions. More regions
 |------------------|----------------------------------|-----------------------------------------------|
 |US Gov Virginia   |✅                           |✅                                        |
 |US Gov Arizona    |✅                           |✅                                        |
-|North Europe      |✅                           |✅                                        |
+|Australia East    |✅                           |✅                                        |
+|Canada Central    |✅                           |✅                                        |
+|Central US        |✅                           |✅                                        |
+|China North 3     |✅                           |✅                                        |
 |East US           |✅                           |✅                                        |
 |East US 2         |✅                           |✅                                        |
-|Central US        |✅                           |✅                                        |
+|France Central    |✅                           |✅                                        |
+|Italy North       |✅                           |✅                                        |
+|Japan East        |✅                           |✅                                        |
+|North Central US  |✅                           |✅                                        |
+|North Europe      |✅                           |✅                                        |
 |South Central US  |✅                           |✅                                        |
-|West US           |✅                           |✅                                        |
-|West US 2         |✅                           |✅                                        |
+|South UK          |✅                           |✅                                        |
+|Southeast Asia    |✅                           |✅                                        |
+|Switzerland North |✅                           |✅                                        |
 |USNat East        |✅                           |✅                                        |
 |USNat West        |✅                           |✅                                        |
 |USSec East        |✅                           |✅                                        |
 |USSec West        |✅                           |✅                                        |
-|South UK          |✅                           |✅                                        |
-|Southeast Asia    |✅                           |✅                                        |
-|Australia East    |✅                           |✅                                        |
-|France Central    |✅                           |✅                                        |
-|Japan East        |✅                           |✅                                        |
-|North Central US  |✅                           |✅                                        |
-|Central Sweden    |✅                           |✅                                        |
-|Switzerland North |✅                           |✅                                        |
 |West Europe       |✅                           |✅                                        |
-|Italy North       |✅                           |✅                                        |
-|China North 3     |✅                           |✅                                        |
+|West US           |✅                           |✅                                        |
+|West US 2         |✅                           |✅                                        |
 
 ## Next steps
 

articles/ai-services/openai/how-to/business-continuity-disaster-recovery.md

@@ -59,7 +59,8 @@ By default, the Azure OpenAI service provides a [default SLA](https://www.micros
 
 The additional benefit of this architecture is that it allows you to stack Standard deployments with Provisioned Deployments so that you can dial in your preferred level of performance and resiliency. This allows you to use PTU for your baseline demand across workloads and leverage pay-as-you-go for spikes in traffic.
 
-:::image type="content" source="../how-to/media/disaster-recovery/recovery.jpg" alt-text="Failover architectural diagram." lightbox="../how-to/media/disaster-recovery/recovery.jpg":::
+:::image type="content" source="../how-to/media/disaster-recovery/scaling.jpg" alt-text="Provisioned scaling diagram." lightbox="../how-to/media/disaster-recovery/scaling.jpg":::
+
 
 ## Supporting Infrastructure
 
@@ -70,9 +71,11 @@ The infrastructure that supports the Azure OpenAI architecture needs to be consi
 Organizations consuming the service through the Microsoft public backbone should consider the following design elements:
 
 1. The Generative AI Gateway should be deployed in manner that ensures it's available in the event of an Azure regional outage. If using APIM (Azure API Management), this can be done by deploying separate APIM instances in multiple regions or using the [multi-region gateway feature of APIM](/azure/api-management/api-management-howto-deploy-multi-region).
+
 1. A public global server load balancer should be used to load balance across the multiple Generative AI Gateway instances in either an active/active or active/passive manner. [Azure FrontDoor](/azure/traffic-manager/traffic-manager-routing-methods) can be used to fulfill this role depending on the organization’s requirements.
 
-:::image type="content" source="../how-to/media/disaster-recovery/scaling.jpg" alt-text="Provisioned scaling diagram." lightbox="../how-to/media/disaster-recovery/scaling.jpg":::
+:::image type="content" source="../how-to/media/disaster-recovery/recovery.png" alt-text="Failover architectural diagram." lightbox="../how-to/media/disaster-recovery/recovery.png":::
+
 
 ### Designing for consumption through the private networking