Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into perf-js

Author: pauljewellmsft

.openpublishing.publish.config.json

@@ -135,9 +135,9 @@
       "branch_mapping": {}
     },
     {
-      "path_to_root": "ms-identity-dotnetcore-b2c-account-management",
+      "path_to_root": "ms-identity-dotnetcore-b2c-account-management-archive",
       "url": "https://github.com/Azure-Samples/ms-identity-dotnetcore-b2c-account-management",
-      "branch": "master",
+      "branch": "archive",
       "branch_mapping": {}
     },
     {

.openpublishing.redirection.azure-monitor.json

@@ -6684,6 +6684,21 @@
             "redirect_url": "/azure/azure-monitor/monitor-azure-monitor-reference",
             "redirect_document_id": false
         },
+        {
+            "source_path_from_root": "/articles/azure-monitor/ai-ops/responsible-ai-faq.md",
+            "redirect_url": "/azure/copilot/overview",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/azure-monitor/ai-ops/investigator-overview.md",
+            "redirect_url": "/azure/copilot/overview",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/azure-monitor/ai-ops/investigate-alert-instance.md",
+            "redirect_url": "/azure/copilot/overview",
+            "redirect_document_id": false
+        },
         {
             "source_path_from_root": "/articles/azure-monitor/insights/resource-group-insights.md",
             "redirect_url": "/azure/azure-resource-manager/management/resource-group-insights",

articles/ai-services/.openpublishing.redirection.applied-ai-services.json

@@ -240,5 +240,15 @@
             "redirect_url": "/azure/ai-services/content-moderator/term-lists-quickstart-dotnet",
             "redirect_document_id": false
           },
+          {
+            "source_path_from_root": "/articles/ai-services/content-safety/concepts/incident-response.md",
+            "redirect_url": "/azure/ai-services/content-safety/concepts/custom-categories-rapid",
+            "redirect_document_id": true
+          },
+          {
+            "source_path_from_root": "/articles/ai-services/content-safety/how-to/incident-response.md",
+            "redirect_url": "/azure/ai-services/content-safety/how-to/custom-categories-rapid",
+            "redirect_document_id": true
+          }
 	]
 }

articles/ai-services/content-safety/concepts/incident-response.md renamed to articles/ai-services/content-safety/concepts/custom-categories-rapid.md

@@ -1,5 +1,5 @@
 ---
-title: "Incident response in Azure AI Content Safety"
+title: "Custom categories (rapid) in Azure AI Content Safety"
 titleSuffix: Azure AI services
 description: Learn about content incidents and how you can use Azure AI Content Safety to handle them on your platform.
 #services: cognitive-services
@@ -12,15 +12,15 @@ ms.date: 04/11/2024
 ms.author: pafarley
 ---
 
-# Incident response
+# Custom categories (rapid)
 
-In content moderation scenarios, incident response is the process of identifying, analyzing, containing, eradicating, and recovering from cyber incidents that involve inappropriate or harmful content on online platforms. 
+In content moderation scenarios, custom categories (rapid) is the process of identifying, analyzing, containing, eradicating, and recovering from cyber incidents that involve inappropriate or harmful content on online platforms. 
 
 An incident may involve a set of emerging content patterns (text, image, or other modalities) that violate Microsoft community guidelines or the customers' own policies and expectations. These incidents need to be mitigated quickly and accurately to avoid potential live site issues or harm to users and communities. 
 
-## Incident response API features
+## Custom categories (rapid) API features
 
-One way to deal with emerging content incidents is to use [Blocklists](/azure/ai-services/content-safety/how-to/use-blocklist), but that only allows exact text matching and no image matching. The Azure AI Content Safety incident response API offers the following advanced capabilities:
+One way to deal with emerging content incidents is to use [Blocklists](/azure/ai-services/content-safety/how-to/use-blocklist), but that only allows exact text matching and no image matching. The Azure AI Content Safety custom categories (rapid) API offers the following advanced capabilities:
 - semantic text matching using embedding search with a lightweight classifier
 - image matching with a lightweight object-tracking model and embedding search.
 
@@ -34,11 +34,11 @@ Then, you can include your defined incident in a regular text analysis or image
 
 ### Language availability
 
-The text incident response API supports all languages that are supported by Content Safety text moderation. See [Language support](/azure/ai-services/content-safety/language-support).
+The text custom categories (rapid) API supports all languages that are supported by Content Safety text moderation. See [Language support](/azure/ai-services/content-safety/language-support).
 
 ### Input limitations
 
-See the following table for the input limitations of the incident response API:
+See the following table for the input limitations of the custom categories (rapid) API:
 
 | Object     | Limitation      |
 | :------------ | :----------- |
@@ -56,6 +56,6 @@ To use this API, you must create your Azure AI Content Safety resource in one of
 
 ## Next steps
 
-Follow the how-to guide to use the Azure AI Content Safety incident response API.
+Follow the how-to guide to use the Azure AI Content Safety custom categories (rapid) API.
 
-* [Use the incident response API](../how-to/incident-response.md)
+* [Use the custom categories (rapid) API](../how-to/custom-categories-rapid.md)

articles/ai-services/content-safety/faq.yml

@@ -27,7 +27,7 @@ sections:
 
           - Azure Content Moderator uses binary classification for each content type (such as `profanity` or `adult`), while Azure AI Content Safety uses multiple classes (such as `sexual`, `violent`, `hate`, and `self-harm`) with different severity levels.
           - Azure AI Content Safety supports multilingual content moderation in English, German, Japanese, Spanish, French, Italian, Portuguese, and Chinese, while Azure Content Moderator's AI classifiers only support English.
-          - Azure Content Moderator has a built-in term list and a custom term list feature, while Azure AI Content Safety does not have a built-in term list but relies on advanced language and vision models to detect harmful content. It also provides a custom term list feature for incident response and customization.
+          - Azure Content Moderator has a built-in term list and a custom term list feature, while Azure AI Content Safety does not have a built-in term list but relies on advanced language and vision models to detect harmful content. It also provides a custom term list feature for customization.
           - Azure AI Content Safety has an interactive studio for exploring and testing the service capabilities, while Azure Content Moderator does not.
       - question: |
           Why should I migrate from Azure Content Moderator to Azure AI Content Safety?

articles/ai-services/content-safety/how-to/incident-response.md renamed to articles/ai-services/content-safety/how-to/custom-categories-rapid.md

@@ -1,7 +1,7 @@
 ---
-title: "Use the incident response API"
+title: "Use the custom categories (rapid) API"
 titleSuffix: Azure AI services
-description: Learn how to use the incident response API to mitigate harmful content incidents quickly.
+description: Learn how to use the custom categories (rapid) API to mitigate harmful content incidents quickly.
 #services: cognitive-services
 author: PatrickFarley
 manager: nitinme
@@ -13,9 +13,9 @@ ms.author: pafarley
 ---
 
 
-# Use the incident response API
+# Use the custom categories (rapid) API
 
-The incident response API lets you quickly respond to emerging harmful content incidents. You can define an incident with a few examples in a specific topic, and the service will start detecting similar content.
+The custom categories (rapid) API lets you quickly respond to emerging harmful content incidents. You can define an incident with a few examples in a specific topic, and the service will start detecting similar content.
 
 Follow these steps to define an incident with a few examples of text content and then analyze new text content to see if it matches the incident.
 
@@ -37,7 +37,7 @@ Follow these steps to define an incident with a few examples of text content and
 
 <!--tbd env vars-->
 
-## Test the text incident response API
+## Test the text custom categories (rapid) API
 
 Use the sample code in this section to create a text incident, add samples to the incident, deploy the incident, and then detect text incidents.
 
@@ -231,7 +231,7 @@ print(response.text)
 ```
 ---
 
-## Test the image incident response API
+## Test the image custom categories (rapid) API
 
 Use the sample code in this section to create an image incident, add samples to the incident, deploy the incident, and then detect image incidents.
 
@@ -801,5 +801,5 @@ print(response.text)
 
 ## Related content
 
-- [Incident response concepts](../concepts/incident-response.md)
+- [Custom categories (rapid) concepts](../concepts/custom-categories-rapid.md)
 - [What is Azure AI Content Safety?](../overview.md)

articles/ai-services/content-safety/overview.md

@@ -50,7 +50,7 @@ There are different types of analysis available from this service. The following
 | Prompt Shields (preview) | Scans text for the risk of a [User input attack](./concepts/jailbreak-detection.md) on a Large Language Model. [Quickstart](./quickstart-jailbreak.md) |
 | Groundedness detection (preview) | Detects whether the text responses of large language models (LLMs) are grounded in the source materials provided by the users. [Quickstart](./quickstart-groundedness.md) |
 | Protected material text detection (preview) | Scans AI-generated text for known text content (for example, song lyrics, articles, recipes, selected web content). [Quickstart](./quickstart-protected-material.md)|
-| Incident response API (preview) | Lets you define [emerging harmful content patterns](./concepts/incident-response.md) and scan text and images for matches. [How-to guide](./how-to/incident-response.md) |
+| Custom categories (rapid) API (preview) | Lets you define [emerging harmful content patterns](./concepts/custom-categories-rapid.md) and scan text and images for matches. [How-to guide](./how-to/custom-categories-rapid.md) |
 
 ## Content Safety Studio
 

articles/ai-services/content-safety/toc.yml

@@ -47,7 +47,7 @@ items:
   - name: Use a blocklist
     href: how-to/use-blocklist.md
   - name: Handle harmful content incidents
-    href: how-to/incident-response.md
+    href: how-to/custom-categories-rapid.md
   - name: Encryption of data at rest
     href: how-to/encrypt-data-at-rest.md
   - name: Migrate from public preview to GA
@@ -64,8 +64,8 @@ items:
     href: concepts/jailbreak-detection.md
   - name: Groundedness detection
     href: concepts/groundedness.md
-  - name: Incident response
-    href: concepts/incident-response.md
+  - name: Custom categories (rapid)
+    href: concepts/custom-categories-rapid.md
 - name: Reference
   items:
   - name: Azure AI Content Safety REST API

articles/ai-services/content-safety/whats-new.md

@@ -19,9 +19,9 @@ Learn what's new in the service. These items might be release notes, videos, blo
 ## May 2024
 
 
-### Incident response API
+### Custom categories (rapid) API
 
-The incident response API lets you quickly define emerging harmful content patterns and scan text and images for matches. See [Incident response](./concepts/incident-response.md) to learn more.
+The custom categories (rapid) API lets you quickly define emerging harmful content patterns and scan text and images for matches. See [Custom categories (rapid)](./concepts/custom-categories-rapid.md) to learn more.
 
 ## March 2024
 

articles/ai-services/document-intelligence/concept-add-on-capabilities.md

@@ -54,7 +54,9 @@ Document Intelligence supports more sophisticated and modular analysis capabilit
 
 > [!NOTE]
 >
-> Not all add-on capabilities are supported by all models. For more information, *see* [model data extraction](concept-model-overview.md#model-analysis-features).
+> * Not all add-on capabilities are supported by all models. For more information, *see* [model data extraction](concept-model-overview.md#model-analysis-features).
+>
+> * Add-on capabilities are currently not supported for Microsoft Office file types.
 
 The following add-on capabilities are available for`2024-02-29-preview`, `2024-02-29-preview`, and later releases: