Merge pull request #305164 from v-albemi/validation-19

Bulk - fix validation issues

Author: prmerger-automator[bot]

articles/azure-vmware/enable-public-ip-nsx-edge.md

@@ -172,8 +172,8 @@ You can provide security protection for your network traffic in and out of the p
 
 If **Match Internal Address** was specified, the destination is the internal or private IP address of the VM.
 
-For more information on the NSX gateway firewall, see the [NSX Gateway Firewall Administration Guide](https://techdocs.broadcom.com/us/en/vmware-cis/nsx/vmware-nsx/4-2/administration-guide/security/gateway-firewall.html).
-The distributed firewall can be used to filter traffic to VMs. For more information, see [NSX Distributed Firewall Administration Guide](https://techdocs.broadcom.com/us/en/vmware-cis/nsx/vmware-nsx/4-2/administration-guide/security/distributed-firewall.html).
+For more information on the NSX gateway firewall, see the [NSX Gateway Firewall Administration Guide](https://techdocs.broadcom.com/us/en/vmware-cis/nsx/nsxt-dc/3-2/administration-guide/security/gateway-firewall.html).
+The distributed firewall can be used to filter traffic to VMs. For more information, see [NSX Distributed Firewall Administration Guide](https://techdocs.broadcom.com/us/en/vmware-cis/nsx/nsxt-dc/3-2/administration-guide/security/distributed-firewall.html).
 
 ## Related content
 

articles/frontdoor/post-migration-dev-ops-experience.md

@@ -16,13 +16,13 @@ After migrating from Azure Front Door (Classic) or CDN Classic to Azure Front Do
 ### Prerequisites
 
 - Ensure the Terraform CLI is installed. See [Install Terraform](https://developer.hashicorp.com/terraform/tutorials/azure-get-started/install-cli).
-- Install the Azure Resource Manager Export extension for Terraform to export existing Azure resources to Terraform templates. See [Overview of Azure Export for Terraform](https://learn.microsoft.com/azure/developer/terraform/azure-export-for-terraform/export-terraform-overview).
+- Install the Azure Resource Manager Export extension for Terraform to export existing Azure resources to Terraform templates. See [Overview of Azure Export for Terraform](/azure/developer/terraform/azure-export-for-terraform/export-terraform-overview).
 
 ### Steps
 
 After migration, all classic AFD resources are migrated to AFD Standard and Premium. Then:
 
-- **Export the new AFD Standard/Premium configuration**: Use Azure’s export tool to generate Terraform configurations for your new Front Door Standard/Premium resources. Follow [Quickstart: Export your first resources using Azure Export for Terraform](https://learn.microsoft.com/azure/developer/terraform/azure-export-for-terraform/export-first-resources?tabs=azure-cli) to export the Front Door Standard/Premium resources into Terraform files.
+- **Export the new AFD Standard/Premium configuration**: Use Azure’s export tool to generate Terraform configurations for your new Front Door Standard/Premium resources. Follow [Quickstart: Export your first resources using Azure Export for Terraform](/azure/developer/terraform/azure-export-for-terraform/export-first-resources?tabs=azure-cli) to export the Front Door Standard/Premium resources into Terraform files.
 - **Update Terraform templates in your pipeline**: Replace references to Front Door Classic resources with the exported Standard/Premium configuration.
   - For AFD Classic, the Terraform resource is [`azurerm_frontdoor`](https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/frontdoor).
   - For CDN Classic, use the [`azurerm_cdn_*`](https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/cdn_endpoint) resources.
@@ -53,38 +53,38 @@ After migration, all classic AFD resources are migrated to AFD Standard and Prem
 After migration, all classic AFD resources are migrated to AFD Standard and Premium.
 
 - **Generate a Bicep template for Front Door Standard/Premium** by decompiling an exported ARM template. See [Decompile ARM template JSON to Bicep](../azure-resource-manager/bicep/decompile.md?tabs=azure-cli).
-- **Update Bicep files in your pipeline**: Replace Front Door Classic definitions with Standard/Premium. This may include updating resource types such as [`Microsoft.Cdn/profiles`](https://learn.microsoft.com/azure/templates/microsoft.cdn/profiles?pivots=deployment-language-bicep) and child resources (endpoints, routes, etc.).
+- **Update Bicep files in your pipeline**: Replace Front Door Classic definitions with Standard/Premium. This may include updating resource types such as [`Microsoft.Cdn/profiles`](/azure/templates/microsoft.cdn/profiles?pivots=deployment-language-bicep) and child resources (endpoints, routes, etc.).
 - **Test** a deployment (for example, `az deployment group create`) to verify provisioning of AFD Standard/Premium.
 
 ## PowerShell
 
 ### Prerequisites
 
-Make sure you have the latest Azure PowerShell Az modules installed (Az.Cdn module version that supports AFD Standard/Premium). See [Install Azure PowerShell](https://learn.microsoft.com/powershell/azure/install-azps-windows).
+Make sure you have the latest Azure PowerShell Az modules installed (Az.Cdn module version that supports AFD Standard/Premium). See [Install Azure PowerShell](/powershell/azure/install-azps-windows).
 
 ### Steps
 
 - **Update PowerShell deployment scripts**: Replace any Front Door (Classic) cmdlets with AFD Standard/Premium cmdlets. For examples, see the [Azure Front Door PowerShell quickstart](create-front-door-powershell.md).
 - **Incorporate new configuration and remove old references**: Ensure scripts configure required components (origins, origin groups, routes, rules, etc.). Remove or comment commands that manage Classic Front Door.
 - Command group mapping:
-  - AzFrontDoorCdn commands under the [Az.Cdn module](https://learn.microsoft.com/powershell/module/az.cdn/) are for AFD Standard/Premium.
-  - AzCdn commands under the [Az.Cdn module](https://learn.microsoft.com/powershell/module/az.cdn/) are for CDN Classic.
-  - The [Az.FrontDoor module](https://learn.microsoft.com/powershell/module/az.frontdoor/) is for AFD Classic.
+  - AzFrontDoorCdn commands under the [Az.Cdn module](/powershell/module/az.cdn/) are for AFD Standard/Premium.
+  - AzCdn commands under the [Az.Cdn module](/powershell/module/az.cdn/) are for CDN Classic.
+  - The [Az.FrontDoor module](/powershell/module/az.frontdoor/) is for AFD Classic.
 - **Test** your script (locally or in a test pipeline) to verify creation or updates to AFD Standard/Premium, then commit changes to your pipeline.
 
 ## CLI
 
 ### Prerequisites
 
-- Ensure Azure CLI is installed and updated to a version that supports the `afd` command group (for example, 2.63.0 or later). See [Install Azure CLI](https://learn.microsoft.com/cli/azure/install-azure-cli).
+- Ensure Azure CLI is installed and updated to a version that supports the `afd` command group (for example, 2.63.0 or later). See [Install Azure CLI](/cli/azure/install-azure-cli).
 - Log in (`az login`) and set the correct subscription context.
 
 ### Steps
 
-- **Update CLI commands in scripts**: Use the Azure Front Door Standard/Premium command group: [`az afd`](https://learn.microsoft.com/cli/azure/afd).
+- **Update CLI commands in scripts**: Use the Azure Front Door Standard/Premium command group: [`az afd`](/cli/azure/afd).
 - **Replace or remove Front Door Classic CLI usage**:
-  - CDN Classic commands: [`az cdn`](https://learn.microsoft.com/cli/azure/cdn)
-  - AFD Classic commands: [`az network front-door`](https://learn.microsoft.com/cli/azure/network/front-door)
+  - CDN Classic commands: [`az cdn`](/cli/azure/cdn)
+  - AFD Classic commands: [`az network front-door`](/cli/azure/network/front-door)
 - **Validate** the updated CLI script manually or in a staging pipeline to ensure successful configuration of Front Door Standard/Premium.
 
 ## Next step

articles/hdinsight/overview-azure-storage.md

@@ -49,7 +49,7 @@ Consider the following principles when using an Azure Storage account with HDIns
 The storage accounts that are defined in the creation process and their keys are stored in %HADOOP_HOME%/conf/core-site.xml on the cluster nodes. By default, HDInsight uses the storage accounts defined in the core-site.xml file. You can modify this setting by using [Apache Ambari](./hdinsight-hadoop-manage-ambari.md). For more information about the storage account settings that can be modified or placed in the core-site.xml file, see these articles:
 
 - [Hadoop Azure Support: Azure Blob Storage](https://hadoop.apache.org/docs/stable/hadoop-azure/index.html)
-- [Hadoop Azure Support: ABFS — Azure Data Lake Storage Gen2](https://hadoop.apache.org/docs/stable/hadoop-azure/abfs.html)
+- [Hadoop Azure Support: ABFS — Azure Data Lake Storage Gen2](https://hadoop.apache.org/docs/stable/hadoop-azure/index.html)
 
 Multiple WebHCat jobs, including Apache Hive. And MapReduce, Apache Hadoop streaming, and Apache Pig, carry a description of storage accounts and metadata. (This aspect is currently true for Pig with storage accounts but not for metadata.) For more information, see [Using an HDInsight cluster with alternate storage accounts and metastores](https://social.technet.microsoft.com/wiki/contents/articles/23256.using-an-hdinsight-cluster-with-alternate-storage-accounts-and-metastores.aspx).