Merge pull request #286812 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: Albertyang0

articles/azure-arc/kubernetes/azure-rbac.md

@@ -86,10 +86,10 @@ For a conceptual overview of this feature, see [Azure RBAC on Azure Arc-enabled
     1. Add the following specification under `volumes`:
 
        ```yml
-       - name: azure-rbac
-           hostPath:
+       - hostPath
            path: /etc/guard
            type: Directory
+       name: azure-rbac
        ```
 
     1. Add the following specification under `volumeMounts`:

articles/azure-arc/kubernetes/extensions-release.md

@@ -215,10 +215,9 @@ For more information, see [What is Edge Storage Accelerator?](../edge-storage-ac
 
 ## Connected registry on Arc-enabled Kubernetes
 
-- **Supported distributions**: Connected registry for Arc-enabled Kubernetes clusters.
-- **Supported Azure regions**: All regions where Azure Arc-enabled Kubernetes is available.
+- **Supported distributions**: AKS enabled by Azure Arc, Kubernetes using kind.
 
-The connected registry extension for Azure Arc enables you to sync container images between your Azure Container Registry (ACR) and your local on-prem Azure Arc-enabled Kubernetes cluster. The extension is deployed to the local or remote cluster and uses a synchronization schedule and window to sync images between the on-prem connected registry and the cloud ACR registry.
+The connected registry extension for Azure Arc allows you to synchronize container images between your Azure Container Registry (ACR) and your on-premises Azure Arc-enabled Kubernetes cluster. This extension can be deployed to either a local or remote cluster and utilizes a synchronization schedule and window to ensure seamless syncing of images between the on-premises connected registry and the cloud-based ACR.
 
 For more information, see [Connected Registry for Arc-enabled Kubernetes clusters](../../container-registry/quickstart-connected-registry-arc-cli.md).
 

articles/databox/data-box-deploy-export-ordered.md

@@ -35,6 +35,9 @@ Complete the following configuration prerequisites for Data Box service and devi
 * Make sure that you have an existing resource group that you can use with your Azure Data Box.
 
 * Make sure that your Azure Storage account that you want to export data from is one of the supported Storage account types as described [Supported storage accounts for Data Box](data-box-system-requirements.md#supported-storage-accounts).
+  
+> [!NOTE] 
+> The Export functionality will not include Access Control List (ACL) or metadata regarding the files and folders. If you are exporting Azure Files data, you may consider using a tool such as Robocopy to apply ACLs to the target folders prior to import. 
 
 ### For device
 

articles/import-export/storage-import-export-data-to-files.md

@@ -41,7 +41,7 @@ Before you create an import job to transfer data into Azure Files, carefully rev
 
 ## Step 1: Prepare the drives
 
-This step generates a journal file. The journal file stores basic information such as drive serial number, encryption key, and storage account details.
+Attach the external disk to the file share and run WAImportExport.exe file. This step generates a journal file. The journal file stores basic information such as drive serial number, encryption key, and storage account details.
 
 Do the following steps to prepare the drives.
 

articles/openshift/create-cluster.md

@@ -6,7 +6,7 @@ ms.author: johnmarc
 ms.topic: article
 ms.service: azure-redhat-openshift
 ms.custom: devx-track-azurecli
-ms.date: 06/12/2024
+ms.date: 09/13/2024
 #Customer intent: As a developer, I want learn how to create an Azure Red Hat OpenShift cluster, scale it, and then clean up resources so that I am not charged for what I'm not using.
 ---
 
@@ -105,7 +105,7 @@ If you provide a custom domain for your cluster, note the following points:
 
 * The OpenShift console will be available at a URL such as `https://console-openshift-console.apps.example.com`, instead of the built-in domain `https://console-openshift-console.apps.<random>.<location>.aroapp.io`.
 
-* By default, OpenShift uses self-signed certificates for all of the routes created on custom domains `*.apps.example.com`.  If you choose to use custom DNS after connecting to the cluster, you will need to follow the OpenShift documentation to [configure a custom CA for your ingress controller](https://docs.openshift.com/container-platform/4.6/security/certificates/replacing-default-ingress-certificate.html) and a [custom CA for your API server](https://docs.openshift.com/container-platform/4.6/security/certificates/api-server.html).
+* By default, OpenShift uses self-signed certificates for all of the routes created on custom domains `*.apps.example.com`.  If you choose to use custom DNS after connecting to the cluster, you will need to follow the OpenShift documentation to [configure a custom CA for your ingress controller](https://docs.openshift.com/container-platform/latest/security/certificates/replacing-default-ingress-certificate.html) and a [custom CA for your API server](https://docs.openshift.com/container-platform/latest/security/certificates/api-server.html).
 
 ### Create a virtual network containing two empty subnets
 
@@ -208,8 +208,14 @@ Run the following command to create a cluster. If you choose to use either of th
 * Optionally, you can [pass your Red Hat pull secret](#get-a-red-hat-pull-secret-optional), which enables your cluster to access Red Hat container registries along with other content. Add the `--pull-secret @pull-secret.txt` argument to your command.
 * Optionally, you can [use a custom domain](#prepare-a-custom-domain-for-your-cluster-optional). Add the `--domain foo.example.com` argument to your command, replacing `foo.example.com` with your own custom domain.
 
+
+<!--
 > [!NOTE]
 > If you're adding any optional arguments to your command, be sure to close the argument on the preceding line of the command with a trailing backslash.
+-->
+
+> [!NOTE]
+> The maximum number of worker nodes definable at creation time is 50. You can scale out up to 250 nodes after the cluster is created.
 
 ```azurecli-interactive
 az aro create \
@@ -220,7 +226,11 @@ az aro create \
   --worker-subnet worker-subnet
 ```
 
-After executing the `az aro create` command, it normally takes about 35 minutes to create a cluster.
+After executing the `az aro create` command, it normally takes about 45 minutes to create a cluster.
+
+#### Large scale ARO clusters
+
+If you are looking to deploy an Azure Red Hat OpenShift cluster with more than 100 worker nodes please see the [Deploy a large Azure Red Hat OpenShift cluster](howto-large-clusters.md)
 
 #### Selecting a different ARO version
 

articles/service-bus-messaging/service-bus-integrate-with-rabbitmq.md

@@ -17,7 +17,7 @@ Here's a few scenarios in which we can make use of these capabilities:
 - **Hybrid Cloud**: Your company just acquired a third party that uses RabbitMQ for their messaging needs. They are on a different cloud. While they transition to Azure you can already start sharing data by bridging RabbitMQ with Azure Service Bus.
 - **Third-Party Integration**: A third party uses RabbitMQ as a broker, and wants to send their data to us, but they are outside our organization. We can provide them with SAS Key giving them access to a limited set of Azure Service Bus queues where they can forward their messages to.
 
-The list goes on, but we can solve most of these use cases by bridging RabbitMQ to Azure.
+The list goes on, but we can solve most of these use cases by [bridging](/azure/architecture/patterns/messaging-bridge) RabbitMQ to Azure.
 
 First you need to create a free Azure account by signing up [here](https://azure.microsoft.com/free/)