Merging changes synced from https://github.com/MicrosoftDocs/azure-docs-pr (branch live)

Author: Learn Build Service GitHub App

articles/ai-services/computer-vision/concept-model-customization.md

@@ -80,8 +80,8 @@ The following table describes the limits on the scale of your custom model proje
 | Max # training images               | 1,000,000                       | 200,000                         |
 | Max # evaluation images             | 100,000                        | 100,000                         |
 | Min # training images per category  | 2                               | 2                               |
-| Max # tags per image                | multiclass: 1                   | NA                              |
-| Max # regions per image             | NA                              | 1,000                           |
+| Max # tags per image                | 1                               | N/A                            |
+| Max # regions per image             | N/A                              | 1,000                           |
 | Max # categories                    | 2,500                           | 1,000                           |
 | Min # categories                    | 2                               | 1                               |
 | Max image size (Training)           | 20 MB                            | 20 MB                            |

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

@@ -30,6 +30,8 @@ This documentation contains the following article types:
 
 The following are a few scenarios in which a software developer or team would require a content moderation service:
 
+- User prompts submitted to a generative AI service. 
+- Content produced by generative AI models.
 - Online marketplaces that moderate product catalogs and other user-generated content.
 - Gaming companies that moderate user-generated game artifacts and chat rooms.
 - Social messaging platforms that moderate images and text added by their users.

articles/ai-services/openai/how-to/gpt-with-vision.md

@@ -30,7 +30,7 @@ The following command shows the most basic way to use the GPT-4 Turbo with Visio
 
 #### [REST](#tab/rest)
 
-Send a POST request to `https://{RESOURCE_NAME}.openai.azure.com/openai/deployments/{DEPLOYMENT_NAME}/chat/completions?api-version=2023-12-01-preview` where 
+Send a POST request to `https://{RESOURCE_NAME}.openai.azure.com/openai/deployments/{DEPLOYMENT_NAME}/chat/completions?api-version=2024-02-15-preview` where 
 
 - RESOURCE_NAME is the name of your Azure OpenAI resource 
 - DEPLOYMENT_NAME is the name of your GPT-4 Turbo with Vision model deployment 
@@ -88,12 +88,12 @@ The following is a sample request body. The format is the same as the chat compl
     api_base = '<your_azure_openai_endpoint>' # your endpoint should look like the following https://YOUR_RESOURCE_NAME.openai.azure.com/
     api_key="<your_azure_openai_key>"
     deployment_name = '<your_deployment_name>'
-    api_version = '2023-12-01-preview' # this might change in the future
+    api_version = '2024-02-15-preview' # this might change in the future
 
     client = AzureOpenAI(
         api_key=api_key,  
         api_version=api_version,
-        base_url=f"{api_base}openai/deployments/{deployment_name}/extensions",
+        base_url=f"{api_base}openai/deployments/{deployment_name}",
     )
     ```
 
@@ -265,7 +265,7 @@ The **object grounding** integration brings a new layer to data analysis and use
 
 #### [REST](#tab/rest)
 
-Send a POST request to `https://{RESOURCE_NAME}.openai.azure.com/openai/deployments/{DEPLOYMENT_NAME}/extensions/chat/completions?api-version=2023-12-01-preview` where 
+Send a POST request to `https://{RESOURCE_NAME}.openai.azure.com/openai/deployments/{DEPLOYMENT_NAME}/chat/completions?api-version=2024-02-15-preview` where 
 
 - RESOURCE_NAME is the name of your Azure OpenAI resource 
 - DEPLOYMENT_NAME is the name of your GPT-4 Turbo with Vision model deployment 
@@ -577,7 +577,7 @@ To use a User assigned identity on your Azure AI Services resource, follow these
 
 #### [REST](#tab/rest)
 
-1. Prepare a POST request to `https://{RESOURCE_NAME}.openai.azure.com/openai/deployments/{DEPLOYMENT_NAME}/extensions/chat/completions?api-version=2023-12-01-preview` where 
+1. Prepare a POST request to `https://{RESOURCE_NAME}.openai.azure.com/openai/deployments/{DEPLOYMENT_NAME}/chat/completions?api-version=2024-02-15-preview` where 
 
     - RESOURCE_NAME is the name of your Azure OpenAI resource 
     - DEPLOYMENT_NAME is the name of your GPT-4 Vision model deployment 

articles/ai-studio/how-to/deploy-models-mistral.md

@@ -64,8 +64,7 @@ Certain models in the model catalog can be deployed as a serverless API with pay
 - An [Azure AI Studio hub](../how-to/create-azure-ai-resource.md).
 
     > [!IMPORTANT]
-    > The serverless API model deployment offering for eligible models in the Mistral family is only available in hubs created in the **East US 2** and **Sweden Central** regions. For _Mistral Large_, the serverless API model deployment offering is also available in the **France Central** region.
-
+    > The serverless API model deployment offering for eligible models in the Mistral family is only available in hubs created in the **East US 2** and **Sweden Central** regions. 
 - An [Azure AI Studio project](../how-to/create-projects.md).
 - Azure role-based access controls (Azure RBAC) are used to grant access to operations in Azure AI Studio. To perform the steps in this article, your user account must be assigned the __Azure AI Developer role__ on the resource group. For more information on permissions, see [Role-based access control in Azure AI Studio](../concepts/rbac-ai-studio.md).
 
@@ -94,7 +93,7 @@ To create a deployment:
 
     :::image type="content" source="../media/deploy-monitor/mistral/mistral-large-deploy-pay-as-you-go.png" alt-text="A screenshot showing how to deploy a model as a serverless API." lightbox="../media/deploy-monitor/mistral/mistral-large-deploy-pay-as-you-go.png":::
 
-1. Select the project in which you want to deploy your model. To deploy the Mistral model, your project must be in the *EastUS2* or *Sweden Central* region. For the Mistral Large model, you can also deploy in a project that's in the *France Central* region.
+1. Select the project in which you want to deploy your model. To deploy the Mistral model, your project must be in the *EastUS2* or *Sweden Central* region.
 1. In the deployment wizard, select the link to **Azure Marketplace Terms** to learn more about the terms of use.
 1. Select the **Pricing and terms** tab to learn about pricing for the selected model.
 1. Select the **Subscribe and Deploy** button. If this is your first time deploying the model in the project, you have to subscribe your project for the particular offering. This step requires that your account has the **Azure AI Developer role** permissions on the resource group, as listed in the prerequisites. Each project has its own subscription to the particular Azure Marketplace offering of the model, which allows you to control and monitor spending. Currently, you can have only one deployment for each model within a project.

articles/ai-studio/how-to/model-catalog-overview.md

@@ -136,7 +136,7 @@ Llama-3-70B-Instruct <br> Llama-3-8B-Instruct | [Microsoft Managed Countries](/p
 Llama-2-7b <br> Llama-2-13b <br> Llama-2-70b | [Microsoft Managed Countries](/partner-center/marketplace/tax-details-marketplace#microsoft-managed-countriesregions) | East US, East US 2, North Central US, South Central US, West US, West US 3 | West US 3
 Llama-2-7b-chat <br> Llama-2-13b-chat <br> Llama-2-70b-chat | [Microsoft Managed Countries](/partner-center/marketplace/tax-details-marketplace#microsoft-managed-countriesregions) | East US, East US 2, North Central US, South Central US, West US, West US 3,  | Not available
 Mistral Small | [Microsoft Managed Countries](/partner-center/marketplace/tax-details-marketplace#microsoft-managed-countriesregions) | East US, East US 2, North Central US, South Central US, Sweden Central, West US, West US 3 | Not available
-Mistral-Large | [Microsoft Managed Countries](/partner-center/marketplace/tax-details-marketplace#microsoft-managed-countriesregions) <br> Brazil <br> Hong Kong <br> Israel|  East US, East US 2, France Central, North Central US, South Central US, Sweden Central, West US, West US 3 | Not available
+Mistral-Large | [Microsoft Managed Countries](/partner-center/marketplace/tax-details-marketplace#microsoft-managed-countriesregions) <br> Brazil <br> Hong Kong <br> Israel|  East US, East US 2, North Central US, South Central US, Sweden Central, West US, West US 3 | Not available
 Cohere-command-r-plus <br> Cohere-command-r <br> Cohere-embed-v3-english <br> Cohere-embed-v3-multilingual | [Microsoft Managed Countries](/partner-center/marketplace/tax-details-marketplace#microsoft-managed-countriesregions) <br> Japan |  East US, East US 2, North Central US, South Central US, Sweden Central, West US, West US 3 | Not available
 TimeGEN-1 | [Microsoft Managed Countries](/partner-center/marketplace/tax-details-marketplace#microsoft-managed-countriesregions) <br> Mexico <br> Israel| East US, East US 2, North Central US, South Central US, Sweden Central, West US, West US 3 | Not available
 jais-30b-chat | [Microsoft Managed Countries](/partner-center/marketplace/tax-details-marketplace#microsoft-managed-countriesregions) | East US, East US 2, North Central US, South Central US, Sweden Central, West US, West US 3 | Not available

articles/app-service/environment/how-to-custom-domain-suffix.md

@@ -61,14 +61,18 @@ If you choose to use Azure role-based access control to manage access to your ke
 
 ### Certificate
 
-The certificate for custom domain suffix must be stored in an Azure Key Vault. The certificate must be uploaded in .PFX format and be smaller than 20 kb. Certificates in .PEM format aren't supported at this time. App Service Environment uses the managed identity you selected to get the certificate. The key vault can be accessed publicly or through a [private endpoint](../../private-link/private-endpoint-overview.md) accessible from the subnet that the App Service Environment is deployed to. To learn how to configure a private endpoint, see [Integrate Key Vault with Azure Private Link](../../key-vault/general/private-link-service.md). In the case of public access, you can secure your key vault to only accept traffic from the outbound IP addresses of the App Service Environment.
-
-:::image type="content" source="./media/custom-domain-suffix/key-vault-networking.png" alt-text="Screenshot of a sample networking page for key vault to allow custom domain suffix feature.":::
+The certificate for custom domain suffix must be stored in an Azure Key Vault. The certificate must be uploaded in .PFX format and be smaller than 20 kb. Certificates in .PEM format aren't supported at this time. App Service Environment uses the managed identity you selected to get the certificate. 
 
 Your certificate must be a wildcard certificate for the selected custom domain name. For example, *internal.contoso.com* would need a certificate covering **.internal.contoso.com*. If the certificate used by the custom domain suffix contains a Subject Alternate Name (SAN) entry for scm, for example **.scm.internal.contoso.com*, the scm site is also available using the custom domain suffix.
 
 If you rotate your certificate in Azure Key Vault, the App Service Environment picks up the change within 24 hours.
 
+### Network access to Key Vault
+
+The key vault can be accessed publicly or through a [private endpoint](../../private-link/private-endpoint-overview.md) accessible from the subnet that the App Service Environment is deployed to. To learn how to configure a private endpoint, see [Integrate Key Vault with Azure Private Link](../../key-vault/general/private-link-service.md). If you use public access, you can secure your key vault to only accept traffic from the outbound IP address of the App Service Environment. The App Service Environment uses the platform outbound IP address as the source address when accessing the key vault. You can find the IP address in the IP Addresses page in Azure portal.
+
+:::image type="content" source="./media/custom-domain-suffix/platform-outbound-ip.png" alt-text="Screenshot of IP Addresses page in Azure portal.":::
+
 ::: zone pivot="experience-azp"
 
 ## Use the Azure portal to configure custom domain suffix

articles/app-service/environment/media/custom-domain-suffix/platform-outbound-ip.png

@@ -125,28 +125,32 @@ Congratulations, you've successfully completed this quickstart.
 The App Service app pulls from the container registry every time it starts. If you rebuild your image, you just need to push it to your container registry, and the app pulls in the updated image when it restarts. To tell your app to pull in the updated image immediately, restart it.
 
 > [!div class="nextstepaction"]
-> [Secure with custom domain and certificate](../../tutorial-secure-domain-certificate.md)
+> [Configure custom container](../../configure-custom-container.md)
 
 > [!div class="nextstepaction"]
-> [Migrate to Windows container in Azure](../../tutorial-custom-container.md)
+> [How to use managed identities for App Service and Azure Functions](../../overview-managed-identity.md)
 
 > [!div class="nextstepaction"]
-> [Integrate your app with an Azure virtual network](../../overview-vnet-integration.md)
+> [Application monitoring for Azure App Service overview](/azure/azure-monitor/app/azure-web-apps)
 
 > [!div class="nextstepaction"]
-> [Use Private Endpoints for App Service apps](../../networking/private-endpoint.md)
+> [Azure Monitor overview](/azure/azure-monitor/overview)
 
 > [!div class="nextstepaction"]
-> [Azure Monitor overview](/azure/azure-monitor/overview)
+> [Secure with custom domain and certificate](../../tutorial-secure-domain-certificate.md)
 
 > [!div class="nextstepaction"]
-> [Application monitoring for Azure App Service overview](/azure/azure-monitor/app/azure-web-apps)
+> [Integrate your app with an Azure virtual network](../../overview-vnet-integration.md)
 
 > [!div class="nextstepaction"]
-> [How to use managed identities for App Service and Azure Functions](../../overview-managed-identity.md)
+> [Use Private Endpoints for App Service apps](../../networking/private-endpoint.md)
 
 > [!div class="nextstepaction"]
-> [Configure custom container](../../configure-custom-container.md)
+> [Migrate to Windows container in Azure](../../tutorial-custom-container.md)
+
+> [!div class="nextstepaction"]
+> [Deploy a container with Azure Pipelines](../../deploy-container-azure-pipelines.md)
 
 > [!div class="nextstepaction"]
-> [Sidecar container tutorial](../../tutorial-custom-container-sidecar.md)
+> [Deploy a container with GitHub Actions](../../deploy-container-github-action.md)
+

articles/app-service/includes/quickstart-custom-container/quickstart-custom-container-windows-azure-portal-pivot.md

@@ -83,31 +83,34 @@ Congratulations, you've successfully completed this quickstart.
 The App Service app pulls from the container registry every time it starts. If you rebuild your image, you just need to push it to your container registry, and the app pulls in the updated image when it restarts. To tell your app to pull in the updated image immediately, restart it.
 
 > [!div class="nextstepaction"]
-> [Secure with custom domain and certificate](../../tutorial-secure-domain-certificate.md)
+> [Configure custom container](../../configure-custom-container.md)
 
 > [!div class="nextstepaction"]
-> [Migrate to Windows container in Azure](../../tutorial-custom-container.md)
+> [How to use managed identities for App Service and Azure Functions](../../overview-managed-identity.md)
 
 > [!div class="nextstepaction"]
-> [Integrate your app with an Azure virtual network](../../overview-vnet-integration.md)
+> [Application monitoring for Azure App Service overview](/azure/azure-monitor/app/azure-web-apps)
 
 > [!div class="nextstepaction"]
-> [Use Private Endpoints for App Service apps](../../networking/private-endpoint.md)
+> [Azure Monitor overview](/azure/azure-monitor/overview)
 
 > [!div class="nextstepaction"]
-> [Azure Monitor overview](/azure/azure-monitor/overview)
+> [Secure with custom domain and certificate](../../tutorial-secure-domain-certificate.md)
 
 > [!div class="nextstepaction"]
-> [Application monitoring for Azure App Service overview](/azure/azure-monitor/app/azure-web-apps)
+> [Integrate your app with an Azure virtual network](../../overview-vnet-integration.md)
 
 > [!div class="nextstepaction"]
-> [How to use managed identities for App Service and Azure Functions](../../overview-managed-identity.md)
+> [Use Private Endpoints for App Service apps](../../networking/private-endpoint.md)
 
 > [!div class="nextstepaction"]
-> [Configure custom container](../../configure-custom-container.md)
+> [Migrate to Windows container in Azure](../../tutorial-custom-container.md)
+
+> [!div class="nextstepaction"]
+> [Deploy a container with Azure Pipelines](../../deploy-container-azure-pipelines.md)
 
 > [!div class="nextstepaction"]
-> [Sidecar container tutorial](../../tutorial-custom-container-sidecar.md)
+> [Deploy a container with GitHub Actions](../../deploy-container-github-action.md)
 
 
 <!-- LINKS - internal -->

articles/app-service/includes/quickstart-custom-container/quickstart-custom-container-windows-cli-pivot.md

@@ -83,28 +83,32 @@ Congratulations, you've successfully completed this quickstart.
 The App Service app pulls from the container registry every time it starts. If you rebuild your image, you just need to push it to your container registry, and the app pulls in the updated image when it restarts. To tell your app to pull in the updated image immediately, restart it.
 
 > [!div class="nextstepaction"]
-> [Secure with custom domain and certificate](../../tutorial-secure-domain-certificate.md)
+> [Configure custom container](../../configure-custom-container.md)
 
 > [!div class="nextstepaction"]
-> [Migrate to Windows container in Azure](../../tutorial-custom-container.md)
+> [How to use managed identities for App Service and Azure Functions](../../overview-managed-identity.md)
 
 > [!div class="nextstepaction"]
-> [Integrate your app with an Azure virtual network](../../overview-vnet-integration.md)
+> [Application monitoring for Azure App Service overview](/azure/azure-monitor/app/azure-web-apps)
 
 > [!div class="nextstepaction"]
-> [Use Private Endpoints for App Service apps](../../networking/private-endpoint.md)
+> [Azure Monitor overview](/azure/azure-monitor/overview)
 
 > [!div class="nextstepaction"]
-> [Azure Monitor overview](/azure/azure-monitor/overview)
+> [Secure with custom domain and certificate](../../tutorial-secure-domain-certificate.md)
 
 > [!div class="nextstepaction"]
-> [Application monitoring for Azure App Service overview](/azure/azure-monitor/app/azure-web-apps)
+> [Integrate your app with an Azure virtual network](../../overview-vnet-integration.md)
 
 > [!div class="nextstepaction"]
-> [How to use managed identities for App Service and Azure Functions](../../overview-managed-identity.md)
+> [Use Private Endpoints for App Service apps](../../networking/private-endpoint.md)
 
 > [!div class="nextstepaction"]
-> [Configure custom container](../../configure-custom-container.md)
+> [Migrate to Windows container in Azure](../../tutorial-custom-container.md)
+
+> [!div class="nextstepaction"]
+> [Deploy a container with Azure Pipelines](../../deploy-container-azure-pipelines.md)
 
 > [!div class="nextstepaction"]
-> [Sidecar container tutorial](../../tutorial-custom-container-sidecar.md)
+> [Deploy a container with GitHub Actions](../../deploy-container-github-action.md)
+