Skip to content

Commit 116a11c

Browse files
authored
Merge pull request #6165 from PatrickFarley/openai-rai
bala's rAPI updates
2 parents cda3df7 + c3bc2c1 commit 116a11c

File tree

2 files changed

+6
-4
lines changed

2 files changed

+6
-4
lines changed

articles/ai-foundry/responsible-ai/openai/data-privacy.md

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ Azure OpenAI processes the following types of data:
3434

3535
- **Prompts and generated content**. Prompts are submitted by the user, and content is generated by the service, via the completions, chat completions, images, and embeddings operations.
3636
- **Uploaded data**. You can provide your own data for use with certain service features (e.g., [fine-tuning](/azure/ai-services/openai/how-to/fine-tuning?pivots=programming-language-studio), [assistants API](/azure/ai-services/openai/how-to/batch?tabs=standard-input&pivots=programming-language-ai-studio), [batch processing](/azure/ai-services/openai/how-to/batch?tabs=standard-input&pivots=programming-language-ai-studio)) using the Files API or vector store.
37-
- **Data for stateful entities**. When you use certain optional features of Azure OpenAI service, such as the Threads feature of the [Assistants API](/azure/ai-services/openai/how-to/assistant) and Stored completions, the service creates a data store to persist message history and other content, in accordance with how you configure the feature.
37+
- **Data for stateful entities**. When you use certain optional features of Azure OpenAI, such as the [Responses API](/azure/ai-services/openai/how-to/responses), the Threads feature of the [Assistants API](/azure/ai-services/openai/how-to/assistant), and Stored completions, the service creates a data store to persist message history and other content, in accordance with how you configure the feature.
3838
- **Augmented data included with or via prompts**. When you use data associated with stateful entities, the service retrieves relevant data from a configured data store and augments the prompt to produce generations that are grounded with your data. Prompts may also be augmented with data retrieved from a source included in the prompt itself, such as a URL.
3939
- **Training & validation data**. You can provide your own training data consisting of prompt-completion pairs for the purposes of [fine-tuning an OpenAI model](/azure/ai-services/openai/how-to/fine-tuning?pivots=programming-language-studio).
4040

@@ -44,11 +44,12 @@ The diagram below illustrates how your data is processed. This diagram covers se
4444

4545
1. How the Azure OpenAI Service processes your prompts via inferencing to generate content (including when additional data from a designated data source is added to a prompt using Azure OpenAI on your data, Assistants, or batch processing).
4646
1. How the Assistants feature stores data in connection with Messages, Threads, and Runs.
47+
1. How the Responses API feature stores data to persist message history.
4748
1. How the Batch feature processes your uploaded data.
4849
1. How the Azure OpenAI Service creates a fine-tuned (custom) model with your uploaded data.
4950
1. How the Azure OpenAI Service and Microsoft personnel analyze prompts and completions (text and image) for harmful content and for patterns suggesting the use of the service in a manner that violates the Code of Conduct or other applicable product terms.
5051

51-
:::image type="content" source="media\flow.jpg" alt-text="Data flow diagram for the service." lightbox="media\flow.jpg":::
52+
:::image type="content" source="media\flow-2.jpg" alt-text="Data flow diagram for the service." lightbox="media\flow-2.jpg":::
5253

5354
As depicted in the diagram above, managed customers may [apply to modify abuse monitoring](https://customervoice.microsoft.com/Pages/ResponsePage.aspx?id=v4j5cvGGr0GRqy180BHbR7en2Ais5pxKtso_Pz4b1_xUOE9MUTFMUlpBNk5IQlZWWkcyUEpWWEhGOCQlQCN0PWcu).
5455

@@ -70,9 +71,9 @@ The Azure OpenAI "on your data" feature lets you connect data sources to ground
7071

7172
### Data storage for Azure OpenAI Service features
7273

73-
Some Azure OpenAI Service features store data in the service. This data is either uploaded by the customer, using the Files API or vector store, or is automatically stored in connection with certain stateful entities such as the Threads feature of the Assistants API and Stored completions. Data stored for Azure OpenAI Service features:
74+
Some Azure OpenAI Service features store data in the service. This data is either uploaded by the customer, using the Files API or vector store, or is automatically stored in connection with certain stateful entities such as the Responses API, the Threads feature of the Assistants API, and Stored completions. Data stored for Azure OpenAI Service features:
7475
- Is stored at rest in the Azure OpenAI resource in the customer's Azure tenant, within the same [geography](https://azure.microsoft.com/explore/global-infrastructure/geographies/) as the Azure OpenAI resource;
75-
- Is always encrypted at rest with Microsoft’s AES-256-encryption by default, with the option of using a customer managed key (certain preview features may not support customer managed keys).
76+
- Is always encrypted at rest with Microsoft’s AES-256-encryption by default, with the option of using a customer managed key (certain preview features may not support customer-managed keys). Microsoft-managed keys are always used to ensure baseline encryption for all stored data.
7677
- Can be deleted by the customer at any time.
7778

7879
> [!NOTE]
@@ -82,6 +83,7 @@ Stored data may be used with the following service features/capabilities:
8283
- **Creating a customized (fine-tuned) model**. Learn more about [how fine-tuning works](/azure/ai-services/openai/how-to/fine-tuning?tabs=turbo%2Cpython-new&pivots=programming-language-studio). Fine-tuned models are exclusively available to the customer whose data was used to create the fine-tuned model, are encrypted at rest (when not deployed for inferencing), and can be deleted by the customer at any time. Training data uploaded for fine-tuning is not used to train, retrain, or improve any Microsoft or third party base models.
8384
- **Batch processing**. Learn more about [how batch processing works](https://aka.ms/aoai-batch-how-to). Batch processing is a Global deployment type; data stored at rest remains in the designated Azure geography until processing capacity becomes available; processing may occur in any geography where the relevant Azure OpenAI model is deployed (learn more about [region availability of models](/azure/ai-services/openai/concepts/models#model-summary-table-and-region-availability)).
8485
- **Assistants API (preview)**. Learn more about [how the Assistants API works](/azure/ai-services/openai/concepts/assistants). Some features of Assistants, such as Threads, store message history and other content.
86+
- **Responses API (preview)**. Learn more about [how the Responses API works](/azure/ai-services/openai/how-to/responses?tabs=python-secure). This API stores message history and other content related to message history. This is required for multi-turn conversations and workflows.
8587
- **Stored completions (preview)**. <!--Learn more about Stored completions. (link)--> Stored completions stores input-output pairs from the customer’s deployed Azure OpenAI models such as GPT-4o through the chat completions API and displays the pairs in the [Azure AI Foundry portal](https://ai.azure.com/). This allows customers to build datasets with their production data, which can then be used for evaluating or fine-tuning models (as permitted in applicable Product Terms).
8688

8789

218 KB
Loading

0 commit comments

Comments
 (0)