Merge pull request #5482 from PatrickFarley/rai-auto-migration

update docs from Build

Author: JillGrant615

articles/ai-foundry/responsible-ai/agents/transparency-note.md

@@ -291,12 +291,12 @@ We are committed to continuously improving our fairness evaluations to gain a de
 ## Evaluating and integrating Image Analysis for your use
 
 
-When integrating Content Understanding for your use case, knowing that Content Understanding is subject to the [Microsoft Generative AI Services Code of Conduct](/azure/ai-foundry/responsible-ai/openai/code-of-conduct), and [Code of Conduct for Azure AI Vision Face](/legal/ai-code-of-conduct?context=%2Fazure%2Fai-services%2Fcomputer-vision%2Fcontext%2Fcontext) will ensure a successful integration. 
+When integrating Content Understanding for your use case, knowing that Content Understanding is subject to the [Microsoft Generative AI Services Code of Conduct](/legal/ai-code-of-conduct) will ensure a successful integration. 
 
 When you're getting ready to integrate Content Understanding to your product or features, the following activities help to set you up for success: 
 - **Understand what it can do**: Fully assess the potential of Content Understanding to understand its capabilities and limitations. Understand how it will perform in your scenario and context. For example, if you're using audio content extraction, test with real-world recordings from your business processes to analyze and benchmark the results against your existing process metrics. 
 - **Respect an individual's right to privacy**: Only collect data and information from individuals from whom you have obtained consent, and for lawful and justifiable purposes. 
-- **Legal and regulatory considerations**. Organizations need to evaluate potential specific legal and regulatory obligations when using Content Understanding. Content Understanding is not appropriate for use in every industry or scenario. Always use Content Understanding in accordance with the applicable terms of service and the [Microsoft Generative AI Services Code of Conduct](/azure/ai-foundry/responsible-ai/openai/code-of-conduct).  
+- **Legal and regulatory considerations**. Organizations need to evaluate potential specific legal and regulatory obligations when using Content Understanding. Content Understanding is not appropriate for use in every industry or scenario. Always use Content Understanding in accordance with the applicable terms of service and the [Microsoft Generative AI Services Code of Conduct](/legal/ai-code-of-conduct).  
 - **Human-in-the-loop**: Keep a human in the loop, and include human oversight as a consistent pattern area to explore. This means ensuring constant human oversight of the AI-powered product or feature and to maintain the role of humans in decision-making. Ensure that you can have real-time human intervention in the solution to prevent harm. A human in the loop enables you to manage situations when Content Understanding does not perform as required. 
 - **Security**: Ensure your solution is secure and that it has adequate controls to preserve the integrity of your content and prevent unauthorized access. 
 

articles/ai-foundry/responsible-ai/content-understanding/transparency-note.md

@@ -5,42 +5,42 @@ keywords: Code of Conduct for Azure OpenAI Service
 author: mrbullwinkle
 ms.author: mbullwin
 ms.service: azure-ai-openai
-ms.topic: article
 ms.reviewer: nitinme
+ms.topic: article
 ms.date: 05/21/2024
 ---
 
 # Customer Copyright Commitment Required Mitigations
 
 > [!NOTE]
-> The requirements described below apply only to customers using Azure OpenAI Service and other Covered Products with configurable Metaprompts or other safety systems ("Configurable GAI Services"). They do not apply to customers using other Covered Products including Copilots with safety systems that are fixed.
+> The requirements described below apply only to customers using Azure OpenAI in Azure AI Foundry Models ("Azure OpenAI") and other Covered Products with configurable Metaprompts or other safety systems ("Configurable GAI Services"). They do not apply to customers using other Covered Products including Copilots with safety systems that are fixed. As of the publication date above, the only Configurable GAI Services are Microsoft Copilot Studio and GitHub Copilot; the Universal Required Mitigations do not apply to these offerings, but service-specific mitigations apply instead.  
 
