Merge pull request #272990 from mohitp930/mp4222024-validation

v-dirichards · web-flow · commit b11787a60fa2 · 2024-04-25T10:20:23.000-05:00
Bulk update: Global effort to fix validation errors
diff --git a/articles/azure-vmware/architecture-hub-and-spoke.md b/articles/azure-vmware/architecture-hub-and-spoke.md
@@ -40,7 +40,7 @@ The architecture has the following main components:
 
 - **ExpressRoute Global Reach:** Enables the connectivity between on-premises and Azure VMware Solution private cloud. The connectivity between Azure VMware Solution and the Azure fabric is through ExpressRoute Global Reach only.
 
-- **S2S VPN considerations:** Connectivity to Azure VMware Solution private cloud using Azure S2S VPN is supported as long as it meets the [minimum network requirements](https://docs.vmware.com/en/VMware-HCX/4.4/hcx-user-guide/GUID-8128EB85-4E3F-4E0C-A32C-4F9B15DACC6D.html) for VMware HCX.
+- **S2S VPN considerations:** Connectivity to Azure VMware Solution private cloud using Azure S2S VPN is supported as long as it meets the [minimum network requirements](https://docs.vmware.com/en/VMware-HCX/4.8/hcx-user-guide/GUID-8128EB85-4E3F-4E0C-A32C-4F9B15DACC6D.html) for VMware HCX.
 
 - **Hub virtual network:** Acts as the central point of connectivity to your on-premises network and Azure VMware Solution private cloud.
 
diff --git a/articles/azure-vmware/azure-vmware-solution-platform-updates.md b/articles/azure-vmware/azure-vmware-solution-platform-updates.md
@@ -118,7 +118,7 @@ All new Azure VMware Solution private clouds are being deployed with VMware NSX-
 
 **VMware HCX Enterprise Edition - Default**
 
-VMware HCX Enterprise is now available and supported on Azure VMware Solution at no extra cost. VMware HCX Enterprise brings valuable [services](https://docs.vmware.com/en/VMware-HCX/4.5/hcx-user-guide/GUID-32AF32BD-DE0B-4441-95B3-DF6A27733EED.html), like Replicated Assisted vMotion (RAV) and Mobility Optimized Networking (MON). VMware HCX Enterprise is now automatically installed for all new VMware HCX add-on requests, and existing VMware HCX Advanced customers can upgrade to VMware HCX Enterprise using the Azure portal. Learn more on how to [Install and activate VMware HCX in Azure VMware Solution](install-vmware-hcx.md).
+VMware HCX Enterprise is now available and supported on Azure VMware Solution at no extra cost. VMware HCX Enterprise brings valuable [services](https://docs.vmware.com/en/VMware-HCX/4.9/hcx-user-guide/GUID-32AF32BD-DE0B-4441-95B3-DF6A27733EED.html), like Replicated Assisted vMotion (RAV) and Mobility Optimized Networking (MON). VMware HCX Enterprise is now automatically installed for all new VMware HCX add-on requests, and existing VMware HCX Advanced customers can upgrade to VMware HCX Enterprise using the Azure portal. Learn more on how to [Install and activate VMware HCX in Azure VMware Solution](install-vmware-hcx.md).
 
 **Azure Log Analytics - Monitor Azure VMware Solution**
 
diff --git a/articles/azure-vmware/install-vmware-hcx.md b/articles/azure-vmware/install-vmware-hcx.md
@@ -48,7 +48,7 @@ After HCX is deployed, follow the recommended [Next steps](#next-steps).
 
 ## VMware HCX license edition 
 
-HCX offers various [services](https://docs.vmware.com/en/VMware-HCX/4.5/hcx-user-guide/GUID-32AF32BD-DE0B-4441-95B3-DF6A27733EED.html#GUID-32AF32BD-DE0B-4441-95B3-DF6A27733EED) based on the type of license installed with the system. Advanced delivers basic connectivity and mobility services to enable hybrid interconnect and migration services. HCX Enterprise offers more services than what standard licenses provide. Some of those services include; Mobility Groups, Replication assisted vMotion (RAV), Mobility Optimized Networking, Network Extension High availability, OS assisted Migration, and others. 
+HCX offers various [services](https://docs.vmware.com/en/VMware-HCX/4.9/hcx-user-guide/GUID-32AF32BD-DE0B-4441-95B3-DF6A27733EED.html) based on the type of license installed with the system. Advanced delivers basic connectivity and mobility services to enable hybrid interconnect and migration services. HCX Enterprise offers more services than what standard licenses provide. Some of those services include; Mobility Groups, Replication assisted vMotion (RAV), Mobility Optimized Networking, Network Extension High availability, OS assisted Migration, and others. 
 
 >[!Note]
 > VMware HCX Enterprise is available for Azure VMware Solution customers at no additional cost.  
@@ -82,7 +82,7 @@ HCX offers various [services](https://docs.vmware.com/en/VMware-HCX/4.5/hcx-user
 - Downgrading from HCX Enterprise Edition to HCX Advanced is possible without redeploying. 
 
     1. Verify that you reverted to an HCX Advanced configuration state and you aren't using the Enterprise features. 
-    1. If you plan to downgrade, verify that no scheduled migrations, [Enterprise services](https://docs.vmware.com/en/VMware-HCX/4.5/hcx-user-guide/GUID-32AF32BD-DE0B-4441-95B3-DF6A27733EED.html#GUID-32AF32BD-DE0B-4441-95B3-DF6A27733EED) like RAV and HCX MON, etc. are in use. Open a [support request](https://rc.portal.azure.com/#create/Microsoft.Support) to request downgrade. 
+    1. If you plan to downgrade, verify that no scheduled migrations, [Enterprise services](https://docs.vmware.com/en/VMware-HCX/4.9/hcx-user-guide/GUID-32AF32BD-DE0B-4441-95B3-DF6A27733EED.html#GUID-32AF32BD-DE0B-4441-95B3-DF6A27733EED) like RAV and HCX MON, etc. are in use. Open a [support request](https://rc.portal.azure.com/#create/Microsoft.Support) to request downgrade. 
 
 ## Download and deploy the VMware HCX Connector on-premises 
 
diff --git a/articles/azure-vmware/upgrade-hcx-azure-vmware-solutions.md b/articles/azure-vmware/upgrade-hcx-azure-vmware-solutions.md
@@ -21,11 +21,11 @@ You can update HCX Connector and HCX Cloud systems during separate maintenance w
 
 - For more information about the upgrade path, see the [Product Interoperability Matrix](https://interopmatrix.vmware.com/Upgrade?productId=660). 
 - For information regarding VMware product compatibility by version, see the [Compatibility Matrix](https://interopmatrix.vmware.com/Interoperability?col=660,&row=0,).
-- Review VMware Software Versioning, Skew and Legacy Support Policies [here](https://docs.vmware.com/en/VMware-HCX/4.5/hcx-skew-policy/GUID-787FB2A1-52AF-483C-B595-CF382E728674.html).
+- Review VMware Software Versioning, Skew and Legacy Support Policies [here](https://docs.vmware.com/en/VMware-HCX/4.8/hcx-skew-policy/GUID-787FB2A1-52AF-483C-B595-CF382E728674.html).
 
 - Ensure HCX manager and site pair configurations are healthy.  
 
-- As part of HCX update planning, and to ensure that HCX components are updated successfully, review the service update considerations and requirements. For planning HCX upgrade, see [Planning for HCX Updates](https://docs.vmware.com/en/VMware-HCX/4.5/hcx-user-guide/GUID-61F5CED2-C347-4A31-8ACB-A4553BFC62E3.html). 
+- As part of HCX update planning, and to ensure that HCX components are updated successfully, review the service update considerations and requirements. For planning HCX upgrade, see [Planning for HCX Updates](https://docs.vmware.com/en/VMware-HCX/4.9/hcx-user-guide/GUID-61F5CED2-C347-4A31-8ACB-A4553BFC62E3.html). 
 
 - Ensure that you have a backup and snapshot of HCX connector in the on-premises environment, if applicable.
 - For more information, see the [HCX support policy for legacy vSphere environment](https://kb.vmware.com/s/article/82702).
@@ -35,7 +35,7 @@ You can update HCX Connector and HCX Cloud systems during separate maintenance w
 - Azure VMware Solution backs up HCX Cloud Manager configuration daily.
 
 
-- Use the appliance management interface to create backup of HCX in on-premises, see [Backing Up HCX Manager](https://docs.vmware.com/en/VMware-HCX/4.4/hcx-user-guide/GUID-6A9D1451-3EF3-4E49-B23E-A9A781E5214A.html). You can use the configuration backup to restore the appliance to its state before the backup. The contents of the backup file supersede configuration changes made before restoring the appliance. 
+- Use the appliance management interface to create backup of HCX in on-premises, see [Backing Up HCX Manager](https://docs.vmware.com/en/VMware-HCX/4.9/hcx-user-guide/GUID-6A9D1451-3EF3-4E49-B23E-A9A781E5214A.html). You can use the configuration backup to restore the appliance to its state before the backup. The contents of the backup file supersede configuration changes made before restoring the appliance. 
  
 - HCX cloud manager snapshots are taken automatically during upgrades to HCX 4.4 or later. HCX retains automatic snapshots for 24 hours before deleting them. To take a manual snapshot on HCX Cloud Manager or help with reverting from a snapshot, [create a support ticket](https://ms.portal.azure.com/#view/Microsoft_Azure_Support/HelpAndSupportBlade/~/overview). 
 
@@ -62,7 +62,7 @@ The HCX update is first applied to the HCX Manager systems.
 
 **Procedure**
 
-To follow the HCX Manager upgrade process, see [Upgrading the HCX Manager](https://docs.vmware.com/en/VMware-HCX/4.5/hcx-user-guide/GUID-02DB88E1-EC81-434B-9AE9-D100E427B31C.html) 
+To follow the HCX Manager upgrade process, see [Upgrading the HCX Manager](https://docs.vmware.com/en/VMware-HCX/4.9/hcx-user-guide/GUID-02DB88E1-EC81-434B-9AE9-D100E427B31C.html) 
 
 ### Upgrade HCX Service Mesh appliances 
 
@@ -81,24 +81,24 @@ While Service Mesh appliances are upgraded independently to the HCX Manager, the
 
 **Procedure**
  
-To follow the Service Mesh appliances upgrade process, see [Upgrading the HCX Service Mesh Appliances](https://docs.vmware.com/en/VMware-HCX/4.5/hcx-user-guide/GUID-EF89A098-D09B-4270-9F10-AEFA37CE5C93.html)   
+To follow the Service Mesh appliances upgrade process, see [Upgrading the HCX Service Mesh Appliances](https://docs.vmware.com/en/VMware-HCX/4.9/hcx-user-guide/GUID-EF89A098-D09B-4270-9F10-AEFA37CE5C93.html)   
 
 ## FAQ 
 
 ### What is the impact of an HCX upgrade? 
 
 Apply service updates during a maintenance window where no new HCX operations and migration are queued up. The upgrade window accounts for a brief disruption to the Network Extension service, while the appliances are redeployed with the updated code.  
-For individual HCX component upgrade impact, see [Planning for HCX Updates](https://docs.vmware.com/en/VMware-HCX/4.5/hcx-user-guide/GUID-61F5CED2-C347-4A31-8ACB-A4553BFC62E3.html). 
+For individual HCX component upgrade impact, see [Planning for HCX Updates](https://docs.vmware.com/en/VMware-HCX/4.9/hcx-user-guide/GUID-61F5CED2-C347-4A31-8ACB-A4553BFC62E3.html). 
 
 ### Do I need to upgrade the service mesh appliances? 
 
 The HCX Service Mesh can be upgraded once all paired HCX Manager systems are updated, and all services are returned to a fully converged state. Check HCX release notes for upgrade requirements. Starting with HCX 4.4.0, HCX appliances installed the VMware Photon Operating System. When upgrading to HCX 4.4.x or later from an HCX version prior to 4.4.0 version, you must upgrade all Service Mesh appliances. 
 
 ### How do I roll back HCX upgrade using a snapshot? 
 
-See [Rolling Back an Upgrade Using Snapshots](https://docs.vmware.com/en/VMware-HCX/4.5/hcx-user-guide/GUID-B34728B9-B187-48E5-AE7B-74E92D09B98B.html).  On the cloud side, open a [support ticket](https://ms.portal.azure.com/#view/Microsoft_Azure_Support/HelpAndSupportBlade/~/overview) to roll back the upgrade. 
+See [Rolling Back an Upgrade Using Snapshots](https://docs.vmware.com/en/VMware-HCX/4.9/hcx-user-guide/GUID-B34728B9-B187-48E5-AE7B-74E92D09B98B.html).  On the cloud side, open a [support ticket](https://ms.portal.azure.com/#view/Microsoft_Azure_Support/HelpAndSupportBlade/~/overview) to roll back the upgrade. 
 
 ## Next steps 
-[Software Versioning, Skew and Legacy Support Policies](https://docs.vmware.com/en/VMware-HCX/4.5/hcx-skew-policy/GUID-787FB2A1-52AF-483C-B595-CF382E728674.html)  
+[Software Versioning, Skew and Legacy Support Policies](https://docs.vmware.com/en/VMware-HCX/4.8/hcx-skew-policy/GUID-787FB2A1-52AF-483C-B595-CF382E728674.html)  
 
-[Updating VMware HCX](https://docs.vmware.com/en/VMware-HCX/4.5/hcx-user-guide/GUID-508A94B2-19F6-47C7-9C0D-2C89A00316B9.html) 
+[Updating VMware HCX](https://docs.vmware.com/en/VMware-HCX/4.6/hcx-user-guide/GUID-508A94B2-19F6-47C7-9C0D-2C89A00316B9.html) 
diff --git a/articles/databox-online/azure-stack-edge-gpu-create-virtual-machine-image.md b/articles/databox-online/azure-stack-edge-gpu-create-virtual-machine-image.md
@@ -84,9 +84,9 @@ If using Red Hat Enterprise Linux (RHEL) images, only the Red Hat Enterprise Lin
 To create a VM image using the RHEL BYOS image, follow these steps:
 
 1. Sign in to [Red Hat Subscription Management](https://access.redhat.com/management). Navigate to the [Cloud Access Dashboard](https://access.redhat.com/management/cloud) from the top menu bar.
-1. Enable your Azure subscription. See [detailed instructions](https://access.redhat.com/documentation/en-us/red_hat_subscription_management/1/html/red_hat_cloud_access_reference_guide/getting-started-with-ca_cloud-access). Enabling the subscription will allow you to access the Red Hat Gold Images.
+1. Enable your Azure subscription. See [detailed instructions](https://access.redhat.com/documentation/en-us/subscription_central/1-latest/html/red_hat_cloud_access_reference_guide/getting-started-with-ca_cloud-access). Enabling the subscription will allow you to access the Red Hat Gold Images.
 
-1. Accept the Azure terms of use (only once per Azure Subscription, per image) and provision a VM. See [instructions](https://access.redhat.com/documentation/en-us/red_hat_subscription_management/1/html/red_hat_cloud_access_reference_guide/understanding-gold-images_cloud-access). 
+1. Accept the Azure terms of use (only once per Azure Subscription, per image) and provision a VM. See [instructions](https://access.redhat.com/documentation/en-us/subscription_central/1-latest/html/red_hat_cloud_access_reference_guide/understanding-gold-images_cloud-access). 
 
 You can now use the VM that you provisioned to [Create a VM custom image](#create-a-custom-vm-image) in Linux.
 
diff --git a/articles/databox/data-box-disk-overview.md b/articles/databox/data-box-disk-overview.md
@@ -44,8 +44,6 @@ You can use your Data Box data with many non-Azure service providers. For instan
 
 - **[Veeam](https://helpcenter.veeam.com/docs/backup/hyperv/osr_adding_data_box.html?ver=100)** - allows you to backup and replicated large amounts of data from your Hyper-V machine to your Data Box.
 
-For a list of other non-Azure service providers that integrate with Data Box, see [Azure Data Box Partners](https://cloudchampions.blob.core.windows.net/db-partners/PartnersTable.pdf).
-
 ## The workflow
 
 A typical flow includes the following steps:
diff --git a/articles/iot-edge/how-to-access-dtpm.md b/articles/iot-edge/how-to-access-dtpm.md
@@ -87,7 +87,7 @@ Once the executable file and dependency files are created, you need to copy the
     cd "C:\Users\User"
     ```
 
-1. Create a *tar* file with all the files created in previous steps. For more information about PowerShell *tar* support, see [Tar and Curl Come to Windows](/virtualization/community/team-blog/2017/20171219-tar-and-curl-come-to-windows).
+1. Create a *tar* file with all the files created in previous steps. For more information about PowerShell *tar* support, see [Tar and Curl Come to Windows](https://devblogs.microsoft.com/commandline/tar-and-curl-come-to-windows/).
     For example, if you have all your files under the folder _TPM_, you can use the following command to create the _TPM.tar_ file.
     ```powershell
      tar -cvzf TPM.tar ".\TPM"
diff --git a/articles/iot-edge/iot-edge-for-linux-on-windows-networking.md b/articles/iot-edge/iot-edge-for-linux-on-windows-networking.md
@@ -22,7 +22,7 @@ ms.author: fcabrera
 ## Networking
 To establish a communication channel between the Windows host OS and the EFLOW virtual machine, we use Hyper-V networking stack. For more information about Hyper-V networking, see [Hyper-V networking basics](/windows-server/virtualization/hyper-v/plan/plan-hyper-v-networking-in-windows-server#hyper-v-networking-basics). Basic networking in EFLOW is simple; it uses two parts, a virtual switch and a virtual network. 
 
-The easiest way to establish basic networking on Windows client SKUs is by using the [**default switch**](/virtualization/community/team-blog/2017/20170726-hyper-v-virtual-machine-gallery-and-networking-improvements#details-about-the-default-switch) already created by the Hyper-V feature. During EFLOW deployment, if no specific virtual switch is specified using the `-vSwitchName` and `-vSwitchType` flags, the virtual machine will be created using the **default switch**.
+The easiest way to establish basic networking on Windows client SKUs is by using the [**default switch**](https://techcommunity.microsoft.com/t5/virtualization/hyper-v-virtual-machine-gallery-and-networking-improvements/ba-p/382375) already created by the Hyper-V feature. During EFLOW deployment, if no specific virtual switch is specified using the `-vSwitchName` and `-vSwitchType` flags, the virtual machine will be created using the **default switch**.
 
 On Windows Server SKUs devices, networking is a bit more complicated as there's no **default switch** available. However, there's a comprehensive guide on [Azure IoT Edge for Linux on Windows virtual switch creation](./how-to-create-virtual-switch.md). 
 
diff --git a/articles/iot-edge/troubleshoot-iot-edge-for-linux-on-windows.md b/articles/iot-edge/troubleshoot-iot-edge-for-linux-on-windows.md
@@ -184,7 +184,7 @@ Second, if the GPU is correctly assigned, but still not being able to use it ins
 The first step before checking *WSSDAgent* logs is to check if the VM was created and is running. 
 
 1. Start an elevated _PowerShell_ session using **Run as Administrator**.
-1. On Windows Client SKUs, check the [HCS](/virtualization/community/team-blog/2017/20170127-introducing-the-host-compute-service-hcs) virtual machines.
+1. On Windows Client SKUs, check the [HCS](https://techcommunity.microsoft.com/t5/containers/introducing-the-host-compute-service-hcs/ba-p/382332) virtual machines.
     ```powershell
     hcsdiag list
     ```
diff --git a/articles/iot-operations/connect-to-cloud/howto-configure-destination-fabric.md b/articles/iot-operations/connect-to-cloud/howto-configure-destination-fabric.md
@@ -30,7 +30,7 @@ To configure and use a Microsoft Fabric destination pipeline stage, you need:
 
 Before you can write to Microsoft Fabric from a data pipeline, you need to grant access to the lakehouse from the pipeline. You can use either a service principal or a managed identity to authenticate the pipeline. The advantage of using a managed identity is that you don't need to manage the lifecycle of the service principal. The managed identity is automatically managed by Azure and is tied to the lifecycle of the resource it's assigned to.
 
-Before you configure either service principal or managed identity access to a lakehouse, enable [service principal authentication](/fabric/onelake/onelake-security#authentication).
+Before you configure either service principal or managed identity access to a lakehouse, enable [service principal authentication](/fabric/onelake/security/get-started-security#authentication).
 
 # [Service principal](#tab/serviceprincipal)
 
diff --git a/articles/machine-learning/how-to-identity-based-service-authentication.md b/articles/machine-learning/how-to-identity-based-service-authentication.md
@@ -362,7 +362,7 @@ The following steps outline how to set up data access with user identity for tra
 
 1. Grant data access and create data store as described above for CLI.
 
-1. Submit a training job with identity parameter set to [azure.ai.ml.UserIdentityConfiguration](/python/api/azure-ai-ml/azure.ai.ml.useridentityconfiguration). This parameter setting enables the job to access data on behalf of user submitting the job.
+1. Submit a training job with identity parameter set to [azure.ai.ml.UserIdentityConfiguration](/python/api/azure-ai-ml/azure.ai.ml.entities.useridentityconfiguration). This parameter setting enables the job to access data on behalf of user submitting the job.
 
     ```python
     from azure.ai.ml import command
diff --git a/articles/sentinel/data-connectors/juniper-srx.md b/articles/sentinel/data-connectors/juniper-srx.md
@@ -10,7 +10,7 @@ ms.author: cwatson
 
 # Juniper SRX connector for Microsoft Sentinel
 
-The [Juniper SRX](https://www.juniper.net/us/en/products-services/security/srx-series/) connector allows you to easily connect your Juniper SRX logs with Microsoft Sentinel. This gives you more insight into your organization's network and improves your security operation capabilities.
+The [Juniper SRX](https://www.juniper.net/us/en/products/security/srx-series.html) connector allows you to easily connect your Juniper SRX logs with Microsoft Sentinel. This gives you more insight into your organization's network and improves your security operation capabilities.
 
 ## Connector attributes
 
diff --git a/articles/site-recovery/hyper-v-azure-troubleshoot.md b/articles/site-recovery/hyper-v-azure-troubleshoot.md
@@ -176,7 +176,7 @@ All Hyper-V replication events are logged in the Hyper-V-VMMS\Admin log, located
 
 ### Log collection for advanced troubleshooting
 
-These tools can help with advanced troubleshooting:
+This tool can help with advanced troubleshooting:
 
 -	For VMM, perform Site Recovery log collection using the [Support Diagnostics Platform (SDP) tool](https://social.technet.microsoft.com/wiki/contents/articles/28198.asr-data-collection-and-analysis-using-the-vmm-support-diagnostics-platform-sdp-tool.aspx).
 -	For Hyper-V without VMM, [download this tool](https://answers.microsoft.com/en-us/windows/forum/all/unable-to-open-diagcab-files/e7f8e4e5-b442-4e53-af7a-90e74985a73f), and run it on the Hyper-V host to collect the logs.
diff --git a/articles/virtual-machines/extensions/hpccompute-amd-gpu-windows.md b/articles/virtual-machines/extensions/hpccompute-amd-gpu-windows.md
diff --git a/articles/virtual-machines/linux/endorsed-distros.md b/articles/virtual-machines/linux/endorsed-distros.md
diff --git a/articles/virtual-machines/workloads/redhat/byos.md b/articles/virtual-machines/workloads/redhat/byos.md
diff --git a/articles/virtual-machines/workloads/redhat/overview.md b/articles/virtual-machines/workloads/redhat/overview.md
diff --git a/articles/virtual-network/virtual-network-tap-overview.md b/articles/virtual-network/virtual-network-tap-overview.md
diff --git a/articles/web-application-firewall/cdn/cdn-overview.md b/articles/web-application-firewall/cdn/cdn-overview.md
