Merge pull request #228495 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: huypub

articles/active-directory/conditional-access/resilience-defaults.md

@@ -54,7 +54,7 @@ If the required controls of a policy weren't previously satisfied, the policy is
 - Country location (resolving new IP or GPS coordinates)
 - Authentication strengths
 
-When active, the Backup Authentication Service doesn't evaluate authentication methods required by [authentication strengths](../authentication/concept-authentication-strengths.md). If you used a non-phishing-resistant authentication method before an outage, during an outage you aren't be prompted for multifactor authentication even if accessing a resource protected by a Conditional Access policy with a phishing-resistant authentication strength.
+When active, the Backup Authentication Service doesn't evaluate authentication methods required by [authentication strengths](../authentication/concept-authentication-strengths.md). If you used a non-phishing-resistant authentication method before an outage, during an outage you aren't prompted for multifactor authentication even if accessing a resource protected by a Conditional Access policy with a phishing-resistant authentication strength.
 
 ## Resilience defaults enabled
 

articles/active-directory/devices/howto-vm-sign-in-azure-ad-linux.md

@@ -43,7 +43,7 @@ The following Linux distributions are currently supported for deployments in a s
 | CentOS | CentOS 7, CentOS 8 |
 | Debian | Debian 9, Debian 10, Debian 11 |
 | openSUSE | openSUSE Leap 42.3, openSUSE Leap 15.1+ |
-| RedHat Enterprise Linux (RHEL) | RHEL 7.4 to RHEL 7.10, RHEL 8.3+ |
+| RedHat Enterprise Linux (RHEL) | RHEL 7.4 to RHEL 7.9, RHEL 8.3+ |
 | SUSE Linux Enterprise Server (SLES) | SLES 12, SLES 15.1+ |
 | Ubuntu Server | Ubuntu Server 16.04 to Ubuntu Server 22.04 |
 

articles/aks/quickstart-helm.md

@@ -170,7 +170,7 @@ description: A Helm chart for Kubernetes
 
 dependencies:
   - name: redis
-    version: 14.7.1
+    version: 17.3.17
     repository: https://charts.bitnami.com/bitnami
 
 ...

articles/cdn/create-profile-endpoint-bicep.md

@@ -46,14 +46,14 @@ One Azure resource is defined in the Bicep file:
 
     ```azurecli
     az group create --name exampleRG --location eastus
-    az deployment group create --resource-group exampleRG --template-file main.bicep --parameters profileName=<profile-name> endpointName=<endpoint-name> originURL=<origin-url>
+    az deployment group create --resource-group exampleRG --template-file main.bicep --parameters profileName=<profile-name> endpointName=<endpoint-name> originUrl=<origin-url>
     ```
 
     # [PowerShell](#tab/PowerShell)
 
     ```azurepowershell
     New-AzResourceGroup -Name exampleRG -Location eastus
-    New-AzResourceGroupDeployment -ResourceGroupName exampleRG -TemplateFile ./main.bicep -profileName "<profile-name>" -endpointName "<endpoint-name>" -originURL "<origin-url>"
+    New-AzResourceGroupDeployment -ResourceGroupName exampleRG -TemplateFile ./main.bicep -profileName "<profile-name>" -endpointName "<endpoint-name>" -originUrl "<origin-url>"
     ```
 
     ---

articles/iot-dps/quick-enroll-device-tpm.md

@@ -389,7 +389,7 @@ AToAAQALAAMAsgAgg3GXZ0SEs/gakMyNRqXXJP1S124GUgtk8qHaGzMUaaoABgCAAEMAEAgAAAAAAAEA
 
 :::zone-end
 
-To verify that the enrollment group has been created:
+To verify that the individual enrollment has been created:
 
 1. In the Azure portal, select your Device Provisioning Service.
 

articles/storage/common/storage-use-azcopy-blobs-copy.md

@@ -31,7 +31,7 @@ See the [Get started with AzCopy](storage-use-azcopy-v10.md) article to download
 
 Apply the following guidelines to your AzCopy commands.
 
-- Source and destination accounts must belong to the same Azure AD tenant.
+- If you're using Azure AD authorization for both source and destination, then both accounts must belong to the same Azure AD tenant.
 
 - Your client must have network access to both the source and destination storage accounts. To learn how to configure the network settings for each storage account, see [Configure Azure Storage firewalls and virtual networks](storage-network-security.md?toc=/azure/storage/blobs/toc.json).
 

articles/virtual-machines/linux/n-series-driver-setup.md

@@ -110,14 +110,11 @@ sudo reboot
       ```
 
 3. Reconnect to the VM and continue installation with the following commands:
-
    ```bash
    sudo rpm -Uvh https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
-   sudo yum install dkms
-   
-   sudo wget https://developer.download.nvidia.com/compute/cuda/repos/rhel7/x86_64/cuda-rhel7.repo -O /etc/yum.repos.d/cuda-rhel7.repo
-
-   sudo yum install cuda-drivers
+   sudo yum-config-manager --add-repo https://developer.download.nvidia.com/compute/cuda/repos/rhel7/x86_64/cuda-rhel7.repo
+   sudo yum clean all
+   sudo yum -y install nvidia-driver-latest-dkms cuda-drivers
    ```
 
    The installation can take several minutes.