Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into AprilERYupdate

Author: siddomala

articles/ai-services/openai/how-to/azure-developer-cli.md

@@ -0,0 +1,87 @@
+---
+title: 'Use the Azure Developer CLI to deploy resources for Azure OpenAI On Your Data'
+titleSuffix: Azure OpenAI
+description: Use this article to learn how to automate resource deployment for Azure OpenAI On Your Data.
+manager: nitinme
+ms.service: azure-ai-openai
+ms.topic: quickstart
+author: aahill
+ms.author: aahi
+ms.date: 04/09/2024
+recommendations: false
+---
+
+# Use the Azure Developer CLI to deploy resources for Azure OpenAI On Your Data 
+
+Use this article to learn how to automate resource deployment for Azure OpenAI On Your Data. The Azure Developer CLI (`azd`) is an open-source, command-line tool that streamlines provisioning and deploying resources to Azure using a template system. The template contains infrastructure files to provision the necessary Azure OpenAI resources and configurations and includes the completed sample app code.
+
+## Prerequisites
+
+- An Azure subscription - <a href="https://azure.microsoft.com/free/cognitive-services" target="_blank">Create one for free</a>.
+- Access granted to Azure OpenAI in the desired Azure subscription.
+
+  Azure OpenAI requires registration and is currently only available to approved enterprise customers and partners. [See Limited access to Azure OpenAI Service](/legal/cognitive-services/openai/limited-access?context=/azure/ai-services/openai/context/context) for more information. You can apply for access to Azure OpenAI by completing the form at <a href="https://aka.ms/oai/access" target="_blank">https://aka.ms/oai/access</a>. Open an issue on this repo to contact us if you have an issue.
+
+- The Azure Developer CLI [installed](/azure/developer/azure-developer-cli/install-azd) on your machine
+
+## Clone and initialize the Azure Developer CLI template
+
+
+
+1. For the steps ahead, clone and initialize the template.
+
+    ```bash
+    azd init --template openai-chat-your-own-data
+    ```
+    
+2. The `azd init` command prompts you for the following information:
+
+    * Environment name: This value is used as a prefix for all Azure resources created by Azure Developer CLI. The name must be unique across all Azure subscriptions and must be between 3 and 24 characters long. The name can contain numbers and lowercase letters only.
+
+## Use the template to deploy resources
+
+1. Sign-in to Azure:
+
+    ```bash
+    azd auth login
+    ```
+
+1. Provision and deploy the OpenAI resource to Azure:
+
+    ```bash
+    azd up
+    ```
+    
+    `azd` prompts you for the following information:
+    
+    * Subscription: The Azure subscription that your resources are deployed to.
+    * Location: The Azure region where your resources are deployed.
+    
+    > [!NOTE]
+    > The sample `azd` template uses the `gpt-35-turbo-16k` model. A recommended region for this template is East US, since different Azure regions support different OpenAI models. You can visit the [Azure OpenAI Service Models](/azure/ai-services/openai/concepts/models) support page for more details about model support by region.
+    
+    > [!NOTE]
+    > The provisioning process may take several minutes to complete. Wait for the task to finish before you proceed to the next steps.
+        
+1. Click the link `azd` outputs to navigate to the new resource group in the Azure portal. You should see the following top level resources:
+    
+    * An Azure OpenAI service with a deployed model
+    * An Azure Storage account you can use to upload your own data files
+    * An Azure AI Search service configured with the proper indexes and data sources
+
+## Upload data to the storage account
+
+`azd` provisioned all of the required resources for you to chat with your own data, but you still need to upload the data files you want to make available to your AI service.
+
+1. Navigate to the new storage account in the Azure portal.
+1. On the left navigation, select **Storage browser**.
+1. Select **Blob containers** and then navigate into the **File uploads** container.
+1. Click the **Upload** button at the top of the screen. 
+1. In the flyout menu that opens, upload _contoso_benefits_document_example.pdf_ file in the root `documents` folder of the example repo.
+ 
+> [!NOTE]
+> The search indexer is set to run every 5 minutes to index the data in the storage account. You can either wait a few minutes for the uploaded data to be indexed, or you can manually run the indexer from the search service page.
+
+## Connect or create an application
+
+After running the `azd` template and uploading your data, you're ready to start using Azure OpenAI on Your Data. See the [quickstart article](../use-your-data-quickstart.md) for code samples you can use to build your applications.

articles/ai-services/openai/includes/connect-your-data-studio.md

@@ -12,6 +12,9 @@ recommendations: false
 
 ## Add your data using Azure OpenAI Studio
 
+> [!TIP]
+> You can [use the Azure Developer CLI](../how-to/azure-developer-cli.md) to programmatically create the resources needed for Azure OpenAI On Your Data 
+
 Navigate to [Azure OpenAI Studio](https://oai.azure.com/) and sign-in with credentials that have access to your Azure OpenAI resource. During or after the sign-in workflow, select the appropriate directory, Azure subscription, and Azure OpenAI resource.
 
 1. Select the **Bring your own data** tile

articles/ai-services/openai/toc.yml

@@ -145,6 +145,8 @@ items:
         href: ./how-to/use-your-data-securely.md
       - name: Deploy and use web apps
         href: ./how-to/use-web-app.md
+      - name: Use the Azure Developer CLI
+        href: ./how-to/azure-developer-cli.md
   - name: Migrate to OpenAI Python v1.x
     href: ./how-to/migration.md
   - name: Models

articles/aks/supported-kubernetes-versions.md

@@ -9,7 +9,7 @@ ms.author: nickoman
 
 # Supported Kubernetes versions in Azure Kubernetes Service (AKS)
 
-The Kubernetes community releases minor versions roughly every three months. Recently, the Kubernetes community has [increased the support window for each version from nine months to one year](https://kubernetes.io/blog/2020/08/31/kubernetes-1-19-feature-one-year-support/), starting with version 1.19.
+The Kubernetes community [releases minor versions](https://kubernetes.io/releases/) roughly every four months. 
 
 Minor version releases include new features and improvements. Patch releases are more frequent (sometimes weekly) and are intended for critical bug fixes within a minor version. Patch releases include fixes for security vulnerabilities or major bugs.
 
@@ -21,8 +21,8 @@ Kubernetes uses the standard [Semantic Versioning](https://semver.org/) versioni
 [major].[minor].[patch]
 
 Examples:
-  1.17.7
-  1.17.8
+  1.29.2
+  1.29.1
 ```
 
 Each number in the version indicates general compatibility with the previous version:
@@ -31,7 +31,7 @@ Each number in the version indicates general compatibility with the previous ver
 * **Minor versions** change when functionality updates are made that are backwards compatible to the other minor releases.
 * **Patch versions** change when backwards-compatible bug fixes are made.
 
-Aim to run the latest patch release of the minor version you're running. For example, if your production cluster is on **`1.17.7`**, **`1.17.8`** is the latest available patch version available for the *1.17* series. You should upgrade to **`1.17.8`** as soon as possible to ensure your cluster is fully patched and supported.
+Aim to run the latest patch release of the minor version you're running. For example, if your production cluster is on **`1.29.1`** and **`1.29.2`** is the latest available patch version available for the *1.29* minor version, you should upgrade to **`1.29.2`** as soon as possible to ensure your cluster is fully patched and supported.
 
 ## AKS Kubernetes release calendar
 
@@ -73,7 +73,7 @@ Note the following important changes before you upgrade to any of the available
 > [!NOTE]
 > Alias minor version requires Azure CLI version 2.37 or above as well as API version 20220401 or above. Use `az upgrade` to install the latest version of the CLI.
 
-AKS allows you to create a cluster without specifying the exact patch version. When you create a cluster without designating a patch, the cluster runs the minor version's latest GA patch. For example, if you create a cluster with **`1.21`**, your cluster runs **`1.21.7`**, which is the latest GA patch version of *1.21*. If you want to upgrade your patch version in the same minor version, please use [auto-upgrade](./auto-upgrade-cluster.md).
+AKS allows you to create a cluster without specifying the exact patch version. When you create a cluster without designating a patch, the cluster runs the minor version's latest GA patch. For example, if you create a cluster with **`1.29`** and **`1.29.2`** is the latest GA'd patch available, your cluster will be created with **`1.29.2`**. If you want to upgrade your patch version in the same minor version, please use [auto-upgrade](./auto-upgrade-cluster.md).
 
 To see what patch you're on, run the `az aks show --resource-group myResourceGroup --name myAKSCluster` command. The `currentKubernetesVersion` property shows the whole Kubernetes version.
 
@@ -83,7 +83,7 @@ To see what patch you're on, run the `az aks show --resource-group myResourceGro
   "autoScalerProfile": null,
   "autoUpgradeProfile": null,
   "azurePortalFqdn": "myaksclust-myresourcegroup.portal.hcp.eastus.azmk8s.io",
-  "currentKubernetesVersion": "1.21.7",
+  "currentKubernetesVersion": "1.29.2",
 }
 ```
 
@@ -102,41 +102,38 @@ AKS provides platform support only for one GA minor version of Kubernetes after
 > [!NOTE]
 > AKS uses safe deployment practices which involve gradual region deployment. This means it might take up to 10 business days for a new release or a new version to be available in all regions.
 
-The supported window of Kubernetes versions on AKS is known as "N-2": (N (Latest release) - 2 (minor versions)), and ".letter" is representative of patch versions.
+The supported window of Kubernetes minor versions on AKS is known as "N-2", where N refers to the latest release, meaning that two previous minor releases are also supported.
 
-For example, if AKS introduces *1.17.a* today, support is provided for the following versions:
+For example, on the day that AKS introduces version 1.29, support is provided for the following versions:
 
-New minor version    |    Supported Version List
+New minor version    |    Supported Minor Version List
 -----------------    |    ----------------------
-1.17.a               |    1.17.a, 1.17.b, 1.16.c, 1.16.d, 1.15.e, 1.15.f
+1.29                 |    1.29, 1.28, 1.27
 
-When a new minor version is introduced, the oldest minor version and patch releases supported are deprecated and removed. For example, let's say the current supported version list is:
+When a new minor version is introduced, the oldest minor version is deprecated and removed. For example, let's say the current supported minor version list is:
 
 ```
-1.17.a
-1.17.b
-1.16.c
-1.16.d
-1.15.e
-1.15.f
+1.29
+1.28
+1.27
 ```
 
-When AKS releases 1.18.\*, all the 1.15.\* versions go out of support 30 days later.
+When AKS releases 1.30, all the 1.27 versions go out of support 30 days later.
 
 AKS also supports a maximum of two **patch** releases of a given minor version. For example, given the following supported versions:
 
 ```
 Current Supported Version List
 ------------------------------
-1.17.8, 1.17.7, 1.16.10, 1.16.9
+1.29.2, 1.29.1, 1.28.7, 1.28.6, 1.27.11, 1.27.10
 ```
 
-If AKS releases `1.17.9` and `1.16.11`, the oldest patch versions are deprecated and removed, and the supported version list becomes:
+If AKS releases `1.29.3` and `1.28.8`, the oldest patch versions are deprecated and removed, and the supported version list becomes:
 
 ```
 New Supported Version List
 ----------------------
-1.17.*9*, 1.17.*8*, 1.16.*11*, 1.16.*10*
+1.29.3, 1.29.2, 1.28.8, 1.28.7, 1.27.11, 1.27.10
 ```
 
 ## Platform support policy
@@ -178,7 +175,7 @@ This table outlines support guidelines for Community Support compared to Platfor
 
 You can use one minor version older or newer of `kubectl` relative to your *kube-apiserver* version, consistent with the [Kubernetes support policy for kubectl](https://kubernetes.io/docs/setup/release/version-skew-policy/#kubectl).
 
-For example, if your *kube-apiserver* is at *1.17*, then you can use versions *1.16* to *1.18* of `kubectl` with that *kube-apiserver*.
+For example, if your *kube-apiserver* is at *1.28*, then you can use versions *1.27* to *1.29* of `kubectl` with that *kube-apiserver*.
 
 To install or update `kubectl` to the latest version, run:
 
@@ -229,7 +226,7 @@ Specific patch releases might be skipped or rollout accelerated, depending on th
 
 ## Azure portal and CLI versions
 
-When you deploy an AKS cluster with Azure portal, Azure CLI, Azure PowerShell, the cluster defaults to the N-1 minor version and latest patch. For example, if AKS supports *1.17.a*, *1.17.b*, *1.16.c*, *1.16.d*, *1.15.e*, and *1.15.f*, the default version selected is *1.16.c*.
+When you deploy an AKS cluster with Azure portal, Azure CLI, Azure PowerShell, the cluster defaults to the N-1 minor version and latest patch. For example, if AKS supports *1.29.2*, *1.29.1*, *1.28.7*, *1.28.6*, *1.27.11*, and *1.27.10*, the default version selected is *1.28.7*.
 
 ### [Azure CLI](#tab/azure-cli)
 
@@ -265,8 +262,8 @@ Starting with Kubernetes 1.19, the [open source community has expanded support t
 
 If you're on the *n-3* version or older, it means you're outside of support and will be asked to upgrade. When your upgrade from version n-3 to n-2 succeeds, you're back within our support policies. For example:
 
-* If the oldest supported AKS version is *1.15.a* and you're on *1.14.b* or older, you're outside of support.
-* When you successfully upgrade from *1.14.b* to *1.15.a* or higher, you're back within our support policies.
+* If the oldest supported AKS minor version is *1.27* and you're on *1.26* or older, you're outside of support.
+* When you successfully upgrade from *1.26* to *1.27* or higher, you're back within our support policies.
 
 Downgrades aren't supported.
 
@@ -302,16 +299,16 @@ The [version skew policy](https://kubernetes.io/releases/version-skew-policy/) n
 
 When you upgrade a supported AKS cluster, Kubernetes minor versions can't be skipped. Kubernetes control planes [version skew policy](https://kubernetes.io/releases/version-skew-policy/) doesn't support minor version skipping. For example, upgrades between:
 
-* *1.12.x* -> *1.13.x*: allowed.
-* *1.13.x* -> *1.14.x*: allowed.
-* *1.12.x* -> *1.14.x*: not allowed.
+* *1.28.x* -> *1.29.x*: allowed.
+* *1.27.x* -> *1.28.x*: allowed.
+* *1.27.x* -> *1.29.x*: not allowed.
 
-To upgrade from *1.12.x* -> *1.14.x*:
+To upgrade from *1.27.x* -> *1.29.x*:
 
-1. Upgrade from *1.12.x* -> *1.13.x*.
-2. Upgrade from *1.13.x* -> *1.14.x*.
+1. Upgrade from *1.27.x* -> *1.28.x*.
+2. Upgrade from *1.28.x* -> *1.29.x*.
 
-Skipping multiple versions can only be done when upgrading from an unsupported version back into the minimum supported version. For example, you can upgrade from an unsupported *1.10.x* to a supported *1.15.x* if *1.15* is the minimum supported minor version.
+Skipping multiple versions can only be done when upgrading from an unsupported version back into the minimum supported version. For example, you can upgrade from an unsupported *1.25.x* to a supported *1.27.x* if *1.27* is the minimum supported minor version.
 
 When performing an upgrade from an _unsupported version_ that skips two or more minor versions, the upgrade is performed without any guarantee of functionality and is excluded from the service-level agreements and limited warranty.Clusters running _unsupported version_ has the flexibility of decoupling control plane upgrades with node pool upgrades. However if your version is significantly out of date, we recommend that you re-create the cluster.
 

articles/api-management/breaking-changes/workspaces-breaking-changes-june-2024.md

@@ -11,7 +11,7 @@ ms.author: danlep
 
 # Workspaces - breaking changes (June 2024)
 
-[!INCLUDE [api-management-availability-premium](../../../includes/api-management-availability-premium.md)]
+[!INCLUDE [api-management-availability-premium-dev-standard](../../../includes/api-management-availability-premium-dev-standard.md)]
 
 On 14 June 2024, as part of our development of [workspaces](../workspaces-overview.md) (preview) in Azure API Management, we're introducing several breaking changes. 
 
@@ -70,4 +70,4 @@ If you have questions, get answers from community experts in [Microsoft Q&A](htt
 
 ## Related content
 
-See all [upcoming breaking changes and feature retirements](overview.md).
+See all [upcoming breaking changes and feature retirements](overview.md).

articles/azure-arc/vmware-vsphere/quick-start-connect-vcenter-to-arc-using-script.md

@@ -44,7 +44,7 @@ First, the script deploys a virtual appliance called [Azure Arc resource bridge]
 
 - A resource pool or a cluster with a minimum capacity of 16 GB of RAM and four vCPUs.
 
-- A datastore with a minimum of 100 GB of free disk space available through the resource pool or cluster.
+- A datastore with a minimum of 200 GB of free disk space available through the resource pool or cluster.
 
 > [!NOTE]
 > Azure Arc-enabled VMware vSphere supports vCenter Server instances with a maximum of 9,500 virtual machines (VMs). If your vCenter Server instance has more than 9,500 VMs, we don't recommend that you use Azure Arc-enabled VMware vSphere with it at this point.

articles/azure-netapp-files/manage-availability-zone-volume-placement.md

@@ -32,6 +32,9 @@ You can deploy new volumes in the logical availability zone of your choice. You
 
 * <a name="file-path-uniqueness"></a> For volumes in different availability zones, Azure NetApp Files allows you to create volumes with the same file path (NFS), share name (SMB), or volume path (dual-protocol). This feature is currently in preview. 
 
+    >[!IMPORTANT]
+    >Once a volume is created with the same file path as another volume in a different availability zone, the volume has the same level of support as other volumes deployed in the subscription without this feature enabled. For example, if there's an issue with other generally available features on the volume such as snapshots, it's supported because the problem is unrelated to the ability to create volumes with the same file path in different availability zones.
+
     You need to register the feature before using it for the first time. After registration, the feature is enabled and works in the background. No UI control is required.
 
     1. Register the feature: 

articles/communication-services/resources/troubleshooting/voice-video-calling/call-setup-issues/call-setup-takes-too-long.md

@@ -0,0 +1,27 @@
+---
+title: Call setup issues - The call setup takes too long
+titleSuffix: Azure Communication Services - Troubleshooting Guide
+description: Learn how to troubleshoot when the call setup takes too long.
+author: sloanster
+ms.author: micahvivion
+
+services: azure-communication-services
+ms.date: 04/10/2024
+ms.topic: troubleshooting
+ms.service: azure-communication-services
+ms.subservice: calling
+---
+
+# The call setup takes too long
+When the user makes a call or accepts a call, multiple steps and messages are exchanged between the signaling layer and media transport.
+If the call setup takes too long, it's often due to network issues.
+Another factor that contributes to call setup delay is the stream acquisition delay, which is the time it takes for a browser to get the media stream.
+Additionally, device performance can also affect call setup time. For example, a busy browser may take longer to schedule the API request, resulting in a longer call setup time.
+
+## How to detect using the SDK
+The application can calculate the delay between when the call is initiated and when it's connected.
+
+## How to mitigate or resolve
+If a user consistently experiences long call setup times, they should check their network for issues such as slow network speed, long round trip time, or high packet loss.
+These issues can affect call setup time because the signaling layer uses a `TCP` connection, and factors such as retransmissions can cause delays.
+Additionally, if the user suspects the delay comes from stream acquisition, they should check their devices. For example, they can choose a different audio input device.