Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into migrate-server-articles-3

Author: paulth1

.openpublishing.publish.config.json

@@ -1215,6 +1215,7 @@
   ".openpublishing.redirection.container-service.json",
   ".openpublishing.redirection.defender-for-cloud.json",
   ".openpublishing.redirection.defender-for-iot.json",
+  ".openpublishing.redirection.guidance.json",
   ".openpublishing.redirection.iot-hub-device-update.json",
   ".openpublishing.redirection.key-vault.json",
   ".openpublishing.redirection.machine-configuration.json",
@@ -1233,6 +1234,7 @@
   "articles/ai-services/.openpublishing.redirection.cognitive-services.json",
   "articles/ai-studio/.openpublishing.redirection.ai-studio.json",
   "articles/azure-fluid-relay/.openpublishing.redirection.fluid-relay.json",
+  "articles/azure-functions/.openpublishing.redirection.azure-functions.json",
   "articles/azure-netapp-files/.openpublishing.redirection.azure-netapp-files.json",
   "articles/azure-relay/.openpublishing.redirection.relay.json",
   "articles/azure-video-analyzer/.openpublishing.redirection.azure-video-analyzer.json",

.openpublishing.redirection.guidance.json

@@ -108,6 +108,7 @@ The following table lists the claim resolvers with information about the OpenID
 | {OIDC:Resource} |The `resource`  query string parameter. | N/A |
 | {OIDC:Scope} |The `scope`  query string parameter. | openid |
 | {OIDC:Username}| The [resource owner password credentials flow](add-ropc-policy.md) user's username.| [email protected]|
+| {OIDC:IdToken} | The `id token`  query string parameter. | N/A |
 
 Check out the [Live demo](https://github.com/azure-ad-b2c/unit-tests/tree/main/claims-resolver#openid-connect-relying-party-application) of the OpenID Connect claim resolvers.
 

.openpublishing.redirection.json

@@ -1,5 +1,5 @@
 ---
-title: "Configure secure access with managed identities and private endpoints"
+title: "Configure secure access with managed identities and virtual networks"
 titleSuffix: Azure AI services
 description: Learn how to configure secure communications between Document Intelligence and other Azure Services.
 author: laujan
@@ -14,7 +14,7 @@ monikerRange: '<=doc-intel-4.0.0'
 ---
 
 
-# Configure secure access with managed identities and private endpoints
+# Configure secure access with managed identities and virtual networks
 
 [!INCLUDE [applies to v4.0, v3.1, v3.0, and v2.1](includes/applies-to-v40-v31-v30-v21.md)]
 
@@ -28,7 +28,7 @@ This how-to guide walks you through the process of enabling secure connections f
 
  You're setting up your environment to secure the resources:
 
-  :::image type="content" source="media/managed-identities/secure-config.png" alt-text="Screenshot of secure configuration with managed identity and private endpoints.":::
+  :::image type="content" source="media/managed-identities/secure-config-di.png" alt-text="Screenshot of secure configuration with managed identity and virtual networks.":::
 
 ## Prerequisites
 
@@ -64,7 +64,7 @@ Configure each of the resources to ensure that the resources can communicate wit
 
 You now have a working implementation of all the components needed to build a Document Intelligence solution with the default security model:
 
-  :::image type="content" source="media/managed-identities/default-config.png" alt-text="Screenshot of default security configuration.":::
+  :::image type="content" source="media/managed-identities/default-config-di.png" alt-text="Screenshot of default security configuration.":::
 
 Next, complete the following steps:
 
@@ -74,7 +74,7 @@ Next, complete the following steps:
 
 * Configure the Document Intelligence managed identity to communicate with the storage account.
 
-* Disable public access to the Document Intelligence resource and create a private endpoint to make it accessible from the virtual network.
+* Disable public access to the Document Intelligence resource and create a private endpoint to make it accessible from only specific virtual networks and IP addresses.
 
 * Add a private endpoint for the storage account in a selected virtual network.
 
@@ -155,7 +155,7 @@ When you connect to resources from a virtual network, adding private endpoints e
 
 Next, configure the virtual network to ensure only resources within the virtual network or traffic router through the network have access to the Document Intelligence resource and the storage account.
 
-### Enable your virtual network and private endpoints
+### Enable your firewalls and virtual networks
 
 1. In the Azure portal, navigate to your Document Intelligence resource.
 
@@ -165,7 +165,7 @@ Next, configure the virtual network to ensure only resources within the virtual
 
 > [!NOTE]
 >
->If you try accessing any of the Document Intelligence Studio features, you'll see an access denied message. To enable access from the Studio on your machine, select the **client IP address checkbox** and **Save** to restore access.
+>If you try accessing any of the Document Intelligence Studio features, you'll see an access denied message. To enable access from the Studio on your machine, select the **Add your client IP address** checkbox and **Save** to restore access.
 
   :::image type="content" source="media/managed-identities/v2-fr-network.png" alt-text="Screenshot showing how to disable public access to Document Intelligence.":::
 
@@ -242,7 +242,7 @@ Navigate to your **storage account** on the Azure portal.
 Great work! You now have all the connections between the Document Intelligence resource and storage configured to use managed identities.
 
 > [!NOTE]
-> The resources are only accessible from the virtual network.
+> The resources are only accessible from the virtual network and allowed IPs.
 >
 > Studio access and analyze requests to your Document Intelligence resource will fail unless the request originates from the virtual network or is routed via the virtual network.
 
@@ -264,13 +264,16 @@ That's it! You can now configure secure access for your Document Intelligence re
 
    :::image type="content" source="media/managed-identities/cors-error.png" alt-text="Screenshot of error message when CORS config is required":::
 
-  **Resolution**: [Configure CORS](quickstarts/try-document-intelligence-studio.md#prerequisites-for-new-users).
+  **Resolution**:
+    1. [Configure CORS](quickstarts/try-document-intelligence-studio.md#prerequisites-for-new-users).
+ 
+    1. Make sure the client computer can access Document Intelligence resource and storage account, either they are in the same VNET, or client IP address is allowed in **Networking > Firewalls and virtual networks** setting page of both Document Intelligence resource and storage account.
 
 * **AuthorizationFailure**:
 
   :::image type="content" source="media/managed-identities/auth-failure.png" alt-text="Screenshot of authorization failure error.":::
 
-  **Resolution**: Ensure that there's a network line-of-sight between the computer accessing the Document Intelligence Studio and the storage account. For example, you can add the client IP address in the storage account's networking tab.
+  **Resolution**: Make sure the client computer can access Document Intelligence resource and storage account, either they are in the same VNET, or client IP address is allowed in **Networking > Firewalls and virtual networks** setting page of both Document Intelligence resource and storage account.
 
 * **ContentSourceNotAccessible**:
 

articles/active-directory-b2c/claim-resolver-overview.md

@@ -22,6 +22,7 @@ Azure OpenAI API version 2023-12-01-preview is currently the latest preview rele
 
 This version contains support for all the latest Azure OpenAI features including:
 
+- [Text to speech](./text-to-speech-quickstart.md). [**Added in 2024-02-15-preview**]
 - [Fine-tuning](./how-to/fine-tuning.md) `gpt-35-turbo`, `babbage-002`, and `davinci-002` models.[**Added in 2023-10-01-preview**]
 - [Whisper](./whisper-quickstart.md). [**Added in 2023-09-01-preview**]
 - [Function calling](./how-to/function-calling.md)  [**Added in 2023-07-01-preview**]

articles/ai-services/document-intelligence/managed-identities-secured-access.md

@@ -0,0 +1,36 @@
+---
+title: Quickstart - Getting started with Azure OpenAI Assistants (Preview)
+titleSuffix: Azure OpenAI
+description: Walkthrough on how to get started with Azure OpenAI assistants with new features like code interpreter and retrieval.
+manager: nitinme
+ms.service: azure-ai-openai
+ms.topic: quickstart
+author: mrbullwinkle
+ms.author: mbullwin
+ms.date: 02/01/2024
+zone_pivot_groups: openai-quickstart
+recommendations: false
+---
+
+
+# Quickstart: Get started using Azure OpenAI Assistants (Preview)
+
+Azure OpenAI Assistants (Preview) allows you to create AI assistants tailored to your needs through custom instructions and augmented by advanced tools like code interpreter, and custom functions.
+
+::: zone pivot="programming-language-studio"
+
+[!INCLUDE [Studio quickstart](includes/assistants-studio.md)]
+
+::: zone-end
+
+::: zone pivot="programming-language-python"
+
+[!INCLUDE [Python SDK quickstart](includes/assistants-python.md)]
+
+::: zone-end
+
+::: zone pivot="rest-api"
+
+[!INCLUDE [REST API quickstart](includes/assistants-rest.md)]
+
+::: zone-end

articles/ai-services/document-intelligence/media/managed-identities/default-config-di.png

@@ -0,0 +1,53 @@
+---
+title: Azure OpenAI Service Assistant API concepts
+titleSuffix: Azure OpenAI Service
+description: Learn about the concepts behind the Azure OpenAI Assistants API.
+ms.topic: conceptual
+ms.date: 02/05/2023
+manager: nitinme
+author: mrbullwinkle
+ms.author: mbullwin
+recommendations: false
+---
+
+# Azure OpenAI Assistants API (Preview)
+
+Assistants, a new feature of Azure OpenAI Service, is now available in public preview. Assistants API makes it easier for developers to create applications with sophisticated copilot-like experiences that can sift through data, suggest solutions, and automate tasks.
+
+## Overview
+
+Previously, building custom AI assistants needed heavy lifting even for experienced developers. While the chat completions API is lightweight and powerful, it's inherently stateless, which means that developers had to manage conversation state and chat threads, tool integrations, retrieval documents and indexes, and execute code manually.
+
+The Assistants API, as the stateful evolution of the chat completion API, provides a solution for these challenges.
+Assistants API supports persistent automatically managed threads. This means that as a developer you no longer need to develop conversation state management systems and work around a model’s context window constraints. The Assistants API will automatically handle the optimizations to keep the thread below the max context window of your chosen model. Once you create a Thread, you can simply append new messages to it as users respond. Assistants can also access multiple tools in parallel, if needed. These tools include:
+
+- [Code Interpreter](../how-to/code-interpreter.md)
+- [Function calling](../how-to/assistant-functions.md)
+
+Assistant API is built on the same capabilities that power OpenAI’s GPT product. Some possible use cases range from AI-powered product recommender, sales analyst app, coding assistant, employee Q&A chatbot, and more. Start building on the no-code Assistants playground on the Azure OpenAI Studio or start building with the API.
+
+> [!IMPORTANT]
+> Retrieving untrusted data using Function calling, Code Interpreter with file input, and Assistant Threads functionalities could compromise the security of your Assistant, or the application that uses the Assistant. Learn about mitigation approaches [here](https://aka.ms/oai/assistant-rai).
+
+## Assistants playground
+
+We provide a walkthrough of the Assistants playground in our [quickstart guide](../assistants-quickstart.md). This provides a no-code environment to test out the capabilities of assistants.
+
+## Assistants components
+
+| **Component** | **Description** |
+|---|---|
+| **Assistant** | Custom AI that uses Azure OpenAI models in conjunction with tools. |
+|**Thread** | A conversation session between an Assistant and a user. Threads store Messages and automatically handle truncation to fit content into a model’s context.|
+| **Message** | A message created by an Assistant or a user. Messages can include text, images, and other files. Messages are stored as a list on the Thread. |
+|**Run** | Activation of an Assistant to begin running based on the contents of the Thread. The Assistant uses its configuration and the Thread’s Messages to perform tasks by calling models and tools. As part of a Run, the Assistant appends Messages to the Thread.|
+|**Run Step** | A detailed list of steps the Assistant took as part of a Run. An Assistant can call tools or create Messages during it’s run. Examining Run Steps allows you to understand how the Assistant is getting to its final results. |
+
+## See also
+
+* Learn more about Assistants and [Code Interpreter](../how-to/code-interpreter.md)
+* Learn more about Assistants and [function calling](../how-to/assistant-functions.md)
+* [Azure OpenAI Assistants API samples](https://github.com/Azure-Samples/azureai-samples/tree/main/scenarios/Assistants)
+
+
+