Merge pull request #214740 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/aks/csi-secrets-store-identity-access.md

@@ -43,7 +43,7 @@ Azure AD workload identity (preview) is supported on both Windows and Linux clus
     az account set --subscription $subscriptionID
     az identity create --name $UAMI --resource-group $resourceGroupName
     export USER_ASSIGNED_CLIENT_ID="$(az identity show -g $resourceGroupName --name $UAMI --query 'clientId' -o tsv)"
-    export IDENTITY_TENANT=$(az aks show --name $clusterName --resource-group $RG --query aadProfile.tenantId -o tsv)
+    export IDENTITY_TENANT=$(az aks show --name $clusterName --resource-group $resourceGroupName --query aadProfile.tenantId -o tsv)
     ```
 
 2. You need to set an access policy that grants the workload identity permission to access the Key Vault secrets, access keys, and certificates. The rights are assigned using the `az keyvault set-policy` command shown below.
@@ -88,7 +88,7 @@ Azure AD workload identity (preview) is supported on both Windows and Linux clus
 
     ```bash
     export federatedIdentityName="aksfederatedidentity" # can be changed as needed
-    az identity federated-credential create --name $federatedIdentityName --identity-name $UAMI --resource-group $RG --issuer ${AKS_OIDC_ISSUER} --subject system:serviceaccount:${serviceAccountNamespace}:${serviceAccountName}
+    az identity federated-credential create --name $federatedIdentityName --identity-name $UAMI --resource-group $resourceGroupName --issuer ${AKS_OIDC_ISSUER} --subject system:serviceaccount:${serviceAccountNamespace}:${serviceAccountName}
     ```
 5. Deploy a `SecretProviderClass` by using the following YAML script, noticing that the variables will be interpolated:
 

articles/azure-arc/data/uninstall-azure-arc-data-controller.md

@@ -158,7 +158,9 @@ kubectl delete crd dags.sql.arcdata.microsoft.com
 kubectl delete crd exporttasks.tasks.arcdata.microsoft.com
 kubectl delete crd monitors.arcdata.microsoft.com
 kubectl delete crd activedirectoryconnectors.arcdata.microsoft.com
-
+kubectl delete crd failovergroups.sql.arcdata.microsoft.com
+kubectl delete crd kafkas.arcdata.microsoft.com
+kubectl delete crd otelcollectors.arcdata.microsoft.com
 
 ## Delete Cluster roles and Cluster role bindings
 kubectl delete clusterrole arcdataservices-extension

articles/deployment-environments/configure-catalog-item.md

@@ -58,6 +58,7 @@ Provide a new catalog item to your development team as follows:
         ```
             name: WebApp
             version: 1.0.0
+            summary: Azure Web App Environment
             description: Deploys an Azure Web App without a data store
             runner: ARM
             templatePath: azuredeploy.json

articles/spring-apps/connect-managed-identity-to-azure-sql.md

@@ -63,9 +63,6 @@ spring.datasource.url=jdbc:sqlserver://$AZ_DATABASE_NAME.database.windows.net:14
 
 Configure your app deployed to Azure Spring to connect to an SQL Database with a system-assigned managed identity using the `az spring connection create` command, as shown in the following example.
 
-> [!NOTE]
-> This command requires you to run the latest [edge build of Azure CLI](https://github.com/Azure/azure-cli/blob/dev/doc/try_new_features_before_release.md). [Download and install the edge builds](https://github.com/Azure/azure-cli#edge-builds) for your platform.
-
 ```azurecli-interactive
 az spring connection create sql \
     --resource-group $SPRING_APP_RESOURCE_GROUP \

articles/virtual-machines/workloads/redhat/redhat-images.md

@@ -164,6 +164,13 @@ RHEL 8.0      |N/A                            | No EUS is available from Red Hat
 
 The latest RHEL for SAP images will be connected to the Update Services for SAP Solutions subscriptions (E4S). For more information about E4S, see the Red Hat [documentation](https://access.redhat.com/support/policy/updates/errata#Update_Services_for_SAP_Solutions).
 
+>[!NOTE]
+> Customers looking to update OS connected to E4S repositories to the latest version can enforce the latest available EUS minor-release in /etc/yum/vars/releasever file without switching to non-EUS.
+> 
+> For information on RedHat EUS availability, see [Red Hat Enterprise Linux life cycle](https://access.redhat.com/support/policy/updates/errata).
+> 
+> For steps on how to enforce a minor version refer, [RedHat KB#4251981](https://access.redhat.com/solutions/4251981). Steps outlined in this RedHat KB also apply to RHEL8.* versions.
+
 #### RHEL images with E4S
 
 Images from the following offers created after December 2019 are connected to E4S repositories: