Merge pull request #229995 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/azure-cni-overlay.md

@@ -59,7 +59,7 @@ The following are additional factors to consider when planning pods IP address s
 
 ## Network security groups
 
-Pod to pod traffic with Azure CNI Overlay is not encapsulated and subnet [network security group][nsgs] rules are applied. If the subnet NSG contains deny rules that would impact the pod CIDR traffic, make sure the following rules are in place to ensure proper cluster functionality (in addition to all [AKS egress requirements][aks-egress]):
+Pod to pod traffic with Azure CNI Overlay is not encapsulated and subnet [network security group][nsg] rules are applied. If the subnet NSG contains deny rules that would impact the pod CIDR traffic, make sure the following rules are in place to ensure proper cluster functionality (in addition to all [AKS egress requirements][aks-egress]):
 
 * Traffic from the node CIDR to the node CIDR on all ports and protocols
 * Traffic from the node CIDR to the pod CIDR on all ports and protocols (required for service traffic routing)
@@ -172,4 +172,4 @@ To learn how to utilize AKS with your own Container Network Interface (CNI) plug
 [az-feature-show]: /cli/azure/feature#az-feature-show
 [aks-egress]: limit-egress-traffic.md
 [aks-network-policies]: use-network-policies.md
-[nsg]: /azure/virtual-network/network-security-groups-overview
+[nsg]: ../virtual-network/network-security-groups-overview.md

articles/mysql/quickstart-create-mysql-server-database-using-bicep.md

@@ -1,5 +1,5 @@
 ---
-title: 'Quickstart: Create an Azure DB for MySQL - Bicep'
+title: 'Quickstart: Create an Azure Database for MySQL - Bicep'
 description: In this Quickstart, learn how to create an Azure Database for MySQL server with virtual network integration using Bicep.
 author: rothja
 ms.author: jroth

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

@@ -235,19 +235,9 @@ southeastasia - 20.24.186.80
 
 ### Update expired RHUI client certificate on a VM
 
-If you are using an older RHEL VM image, for example, RHEL 7.4 (image URN: `RedHat:RHEL:7.4:7.4.2018010506`), you will experience connectivity issues to RHUI due to a now-expired TLS/SSL client certificate. The error you see may look like _"SSL peer rejected your certificate as expired"_ or _"Error: Cannot retrieve repository metadata (repomd.xml) for repository: ... Please verify its path and try again"_. To overcome this problem, please update the RHUI client package on the VM using the following command:
+If you experience RHUI certificate issues from your Azure RHEL PAYG VM, reference the [troubleshooting guidance for RHUI certificate issues in Azure](/troubleshoot/azure/virtual-machines/troubleshoot-linux-rhui-certificate-issues).
 
-```bash
-sudo yum update -y --disablerepo='*' --enablerepo='*microsoft*'
-```
-
-Alternatively, running `sudo yum update` may also update the client certificate package (depending on your RHEL version), despite "expired SSL certificate" errors you will see for other repositories. If this update is successful, normal connectivity to other RHUI repositories should be restored, so you will be able to run `sudo yum update` successfully.
-
-If you run into a 404 error while running a `yum update`, try the following to refresh your yum cache:
-```bash
-sudo yum clean all;
-sudo yum makecache
-```
+ 
 
 ### Troubleshoot connection problems to Azure RHUI
 If you experience problems connecting to Azure RHUI from your Azure RHEL PAYG VM, follow these steps: