Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into ade-github-streamline-catalog-attach

Author: RoseHJM

.openpublishing.redirection.json

@@ -3851,7 +3851,7 @@
         },
         {
             "source_path_from_root": "/articles/aks/cluster-configuration.md",
-            "redirect_url": "/azure/aks/concepts-clusters-workloads.md",
+            "redirect_url": "/azure/aks/concepts-clusters-workloads",
             "redirect_document_id": false
         },
         {

articles/ai-services/openai/includes/assistants-python.md

@@ -30,9 +30,12 @@ ms.date: 02/01/2024
 Install the OpenAI Python client library with:
 
 ```console
-pip install openai
+pip install openai==v1.20.0
 ```
 
+> [!NOTE]
+> Azure OpenAI does not yet support Assistants V2. Please use the v1.20.0 release of the OpenAI Python library until V2 support is available.
+
 > [!NOTE]
 > This library is maintained by OpenAI. Refer to the [release history](https://github.com/openai/openai-python/releases) to track the latest updates to the library.
 

articles/ai-services/speech-service/batch-synthesis.md

@@ -48,7 +48,7 @@ To submit a batch synthesis request, construct the HTTP PUT request path and bod
 - Optionally you can set the `description`, `timeToLiveInHours`, and other properties. For more information, see [batch synthesis properties](batch-synthesis-properties.md).
 
 > [!NOTE]
-> The maximum JSON payload size that will be accepted is 2 megabytes. Each Speech resource can have up to 300 batch synthesis jobs that are running concurrently.
+> The maximum JSON payload size that will be accepted is 2 megabytes.
 
 Set the required `YourSynthesisId` in path. The `YourSynthesisId` have to be unique. It must be 3-64 long, contains only numbers, letters, hyphens, underscores and dots, starts and ends with a letter or number.
 

articles/ai-services/speech-service/bring-your-own-storage-speech-resource.md

@@ -48,12 +48,100 @@ Consider the following rules when planning BYOS-enabled Speech resource configur
 
 ## Create and configure BYOS-enabled Speech resource
 
-This section describes how to create a BYOS enabled Speech resource.
+This section describes how to create a BYOS enabled Speech resource. 
+
 
 ### Request access to BYOS for your Azure subscriptions
 
 You need to request access to BYOS functionality for each of the Azure subscriptions you plan to use. To request access, fill and submit [Cognitive Services & Applied AI Customer Managed Keys and Bring Your Own Storage access request form](https://aka.ms/cogsvc-cmk). Wait for the request to be approved.
 
+### (Optional) Check whether Azure subscription has access to BYOS
+
+You can quickly check whether your Azure subscription has access to BYOS. This check uses [preview features](/azure/azure-resource-manager/management/preview-features) functionality of Azure.
+
+# [Azure portal](#tab/portal)
+
+This functionality isn't available through Azure portal.
+
+> [!NOTE]
+> You may view the list of preview features for a given Azure subscription as explained in [this article](/azure/azure-resource-manager/management/preview-features), however note that not all preview features, including BYOS are visible this way.
+
+# [PowerShell](#tab/powershell)
+
+To check whether an Azure subscription has access to BYOS with PowerShell, we use [Get-AzProviderFeature](/powershell/module/az.resources/get-azproviderfeature) command.
+
+You can [install PowerShell locally](/powershell/azure/install-azure-powershell) or use [Azure Cloud Shell](../../cloud-shell/overview.md).
+
+If you use local installation of PowerShell, connect to your Azure account using `Connect-AzAccount` command before trying the following script.
+
+```azurepowershell
+# Target subscription parameters
+# REPLACE WITH YOUR CONFIGURATION VALUES
+$azureSubscriptionId = "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX"
+
+# Select the right subscription
+Set-AzContext -SubscriptionId $azureSubscriptionId 
+
+# Check whether the Azure subscription has access to BYOS
+Get-AzProviderFeature -ListAvailable -ProviderNamespace "Microsoft.CognitiveServices" | where-object FeatureName -Match byox
+```
+
+If you get the response like this, your subscription has access to BYOS.
+```powershell
+FeatureName ProviderName                RegistrationState
+----------- ------------                -----------------
+byoxPreview Microsoft.CognitiveServices Registered
+```
+
+If you get empty response or `RegistrationState` value is `NotRegistered` then your Azure subscription doesn't have access to BYOS and you need to [request it](#request-access-to-byos-for-your-azure-subscriptions).
+
+# [Azure CLI](#tab/azure-cli)
+
+To check whether an Azure subscription has access to BYOS with Azure CLI, we use [az feature show](/cli/azure/feature) command.
+
+You can [install Azure CLI locally](/cli/azure/install-azure-cli) or use [Azure Cloud Shell](../../cloud-shell/overview.md).
+
+> [!NOTE]
+> The following script doesn't use variables because variable usage differs, depending on the platform where Azure CLI runs. See information on Azure CLI variable usage in [this article](/cli/azure/azure-cli-variables).
+
+If you use local installation of Azure CLI, connect to your Azure account using `az login` command before trying the following script.
+
+```azurecli
+az account set --subscription "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX"
+
+az feature show --name byoxPreview --namespace  Microsoft.CognitiveServices --output table
+```
+
+If you get the response like this, your subscription has access to BYOS.
+```dos
+Name                                     RegistrationState
+---------------------------------------  -------------------
+Microsoft.CognitiveServices/byoxPreview  Registered
+```
+If you get empty response or `RegistrationState` value is `NotRegistered` then your Azure subscription doesn't have access to BYOS and you need to [request it](#request-access-to-byos-for-your-azure-subscriptions).
+
+> [!Tip]
+> See additional commands related to listing Azure subscription preview features in [this article](/azure/azure-resource-manager/management/preview-features).
+
+# [REST](#tab/rest)
+
+To check through REST API whether an Azure subscription has access to BYOS use [Features - List](/rest/api/resources/features/list) request from Azure Resource Manager REST API.
+
+If your subscription has access to BYOS, the REST response will contain the following element:
+```json
+{
+  "properties": {
+    "state": "Registered"
+  },
+  "id": "/subscriptions/XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX/providers/Microsoft.Features/providers/Microsoft.CognitiveServices/features/byoxPreview",
+  "type": "Microsoft.Features/providers/features",
+  "name": "Microsoft.CognitiveServices/byoxPreview"
+}
+```
+If the REST response doesn't contain the reference to `byoxPreview` feature or its state is `NotRegistered` then your Azure subscription doesn't have access to BYOS and you need to [request it](#request-access-to-byos-for-your-azure-subscriptions).
+***
+
+
 ### Plan and prepare your Storage account
 
 If you use Azure portal to create a BYOS-enabled Speech resource, an associated Storage account can be created automatically. For all other provisioning methods (Azure CLI, PowerShell, REST API Request) you need to use existing Storage account.

articles/ai-services/speech-service/speech-services-quotas-and-limits.md

@@ -86,10 +86,10 @@ These limits aren't adjustable. For more information on batch synthesis latency,
 
 | Quota | Free (F0) | Standard (S0) |
 |-----|-----|-----|
-|REST API limit | Not available for F0 | 50 requests per 5 seconds |
-| Max JSON payload size to create a synthesis job  | N/A | 500 kilobytes |
-| Concurrent active synthesis jobs | N/A | 200 |
-| Max number of text inputs per synthesis job | N/A | 1000 |
+|REST API limit | Not available for F0 | 100 requests per 10 seconds |
+| Max JSON payload size to create a synthesis job  | N/A | 2 megabytes |
+| Concurrent active synthesis jobs | N/A | No limit |
+| Max number of text inputs per synthesis job | N/A | 10000 |
 |Max time to live for a synthesis job since it being in the final state  | N/A | Up to 31 days (specified using properties) |
 
 #### Custom neural voice - professional

articles/ai-studio/concepts/rbac-ai-studio.md

@@ -24,7 +24,7 @@ In this article, you learn how to manage access (authorization) to an Azure AI h
 
 ## Azure AI hub resource vs Azure AI project
 
-In the Azure AI Studio, there are two levels of access: the Azure AI hub resource and the Azure AI project. The resource is home to the infrastructure (including virtual network setup, customer-managed keys, managed identities, and policies) as well as where you configure your Azure AI services. Azure AI hub resource access can allow you to modify the infrastructure, create new Azure AI hub resources, and create projects. Azure AI projects are a subset of the Azure AI hub resource that act as workspaces that allow you to build and deploy AI systems. Within a project you can develop flows, deploy models, and manage project assets. Project access lets you develop AI end-to-end while taking advantage of the infrastructure setup on the Azure AI hub resource.
+In the Azure AI Studio, there are two levels of access: the Azure AI hub and the Azure AI project. The AI hub is home to the infrastructure (including virtual network setup, customer-managed keys, managed identities, and policies) as well as where you configure your Azure AI services. Azure AI hub access can allow you to modify the infrastructure, create new Azure AI hub resources, and create projects. Azure AI projects are a subset of the Azure AI hub resource that act as workspaces that allow you to build and deploy AI systems. Within a project you can develop flows, deploy models, and manage project assets. Project access lets you develop AI end-to-end while taking advantage of the infrastructure setup on the Azure AI hub resource.
 
 :::image type="content" source="../media/concepts/azureai-hub-project-relationship.png" alt-text="Diagram of the relationship between AI Studio resources." lightbox="../media/concepts/azureai-hub-project-relationship.png":::
 
@@ -114,7 +114,6 @@ The Azure AI hub resource has dependencies on other Azure services. The followin
 | `Microsoft.Insights/Components/Write` | Write to an application insights component configuration. |
 | `Microsoft.OperationalInsights/workspaces/write` | Create a new workspace or links to an existing workspace by providing the customer ID from the existing workspace. |
 
-
 ## Sample enterprise RBAC setup
 The following is an example of how to set up role-based access control for your Azure AI Studio for an enterprise.
 
@@ -151,6 +150,18 @@ If the built-in roles are insufficient, you can create custom roles. Custom role
 > [!NOTE]
 > You must be an owner of the resource at that level to create custom roles within that resource. 
 
+## Scenario: Use a customer-managed key
+
+When using a customer-managed key (CMK), an Azure Key Vault is used to store the key. The user or service principal used to create the workspace must have owner or contributor access to the key vault.
+
+If your Azure AI hub is configured with a **user-assigned managed identity**, the identity must be granted the following roles. These roles allow the managed identity to create the Azure Storage, Azure Cosmos DB, and Azure Search resources used when using a customer-managed key:
+
+- `Microsoft.Storage/storageAccounts/write`
+- `Microsoft.Search/searchServices/write`
+- `Microsoft.DocumentDB/databaseAccounts/write`
+
+Within the key vault, the user or service principal must have create, get, delete, and purge access to the key through a key vault access policy. For more information, see [Azure Key Vault security](/azure/key-vault/general/security-features#controlling-access-to-key-vault-data).
+
 ## Next steps
 
 - [How to create an Azure AI hub resource](../how-to/create-azure-ai-resource.md)

articles/aks/custom-node-configuration.md

@@ -239,7 +239,7 @@ The settings below can be used to tune the operation of the virtual memory (VM)
 
 ## Next steps
 
-- Learn [how to configure your AKS cluster](cluster-configuration.md).
+- Learn [how to configure your AKS cluster](./concepts-clusters-workloads.md).
 - Learn how [upgrade the node images](node-image-upgrade.md) in your cluster.
 - See [Upgrade an Azure Kubernetes Service (AKS) cluster](upgrade-cluster.md) to learn how to upgrade your cluster to the latest version of Kubernetes.
 - See the list of [Frequently asked questions about AKS](faq.md) to find answers to some common AKS questions.

articles/automation/automation-linux-hrw-install.md

@@ -4,7 +4,7 @@ description: This article tells how to install an agent-based  Hybrid Runbook Wo
 services: automation
 ms.subservice: process-automation
 ms.custom: linux-related-content
-ms.date: 09/17/2023
+ms.date: 04/21/2024
 ms.topic: conceptual
 ---
 
@@ -58,9 +58,14 @@ The Hybrid Runbook Worker feature supports the following distributions. All oper
   16.04 LTS | Xenial Xerus
   14.04 LTS | Trusty Tahr
 
+> [!NOTE]
+> Hybrid Worker would follow support timelines of the OS vendor.
+
 > [!IMPORTANT]
 > Before enabling the Update Management feature, which depends on the system Hybrid Runbook Worker role, confirm the distributions it supports [here](update-management/operating-system-requirements.md).
 
+
+
 ### Minimum requirements
 
 The minimum requirements for a Linux system and user Hybrid Runbook Worker are:

articles/automation/automation-windows-hrw-install.md

@@ -3,7 +3,7 @@ title: Deploy an agent-based Windows Hybrid Runbook Worker in Automation
 description: This article tells how to deploy an agent-based Hybrid Runbook Worker that you can use to run runbooks on Windows-based machines in your local datacenter or cloud environment.
 services: automation
 ms.subservice: process-automation
-ms.date: 09/17/2023
+ms.date: 04/21/2024
 ms.topic: conceptual 
 ---
 
@@ -50,6 +50,9 @@ The Hybrid Runbook Worker feature supports the following operating systems:
 * Windows 8 Enterprise and Pro
 * Windows 7 SP1
 
+> [!NOTE]
+> Hybrid Worker would follow support timelines of the OS vendor.
+
 ### Minimum requirements
 
 The minimum requirements for a Windows system and user Hybrid Runbook Worker are:

articles/azure-arc/edge-storage-accelerator/jumpstart.md

@@ -0,0 +1,27 @@
+---
+title: Azure Arc Jumpstart scenario using Edge Storage Accelerator (preview)
+description: Learn about an Azure Arc scenario that uses Edge Storage Accelerator.
+author: sethmanheim
+ms.author: sethm
+ms.topic: overview
+ms.date: 04/18/2024
+
+---
+
+# Azure Arc Jumpstart scenario using Edge Storage Accelerator
+
+Edge Storage Accelerator (ESA) collaborated with the [Arc Jumpstart](https://azurearcjumpstart.com/) team to implement a scenario in which a computer vision AI model detects defects in bolts by analyzing video from a supply line video feed streamed over Real-Time Streaming Protocol (RTSP). The identified defects are then stored in a container within a storage account using Edge Storage Accelerator.
+
+## Scenario description
+
+In this automated setup, ESA is deployed on an [AKS Edge Essentials](/azure/aks/hybrid/aks-edge-overview) single-node instance, running in an Azure virtual machine. An Azure Resource Manager template is provided to create the necessary Azure resources and configure the **LogonScript.ps1** custom script extension. This extension handles AKS Edge Essentials cluster creation, Azure Arc onboarding for the Azure VM and AKS Edge Essentials cluster, and Edge Storage Accelerator deployment. Once AKS Edge Essentials is deployed, ESA is installed as a Kubernetes service that exposes a CSI driven storage class for use by applications in the Edge Essentials Kubernetes cluster.
+
+For more information, see the following articles:
+
+- [Watch the ESA jumpstart scenario on YouTube](https://youtu.be/Qnh2UH1g6Q4)
+- [Visit the ESA jumpstart documentation](https://aka.ms/esajumpstart)
+
+## Next steps
+
+- [Edge Storage Accelerator overview](overview.md)
+- [AKS Edge Essentials overview](/azure/aks/hybrid/aks-edge-overview)