-The Customer Copyright Commitment ("CCC") is a provision in the Microsoft Product Terms that describes Microsoft's obligation to defend customers against certain third-party intellectual property claims relating to Output Content. For Azure OpenAI Service and any Configurable GAI Service, Customer also must have implemented all mitigations required by the Azure OpenAI Service documentation in the offering that delivered the Output Content that is the subject of the claim. The required mitigations to maintain CCC coverage are set forth below.
+The Customer Copyright Commitment ("CCC") is a provision in the Microsoft Product Terms that describes Microsoft's obligation to defend customers against certain third-party intellectual property claims relating to Output Content. For Azure OpenAI and any Configurable GAI Service, Customer also must have implemented all mitigations required by the Azure OpenAI documentation in the offering that delivered the Output Content that is the subject of the claim. The required mitigations to maintain CCC coverage are set forth below.
 
-This page describes only the required mitigations necessary to maintain CCC coverage for Azure OpenAI Service and Configurable GAI Services. It is not an exhaustive list of requirements or mitigations required to use Azure OpenAI Service (or Configurable GAI Services) responsibly in compliance with the documentation. Azure OpenAI Service customers must comply with the [Code of Conduct](/azure/ai-foundry/responsible-ai/openai/code-of-conduct?context=/azure/ai-services/openai/context/context) at all times.
+This page describes only the required mitigations necessary to maintain CCC coverage for Azure OpenAI and Configurable GAI Services. It is not an exhaustive list of requirements or mitigations required to use Azure OpenAI (or Configurable GAI Services) responsibly in compliance with the documentation. Azure OpenAI customers must comply with the [Code of Conduct](/legal/ai-code-of-conduct) at all times.
 
-The section "Required Mitigations for GitHub Offerings" are the only requirements that apply to GitHub offerings, and separately took effect on November 1, 2023. The other mitigations below took effect on the dates indicated. For new Configurable GAI Services, features, models, or use cases, new CCC requirements will be posted and take effect at or following the launch of such Configurable GAI Service, feature, model, or use case. Otherwise, customers will have six months from the date of publication on this page to implement any new mitigations required to maintain coverage under the CCC. The Effective Date indicates when the mitigation must be deployed. If a customer tenders a claim for defense, the customer will be required to demonstrate compliance with all relevant requirements, both on this page and as listed in the Product Terms.
+The mitigations below take effect on the dates indicated. For new Configurable GAI Services, features, models, or use cases, new CCC requirements will be posted and take effect at or following the launch of such Configurable GAI Service, feature, model, or use case. Otherwise, customers will have six months from the date of publication on this page to implement any new mitigations required to maintain coverage under the CCC. The Effective Date indicates when the mitigation must be deployed. If a customer tenders a claim for defense, the customer will be required to demonstrate compliance with all relevant requirements, both on this page and as listed in the Product Terms.
 
 ## Universal Required Mitigations
 
-Universal required mitigations must be implemented to maintain CCC coverage for all offerings delivering Output Content from Azure OpenAI Service and Configurable GAI Services, with the exception of GitHub Offerings. The requirements are set forth here:
+Universal required mitigations must be implemented to maintain CCC coverage for all offerings delivering Output Content from Azure OpenAI and Configurable GAI Services, with the exceptions of GitHub Offerings and Microsoft Copilot Studio. The requirements are set forth here:
 
-**Azure OpenAI Service & Configurable GAI Services - Universal Required Mitigations:**
+**Azure OpenAI & Configurable GAI Services - Universal Required Mitigations:**
 
 |**Category**|**Required Mitigation**|**Effective Date**|
 |---|---|---|
 | Metaprompt | The customer offering must include a metaprompt directing the model to prevent copyright infringement in its output, for example, the sample metaprompt, "To Avoid Copyright Infringements" at: [System message framework and template recommendations for Large Language Models(LLMs)](/azure/ai-services/openai/concepts/system-message)|December 1, 2023|
-| Testing and Evaluation Report | The customer offering must have been subjected to evaluations (e.g., guided red teaming, systematic measurement, or other equivalent approach) by the customer using tests designed to detect the output of third-party content. Significant ongoing reproduction of third-party content determined through evaluation must be addressed. The report of results and mitigations must be retained by the customer and provided to Microsoft in the event of a claim. Customer is under no obligation to conduct direct testing of Microsoft services to maintain CCC coverage. More information on guided red teaming is at: [Red teaming large language models (LLMs)](/azure/ai-services/openai/concepts/red-teaming). More information on systematic measurement is at: [Overview of Responsible AI practices for Azure OpenAI models - Azure AI services - Microsoft Learn.](overview.md) |December 1, 2023|
+| Testing and Evaluation Report | The customer offering must have been subjected to evaluations (e.g., guided red teaming, systematic measurement, or other equivalent approach) by the customer using tests designed to detect the output of third-party content. Significant ongoing reproduction of third-party content determined through evaluation must be addressed. The report of results and mitigations must be retained by the customer and provided to Microsoft in the event of a claim. Customer is under no obligation to conduct direct testing of Microsoft services to maintain CCC coverage. More information on guided red teaming is at: [Red teaming large language models (LLMs)](/azure/ai-services/openai/concepts/red-teaming). More information on systematic measurement is at: [Overview of Responsible AI practices for Azure OpenAI models - Azure AI services - Microsoft Learn.](./overview.md) |December 1, 2023|
 
-## Additional Required Mitigations Per Azure OpenAI Service Use Case
+## Additional Required Mitigations Per Azure OpenAI Use Case
 
-Additional required mitigations are required to maintain CCC coverage for offerings delivering Output Content from Azure OpenAI Service, depending on what use cases the customer is using. As used below, “use case” refers to a major intended use of your application by your users. Use cases may have been indicated on a Limited Access Form. More information about use cases is available at: [Transparency Note for Azure OpenAI - Azure AI services | Microsoft Learn](transparency-note.md). Requirements are cumulative, meaning that the customer offering must include the required mitigations for all use cases. These additional requirements do not apply to Configurable GAI Services, only Azure OpenAI Service.
+Additional required mitigations are required to maintain CCC coverage for offerings delivering Output Content from Azure OpenAI, depending on what use cases the customer is using. As used below, “use case” refers to a major intended use of your application by your users. Use cases may have been indicated on a Limited Access Form. More information about use cases is available at: [Transparency Note for Azure OpenAI - Azure AI services | Microsoft Learn](./transparency-note.md). Requirements are cumulative, meaning that the customer offering must include the required mitigations for all use cases. These additional requirements do not apply to Configurable GAI Services, only Azure OpenAI.
 
 Not all content types can be generated by every application. The following required mitigations must be enabled for any use case described below. Azure OpenAI content filters include protected material detection and Prompt Shield. Protected material detection can analyze both text and code. Different filters must be on depending on content type.
 
 The required mitigations are set forth here:
 
-**Azure OpenAI Service Only - Additional Required Mitigations Per Use Case**
+**Azure OpenAI Only - Additional Required Mitigations Per Use Case**
 
 **Text and Code Use Cases:**
 
@@ -64,3 +64,14 @@ The below are the only required mitigations that apply to GitHub Offerings, and
 |**Category**|**Required Mitigation**|**Effective Date**|
 |---|---|---|
 |GitHub Offerings| Either the Duplicate Detection filtering feature must be set to the "Block" setting, or, if using annotate mode, customers must comply with cited licenses. Customers can learn how to enable the Duplicate Detection filter at [https://gh.io/cfb-dd](https://gh.io/cfb-dd).|November 1, 2023|
+
+
+## Required Mitigations for Microsoft Copilot Studio
+
+The below are the only required mitigations that apply to Microsoft Copilot Studio. 
+
+**Required Mitigations for Copilot Studio Only**
+
+|**Category**|**Required Mitigation**|**Effective Date**|
+|---|---|---|
+| Bring your own model |  If Customer chooses to connect to or incorporate a model hosted outside of Copilot Studio, the Output Content from such model is not covered by the CCC unless such model runs in Azure OpenAI and meets the required mitigations on this page for Azure OpenAI. |June 1, 2025 |