Merge branch 'main' into release-blob-backup

Author: v-alje

.openpublishing.redirection.json

@@ -4502,6 +4502,11 @@
             "source_path_from_root": "/articles/kubernetes-fleet/configuration-propagation.md",
             "redirect_url": "/azure/kubernetes-fleet/resource-propagation"
         },
+        {
+            "source_path_from_root": "/articles/aks/network-observability-byo-cli.md",
+            "redirect_url": "/azure/aks/network-observability-overview",
+            "redirect_document_id": false
+        },
         {
             "source_path_from_root": "/articles/orbital/license-spacecraft.md",
             "redirect_url": "/azure/orbital/initiate-licensing",

articles/ai-services/document-intelligence/faq.yml

@@ -59,11 +59,11 @@ sections:
           - You can find more details in the [technical community blog](https://techcommunity.microsoft.com/t5/azure-ai-services-blog/document-generative-ai-the-power-of-azure-ai-document/ba-p/3875015).
 
       - question: |
-          Does Document Intelligence offer a semantic chunking solution for retrieval-augmented generation?
+         Can Document Intelligence help with semantic chunking within documents for retrieval-augmented generation?
         answer: |
           **Yes.**
-
-          Semantic chunking is a key step in retrieval-augmented generation (RAG) to ensure its efficient storage and retrieval.
+          
+          Document Intelligence can provide the building blocks to enable semantic chunking. Semantic chunking is a key step in retrieval-augmented generation (RAG) to ensure its efficient storage and retrieval.
 
           - Document Intelligence provides a layout model that segments documents into coherent units based on their semantic content.
 

articles/ai-services/openai/concepts/models.md

@@ -312,7 +312,7 @@ The following Embeddings models are available with [Azure Government](/azure/azu
 
 ### Assistants (Preview)
 
-For Assistants you need a combination of a supported model, and a supported region. Certain tools and capabilities require the latest models. The following models are available in the Assistants API, SDK, Azure AI Studio and Azure OpenAI Studio. The following table is for pay-as-you-go. For information on Provisioned Throughput Unit (PTU) availability, see [provisioned throughput](./provisioned-throughput.md). 
+For Assistants you need a combination of a supported model, and a supported region. Certain tools and capabilities require the latest models. The following models are available in the Assistants API, SDK, Azure AI Studio and Azure OpenAI Studio. The following table is for pay-as-you-go. For information on Provisioned Throughput Unit (PTU) availability, see [provisioned throughput](./provisioned-throughput.md). The listed models and regions can be used with both Assistants v1 and v2.
 
 | Region | `gpt-35-turbo (0613)` | `gpt-35-turbo (1106)`| `fine tuned gpt-3.5-turbo-0125` | `gpt-4 (0613)` | `gpt-4 (1106)` | `gpt-4 (0125)` | `gpt-4o (2024-05-13)` |
 |-----|:---:|:---:|:---:|:---:|:---:|:---:|:---:|

articles/ai-services/openai/how-to/use-your-data-securely.md

@@ -265,9 +265,10 @@ So far you have already setup each resource work independently. Next you need to
 |--|--|--|--|
 | `Search Index Data Reader` | Azure OpenAI | Azure AI Search | Inference service queries the data from the index. |
 | `Search Service Contributor` | Azure OpenAI | Azure AI Search | Inference service queries the index schema for auto fields mapping. Data ingestion service creates index, data sources, skill set, indexer, and queries the indexer status. |
-| `Storage Blob Data Contributor` | Azure OpenAI | Storage Account | Reads from the input container, and writes the preprocess result to the output container. |
-| `Cognitive Services OpenAI Contributor` | Azure AI Search | Azure OpenAI | Custom skill |
-| `Storage Blob Data Contributor` | Azure AI Search | Storage Account | Reads blob and writes knowledge store. |
+| `Storage Blob Data Contributor` | Azure OpenAI | Storage Account | Reads from the input container, and writes the preprocessed result to the output container. |
+| `Cognitive Services OpenAI Contributor` | Azure AI Search | Azure OpenAI | Custom skill. |
+| `Storage Blob Data Reader` | Azure AI Search | Storage Account | Reads document blobs and chunk blobs. |
+| `Cognitive Services OpenAI User` | Web app | Azure OpenAI | Inference. |
 
 
 In the above table, the `Assignee` means the system assigned managed identity of that resource.

articles/ai-services/speech-service/how-to-pronunciation-assessment.md

@@ -91,23 +91,23 @@ In the `SpeechRecognizer`, you can specify the language to learn or practice imp
 ::: zone pivot="programming-language-csharp"
 
 ```csharp
-var recognizer = new SpeechRecognizer(config, "en-US", audioInput);
+var recognizer = new SpeechRecognizer(speechConfig, "en-US", audioConfig);
 ```
 
 ::: zone-end  
 
 ::: zone pivot="programming-language-cpp"
 
 ```cpp
-auto recognizer = SpeechRecognizer::FromConfig(config, "en-US", audioConfig);
+auto recognizer = SpeechRecognizer::FromConfig(speechConfig, "en-US", audioConfig);
 ```
 
 ::: zone-end
 
 ::: zone pivot="programming-language-java"
 
 ```Java
-SpeechRecognizer recognizer = new SpeechRecognizer(config, "en-US", audioInput);
+SpeechRecognizer recognizer = new SpeechRecognizer(speechConfig, "en-US", audioConfig);
 ```
 
 ::: zone-end
@@ -131,15 +131,15 @@ speechConfig.speechRecognitionLanguage = "en-US";
 ::: zone pivot="programming-language-objectivec"
 
 ```ObjectiveC
-SPXSpeechRecognizer* speechRecognizer = [[SPXSpeechRecognizer alloc] initWithSpeechConfiguration:speechConfig language:@"en-US" audioConfiguration:pronAudioSource];
+SPXSpeechRecognizer* recognizer = [[SPXSpeechRecognizer alloc] initWithSpeechConfiguration:speechConfig language:@"en-US" audioConfiguration:audioConfig];
 ```
 
 ::: zone-end
 
 ::: zone pivot="programming-language-swift"
 
 ```swift
-let reco = try! SPXSpeechRecognizer(speechConfiguration: speechConfig, language: "en-US", audioConfiguration: audioInput)
+let recognizer = try! SPXSpeechRecognizer(speechConfiguration: speechConfig, language: "en-US", audioConfiguration: audioConfig)
 ```
 
 ::: zone-end

articles/aks/TOC.yml

@@ -693,8 +693,10 @@
             href: cost-analysis.md
         - name: Network Observability
           items:
+            - name: Network Observability
+              href: network-observability-managed-cli.md
             - name: Advanced Network Observability - Azure managed Prometheus and Grafana
-              href: advanced-network-observability-cli.md 
+              href: advanced-network-observability-cli.md
             - name: Advanced Network Observability - Bring Your Own Prometheus and Grafana
               href: advanced-network-observability-bring-your-own-cli.md
     - name: Service Mesh

articles/aks/azure-csi-blob-storage-provision.md

@@ -47,7 +47,7 @@ The following table includes parameters you can use to define a custom storage c
 |skuName | Specify an Azure storage account type (alias: `storageAccountType`). | `Standard_LRS`, `Premium_LRS`, `Standard_GRS`, `Standard_RAGRS` | No | `Standard_LRS`|
 |location | Specify an Azure location. | `eastus` | No | If empty, driver will use the same location name as current cluster.|
 |resourceGroup | Specify an Azure resource group name. | myResourceGroup | No | If empty, driver will use the same resource group name as current cluster.|
-|storageAccount | Specify an Azure storage account name.| storageAccountName | - No for blobfuse mount </br> - Yes for NFSv3 mount. |  - For blobfuse mount: if empty, driver finds a suitable storage account that matches `skuName` in the same resource group. If a storage account name is provided, storage account must exist. </br>  - For NFSv3 mount, storage account name must be provided.|
+|storageAccount | Specify an Azure storage account name.| storageAccountName | - No | When a specific storage account name is not provided, the driver will look for a suitable storage account that matches the account settings within the same resource group. If it fails to find a matching storage account, it will create a new one. However, if a storage account name is specified, the storage account must already exist. |
 |networkEndpointType| Specify network endpoint type for the storage account created by driver. If privateEndpoint is specified, a [private endpoint][storage-account-private-endpoint] is created for the storage account. For other cases, a service endpoint will be created for NFS protocol.<sup>1</sup> | `privateEndpoint` | No | For an AKS cluster, add the AKS cluster name to the Contributor role in the resource group hosting the VNET.|
 |protocol | Specify blobfuse mount or NFSv3 mount. | `fuse`, `nfs` | No | `fuse`|
 |containerName | Specify the existing container (directory) name. | container | No | If empty, driver creates a new container name, starting with `pvc-fuse` for blobfuse or `pvc-nfs` for NFS v3. |

articles/aks/azure-csi-files-storage-provision.md

@@ -5,7 +5,7 @@ description: Learn how to create a static or dynamic persistent volume with Azur
 ms.topic: article
 ms.custom: devx-track-azurecli
 ms.subservice: aks-storage
-ms.date: 06/28/2024
+ms.date: 07/09/2024
 author: tamram
 ms.author: tamram
 
@@ -57,6 +57,7 @@ The following table includes parameters you can use to define a custom storage c
 |shareName | Specify Azure file share name. | Existing or new Azure file share name. | No | If empty, driver generates an Azure file share name. |
 |shareNamePrefix | Specify Azure file share name prefix created by driver. | Share name can only contain lowercase letters, numbers, hyphens, and length should be fewer than 21 characters. | No |
 |skuName | Azure Files storage account type (alias: `storageAccountType`)| `Standard_LRS`, `Standard_ZRS`, `Standard_GRS`, `Standard_RAGRS`, `Standard_RAGZRS`,`Premium_LRS`, `Premium_ZRS` | No | `StandardSSD_LRS`<br> Minimum file share size for Premium account type is 100 GB.<br> ZRS account type is supported in limited regions.<br> NFS file share only supports Premium account type.|
+|storageAccount | Specify an Azure storage account name.| storageAccountName | - No | When a specific storage account name is not provided, the driver will look for a suitable storage account that matches the account settings within the same resource group. If it fails to find a matching storage account, it will create a new one. However, if a storage account name is specified, the storage account must already exist. |
 |storageEndpointSuffix | Specify Azure storage endpoint suffix. | `core.windows.net`, `core.chinacloudapi.cn`, etc. | No | If empty, driver uses default storage endpoint suffix according to cloud environment. For example, `core.windows.net`. |
 |tags | [Tags][tag-resources] are created in new storage account. | Tag format: 'foo=aaa,bar=bbb' | No | "" |
 |--- | **Following parameters are only for SMB protocol** | --- | --- |

articles/aks/dapr-settings.md

@@ -6,15 +6,15 @@ ms.author: hannahhunter
 ms.topic: article
 ms.custom: build-2023, devx-track-azurecli, linux-related-content
 ms.subservice: aks-developer
-ms.date: 04/01/2024
+ms.date: 07/09/2024
 ---
 
 # Configure the Dapr extension for your Azure Kubernetes Service (AKS) and Arc-enabled Kubernetes project
 
-Once you've [created the Dapr extension](./dapr.md), you can configure the [Dapr](https://dapr.io/) extension to work best for you and your project using various configuration options, like:
+After [creating the Dapr extension](./dapr.md), you can configure the [Dapr](https://dapr.io/) extension to work best for you and your project using various configuration options, like:
 
 - Limiting which of your nodes use the Dapr extension
-- Setting automatic CRD updates
+- Setting automatic custom resource definition (CRD) updates
 - Configuring the Dapr release namespace
 
 The extension enables you to set Dapr configuration options by using the `--configuration-settings` parameter in the Azure CLI or `configurationSettings` property in a Bicep template. 
@@ -137,7 +137,7 @@ properties: {
 
 ## Install Dapr in multiple availability zones while in HA mode
 
-By default, the placement service uses a storage class of type `standard_LRS`. It is recommended to create a **zone redundant storage class** while installing Dapr in HA mode across multiple availability zones. For example, to create a `zrs` type storage class, add the `storageaccounttype` parameter: 
+By default, the placement service uses a storage class of type `standard_LRS`. It's recommended to create a **zone redundant storage class** while installing Dapr in HA mode across multiple availability zones. For example, to create a `zrs` type storage class, add the `storageaccounttype` parameter: 
 
 ```yaml
 kind: StorageClass
@@ -186,7 +186,7 @@ You can configure the release namespace.
 
 # [Azure CLI](#tab/cli)
 
-The Dapr extension gets installed in the `dapr-system` namespace by default. To override it, use `--release-namespace`. Include the cluster `--scope` to redefine the namespace.
+The Dapr extension gets installed in the `dapr-system` namespace by default. To override it, use `--release-namespace`. To redefine the namespace, include the cluster `--scope`.
 
 ```azurecli
 az k8s-extension create \
@@ -218,7 +218,7 @@ properties: {
 
 ---
 
-[Learn how to configure the Dapr release namespace if you already have Dapr installed](./dapr-migration.md).
+[Learn how to configure the Dapr release namespace when migrating from Dapr open source to the Dapr extension](./dapr-migration.md).
 
 ## Show current configuration settings
 
@@ -240,7 +240,7 @@ az k8s-extension show --cluster-type managedClusters \
 >
 > HA is enabled by default. Disabling it requires deletion and recreation of the extension.
 
-To update your Dapr configuration settings, recreate the extension with the desired state. For example, assume we've previously created and installed the extension using the following configuration:
+To update your Dapr configuration settings, recreate the extension with the desired state. For example, let's say you previously created and installed the extension using the following configuration:
 
 ```azurecli-interactive
 az k8s-extension create --cluster-type managedClusters \
@@ -368,14 +368,13 @@ properties: {
 
 ## Meet network requirements
 
-The Dapr extension for AKS and Arc for Kubernetes requires the following outbound URLs on `https://:443` to function:
+The Dapr extension requires the following outbound URLs on `https://:443` to function on AKS and Arc for Kubernetes:
 1. `https://mcr.microsoft.com/daprio` URL for pulling Dapr artifacts.
-2. `https://linuxgeneva-microsoft.azurecr.io/` URL for pulling some Dapr dependencies.
-3. The [outbound URLs required for AKS or Arc for Kubernetes](../azure-arc/kubernetes/network-requirements.md). 
+1. The [outbound URLs required for AKS or Arc for Kubernetes](../azure-arc/kubernetes/network-requirements.md). 
 
 ## Next Steps
 
-Once you have successfully provisioned Dapr in your AKS cluster, try deploying a [sample application][sample-application].
+Once you successfully provisioned Dapr in your AKS cluster, try deploying a [sample application][sample-application].
 
 <!-- LINKS INTERNAL -->
 [deploy-cluster]: ./tutorial-kubernetes-deploy-cluster.md

articles/aks/long-term-support.md

@@ -128,7 +128,8 @@ To carry out an in-place upgrade to the latest LTS version, you need to specify
 az aks upgrade --resource-group myResourceGroup --name myAKSCluster --kubernetes-version 1.32.2
 ```
 > [!NOTE]
-> The next Long Term Support Version after 1.27 is to be determined. However Customers will get a minimum 6 months of overlap between 1.27 LTS and the next LTS version to plan upgrades.
+
+> 1.30 is the next LTS version after 1.27. Customers will be able to upgrade from 1.27 LTS to 1.30 LTS starting August, 2024. 1.27 LTS goes End of Life by July 2025.  
 > Kubernetes 1.32.2 is used as an example version in this article. Check the [AKS release tracker](release-tracker.md) for available Kubernetes releases.
 
 ## Frequently asked questions