Merge pull request #270023 from mattbriggs/mdb_20240322_bender

214824 - rework the YAML

Author: Jill Grant

articles/dns/private-dns-autoregistration.md

@@ -23,7 +23,7 @@ To enable auto registration, select the checkbox for "Enable auto registration"
 
 * Auto registration works only for virtual machines. For all other resources like internal load balancers, you can create DNS records manually in the private DNS zone linked to the virtual network.
 * DNS records are created automatically only for the primary virtual machine NIC. If your virtual machines have more than one NIC, you can manually create the DNS records for other network interfaces.
-* DNS records are created automatically only if the primary virtual machine NIC is using DHCP. If you're using static IPs, such as a configuration with [multiple IP addresses in Azure](../virtual-network/ip-services/virtual-network-multiple-ip-addresses-portal.yml#os-config), auto registration doesn't create records for that virtual machine.
+* DNS records are created automatically only if the primary virtual machine NIC is using DHCP. If you're using static IPs, such as a configuration with [multiple IP addresses in Azure](../virtual-network/ip-services/virtual-network-multiple-ip-addresses-portal.md), auto registration doesn't create records for that virtual machine.
 * A specific virtual network can be linked to only one private DNS zone when automatic VM DNS registration is enabled. You can, however, link multiple virtual networks to a single DNS zone.
 
 ## Next steps

articles/sap/workloads/planning-guide.md

@@ -276,7 +276,7 @@ For more information, see [Create a VM that has a static private IP address](/az
 
 #### Secondary IP addresses for SAP host name virtualization
 
-Each Azure VM's NIC can have multiple IP addresses assigned to it. A secondary IP can be used for an SAP virtual host name, which is mapped to a DNS A record or DNS PTR record. A secondary IP address must be assigned to the Azure NIC's [IP configuration](../../virtual-network/ip-services/virtual-network-multiple-ip-addresses-portal.yml). A secondary IP also must be configured within the operating system statically because secondary IPs often aren't assigned through DHCP. Each secondary IP must be from the same subnet that the NIC is bound to. A secondary IP can be added and removed from an Azure NIC without stopping or deallocating the VM. To add or remove the primary IP of a NIC, the VM must be deallocated.
+Each Azure VM's NIC can have multiple IP addresses assigned to it. A secondary IP can be used for an SAP virtual host name, which is mapped to a DNS A record or DNS PTR record. A secondary IP address must be assigned to the Azure NIC's [IP configuration](../../virtual-network/ip-services/virtual-network-multiple-ip-addresses-portal.md). A secondary IP also must be configured within the operating system statically because secondary IPs often aren't assigned through DHCP. Each secondary IP must be from the same subnet that the NIC is bound to. A secondary IP can be added and removed from an Azure NIC without stopping or deallocating the VM. To add or remove the primary IP of a NIC, the VM must be deallocated.
 
 > [!NOTE]
 > On secondary IP configurations, the Azure load balancer's floating IP address is [not supported](../../load-balancer/load-balancer-multivip-overview.md#limitations). The Azure load balancer is used by SAP high-availability architectures with Pacemaker clusters. In this scenario, the load balancer enables the SAP virtual host names. For general guidance about using virtual host names, see SAP Note [962955](https://launchpad.support.sap.com/#/notes/962955).

articles/site-recovery/azure-to-azure-customize-networking.md

@@ -24,7 +24,7 @@ You can provide the following key resource configurations for the failover VM wh
 
 - [Internal load balancer](../load-balancer/load-balancer-overview.md)
 - [Public IP](../virtual-network/public-ip-addresses.md)
-- [Secondary IP](../virtual-network/ip-services/virtual-network-multiple-ip-addresses-portal.yml)
+- [Secondary IP](../virtual-network/ip-services/virtual-network-multiple-ip-addresses-portal.md)
 - [Network security group](../virtual-network/manage-network-security-group.md) both for the subnet and for the NIC
 
 ## Prerequisites

articles/virtual-machines/TOC.yml

@@ -1644,7 +1644,7 @@
   - name: Create VM - multiple IPs
     items:
     - name: Azure portal
-      href: ../virtual-network/ip-services/virtual-network-multiple-ip-addresses-portal.yml?toc=/azure/virtual-machines/toc.json
+      href: ../virtual-network/ip-services/virtual-network-multiple-ip-addresses-portal.md?toc=/azure/virtual-machines/toc.json
     - name: Azure PowerShell
       href: ../virtual-network/ip-services/virtual-network-multiple-ip-addresses-powershell.md?toc=/azure/virtual-machines/toc.json
     - name: Azure CLI

articles/virtual-machines/windows/multiple-nics.md

@@ -16,7 +16,7 @@ ms.custom: devx-track-azurepowershell
 Virtual machines (VMs) in Azure can have multiple virtual network interface cards (NICs) attached to them. A common scenario is to have different subnets for front-end and back-end connectivity. You can associate multiple NICs on a VM to multiple subnets, but those subnets must all reside in the same virtual network (vNet). This article details how to create a VM that has multiple NICs attached to it. You also learn how to add or remove NICs from an existing VM. Different [VM sizes](../sizes.md) support a varying number of NICs, so size your VM accordingly.
 
 > [!NOTE]
-> If multiple subnets are not required for a scenario, it may be more straightforward to utilize multiple IP configurations on a single NIC.  Instructions for this setup can be found [here](../../virtual-network/ip-services/virtual-network-multiple-ip-addresses-portal.yml).
+> If multiple subnets are not required for a scenario, it may be more straightforward to utilize multiple IP configurations on a single NIC.  Instructions for this setup can be found [here](../../virtual-network/ip-services/virtual-network-multiple-ip-addresses-portal.md).
 
 ## Prerequisites
 

articles/virtual-network/.openpublishing.redirection.virtual-network.json

@@ -766,7 +766,7 @@
             "redirect_document_id": false
         },
         {
-            "source_path_from_root": "/articles/virtual-network/virtual-network-multiple-ip-addresses-portal.yml",
+            "source_path_from_root": "/articles/virtual-network/virtual-network-multiple-ip-addresses-portal.md",
             "redirect_url": "/azure/virtual-network/ip-services/virtual-network-multiple-ip-addresses-portal",
             "redirect_document_id": false
         },

articles/virtual-network/deploy-container-networking.md

@@ -87,7 +87,7 @@ Complete the following steps to install the plug-in on every Azure virtual machi
 
    - **PowerShell**: [Assign multiple IP addresses using PowerShell](./ip-services/virtual-network-multiple-ip-addresses-powershell.md)
 
-   - **Portal**: [Assign multiple IP addresses using the Azure portal](./ip-services/virtual-network-multiple-ip-addresses-portal.yml)
+   - **Portal**: [Assign multiple IP addresses using the Azure portal](./ip-services/virtual-network-multiple-ip-addresses-portal.md)
 
    - **Azure Resource Manager template**: [Assign multiple IP addresses using templates](./template-samples.md)
 

articles/virtual-network/ip-services/configure-public-ip-vm-old.md

@@ -115,7 +115,7 @@ In this section, you'll change the public IP address associated with the default
 
 In this section, you'll add a public IP configuration to the virtual machine. 
 
-For more information on adding multiple IP addresses, see [Assign multiple IP addresses to virtual machines using the Azure portal](./virtual-network-multiple-ip-addresses-portal.yml). 
+For more information on adding multiple IP addresses, see [Assign multiple IP addresses to virtual machines using the Azure portal](./virtual-network-multiple-ip-addresses-portal.md). 
 
 For more information for using both types of routing preference, see [Configure both routing preference options for a virtual machine](./routing-preference-mixed-network-adapter-portal.md).
 

articles/virtual-network/ip-services/configure-public-ip-vm.yml

@@ -121,7 +121,7 @@ procedureSection:
     summary: |
       In this section, you'll add a public IP configuration to the virtual machine. 
 
-      For more information on adding multiple IP addresses, see [Assign multiple IP addresses to virtual machines using the Azure portal](./virtual-network-multiple-ip-addresses-portal.yml). 
+      For more information on adding multiple IP addresses, see [Assign multiple IP addresses to virtual machines using the Azure portal](./virtual-network-multiple-ip-addresses-portal.md). 
 
       For more information for using both types of routing preference, see [Configure both routing preference options for a virtual machine](./routing-preference-mixed-network-adapter-portal.md).
     steps: 

articles/virtual-network/ip-services/index.yml

@@ -86,7 +86,7 @@ landingContent:
           - text: Configure a private IP address for a virtual machine
             url: virtual-networks-static-private-ip-arm-pportal.md
           - text: Assign multiple IP addresses to virtual machines
-            url: virtual-network-multiple-ip-addresses-portal.yml
+            url: virtual-network-multiple-ip-addresses-portal.md
 
   - title: Learn about IP services architecture
     linkLists: