Merge pull request #266173 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)

Author: v-alje

articles/ai-services/computer-vision/includes/read-editions.md

@@ -17,7 +17,7 @@ ms.author: pafarley
 >
 > | Input | Examples | Read edition | Benefit |
 > |----------|--------------|-------------------------|-------------------------|
-> | **Images**: General, in-the-wild images |  labels, street signs, and posters | [OCR for images (version 4.0 preview)](../concept-ocr.md) | Optimized for general, non-document images with a performance-enhanced synchronous API that makes it easier to embed OCR in your user experience scenarios.
+> | **Images**: General, in-the-wild images |  labels, street signs, and posters | [OCR for images (version 4.0)](../concept-ocr.md) | Optimized for general, non-document images with a performance-enhanced synchronous API that makes it easier to embed OCR in your user experience scenarios.
 > | **Documents**: Digital and scanned, including images | books, articles, and reports | [Document Intelligence read model](../../../ai-services/document-intelligence/concept-read.md) | Optimized for text-heavy scanned and digital documents with an asynchronous API to help automate intelligent document processing at scale.
 >
 > **About Azure AI Vision v3.2 GA Read**

articles/aks/azure-files-csi.md

@@ -346,7 +346,10 @@ mountOptions:
 
 ### Create NFS file share storage class
 
-Create a file named `nfs-sc.yaml` and copy the manifest below. For a list of supported `mountOptions`, see [NFS mount options][nfs-file-share-mount-options]
+Create a file named `nfs-sc.yaml` and copy the manifest below. For a list of supported `mountOptions`, see [NFS mount options][nfs-file-share-mount-options].
+
+> [!NOTE]
+> `vers`, `minorversion`, `sec` are configured by the Azure File CSI driver. Specifying a value in your manifest for these properties aren't supported.
 
 ```yml
 apiVersion: storage.k8s.io/v1
@@ -510,4 +513,4 @@ The output of the commands resembles the following example:
 [statically-provision-a-volume]: azure-csi-files-storage-provision.md#statically-provision-a-volume
 [azure-private-endpoint-dns]: ../private-link/private-endpoint-dns.md#azure-services-dns-zone-configuration
 [azure-netapp-files-mount-options-best-practices]: ../azure-netapp-files/performance-linux-mount-options.md#rsize-and-wsize
-[nfs-file-share-mount-options]: ../storage/files/storage-files-how-to-mount-nfs-shares.md#mount-options
+[nfs-file-share-mount-options]: ../storage/files/storage-files-how-to-mount-nfs-shares.md#mount-options

articles/aks/configure-kubenet-dual-stack.md

@@ -298,10 +298,7 @@ Once the cluster has been created, you can deploy your workloads. This article w
 ## Expose the workload via a `LoadBalancer` type service
 
 > [!IMPORTANT]
-> There are currently **two limitations** pertaining to IPv6 services in AKS.
->
-> 1. Azure Load Balancer sends health probes to IPv6 destinations from a link-local address. In Azure Linux node pools, this traffic can't be routed to a pod, so traffic flowing to IPv6 services deployed with `externalTrafficPolicy: Cluster` fail. IPv6 services must be deployed with `externalTrafficPolicy: Local`, which causes `kube-proxy` to respond to the probe on the node.
-> 2. Starting from AKS v1.27, you can directly create a dualstack service. However, for older versions, only the first IP address for a service will be provisioned to the load balancer, so a dual-stack service only receives a public IP for its first-listed IP family. To provide a dual-stack service for a single deployment, please create two services targeting the same selector, one for IPv4 and one for IPv6.
+> Starting in AKS v1.27, you can create a dual-stack LoadBalancer service which will be provisioned with 1 IPv4 public IP and 1 IPv6 public IP. However, in older versions, only the first IP address for a service will be provisioned to the load balancer, so a dual-stack service only receives a public IP for its first-listed IP family. To provide a dual-stack service for a single deployment, please create two services targeting the same selector, one for IPv4 and one for IPv6.
 
 # [kubectl](#tab/kubectl)
 

articles/azure-monitor/containers/kubernetes-monitoring-enable.md

@@ -612,6 +612,8 @@ As of version 6.4.0-main-02-22-2023-3ee44b9e of the Managed Prometheus addon con
    * `memory`
    * `process`
    * `cpu_info`
+   
+   For more collectors, please see [Prometheus exporter for Windows metrics](https://github.com/prometheus-community/windows_exporter#windows_exporter).
 
    Deploy the [windows-exporter-daemonset YAML](https://github.com/prometheus-community/windows_exporter/blob/master/kubernetes/windows-exporter-daemonset.yaml) file:
 

articles/azure-resource-manager/bicep/bicep-extensibility-kubernetes-provider.md

@@ -13,13 +13,14 @@ The Kubernetes provider allows you to create Kubernetes resources directly with
 > [!NOTE]
 > Kubernetes provider is not currently supported for private clusters:
 > 
-> ```json
+> ```bicep
 > resource AKS 'Microsoft.ContainerService/managedClusters@2023-01-02-preview' = {
+>  ...
 >  properties: {
->   "apiServerAccessProfile": {
->     "enablePrivateCluster": "true"
->     }
+>   apiServerAccessProfile: {
+>     enablePrivateCluster: true
 >   }
+>  }
 > }
 > 
 > ```

articles/container-apps/ingress-how-to.md

@@ -158,7 +158,7 @@ You can expose additional TCP ports from your application. To learn more, see th
 Adding additional TCP ports can be done through the CLI by referencing a YAML file with your TCP port configurations.
 
 ```azurecli
-az containerapp create
+az containerapp create \
     --name <app-name> \
     --resource-group <resource-group> \
     --yaml <your-yaml-file>