Merge pull request #227655 from cynthn/Release_Archive_main_2023-02-16-20-14-32

LB [DocsArchive-1.0.23045.1](2023-02-16-20-14-32)Auto archive content

Author: Stacyrch140

articles/guides/operations/TOC.yml

@@ -40,10 +40,10 @@
         href: ../../virtual-machines/linux/tutorial-manage-vm.md?toc=%2fazure%2fguides%2foperations%2ftoc.json
       - name: Jenkins CI/CD Pipeline
         href: /azure/developer/jenkins/pipeline-with-github-and-docker?toc=%2fazure%2fguides%2foperations%2ftoc.json
-      - name: Load balance VMs
-        href: ../../virtual-machines/linux/tutorial-load-balancer.md?toc=%2fazure%2fguides%2foperations%2ftoc.json
       - name: Authoring Azure Resource Manager templates
         href: ../../azure-resource-manager/templates/syntax.md?toc=%2fazure%2fguides%2foperations%2ftoc.json
+      - name: Create a load balancer
+        href: ../../load-balancer/quickstart-load-balancer-standard-public-powershell.md
       - name: Backup VMs at Scale
         href: ../../backup/tutorial-backup-vm-at-scale.md
   - name: How To Guides
@@ -60,4 +60,4 @@
       href: https://azure.microsoft.com/pricing/calculator/
     - name: Microsoft Azure portal overview
       href: ../../azure-portal/azure-portal-overview.md
-  - name: References
+  - name: References

articles/marketplace/azure-vm-certification-faq.yml

@@ -483,7 +483,7 @@ sections:
           |NVA Deployment|Deploy a VM using the NVA with 1 NIC. Verify that the deployment is completed in 20 minutes.|If the deployment is not completed within 20 minutes, then verify the NVA image.|
           |NVA Reboot|Deploy a VM using the NVA with 1 NIC. Then, go to the VM in Azure portal, and under section **Support + troubleshooting** in the left pane, click on **Redeploy + Reapply** and redeploy the VM. After redeployment is completed, verify that the status of the VM is *Running* and the NIC port 22 is reachable using Netcat command.|If VM doesn't come up after reboot, then there may be an issue with the NVA image.<br><br>If the Netcat test fails, then it could be because the NIC failed to come up after the reboot even though the VM was running. Please wait for few minutes and try again. If after 20 mins it still fails, then there may be an issue with the NVA image|
           |NVA Redeployment|Deploy a VM using the NVA with 1 NIC. Then, redeploy the VM. Verify that the status of the VM is *Running* and the NIC port 22 is reachable using Netcat command.|If the redeploy does not complete within 15 minutes, then there may be an issue with the NVA image.<br><br>If the Netcat test fails, then it could be because the NIC failed to come up after the reboot even though the VM was running. Please wait for few minutes and try again. If after 20 mins it still fails, then there may be an issue with the NVA image|
-          |High Availability|Deploy a VM using the NVA with 1 NIC. Either No public IP should be attached to NIC or if Public IP is attached then SKU should be standard and IP allocation method should be static. In the same virtual network, setup an Azure Internal [load balancer](../virtual-machines/linux/tutorial-load-balancer.md) using configuration below.<br> - Load balancer using *Standard SKU*<br> - Frontend IP using private IP allocation method as dynamic<br> - Health probes using TCP, port 22 with a retry interval of 15 seconds<br> - A load balancing rule with protocol as *all* and enable floating IP set to False.<br> - Backend pool pointing to NVA VM.<br><br>Once the setup is ready, verify that the NVA VM is reachable across the load balancer, using Netcat command.|If the NVA is unreachable across the load balancer, then verify the setup of the VM, load balancer and HA ports feature. If everything is accurate, then there may be an issue with the NVA image.|
+          |High Availability|Deploy a VM using the NVA with 1 NIC. Either No public IP should be attached to NIC or if Public IP is attached then SKU should be standard and IP allocation method should be static. In the same virtual network, set up an Azure Internal [load balancer](../load-balancer/quickstart-load-balancer-standard-public-portal.md) using configuration below.<br> - Load balancer using *Standard SKU*<br> - Frontend IP using private IP allocation method as dynamic<br> - Health probes using TCP, port 22 with a retry interval of 15 seconds<br> - A load balancing rule with protocol as *all* and enable floating IP set to False.<br> - Backend pool pointing to NVA VM.<br><br>Once the setup is ready, verify that the NVA VM is reachable across the load balancer, using Netcat command.|If the NVA is unreachable across the load balancer, then verify the setup of the VM, load balancer and HA ports feature. If everything is accurate, then there may be an issue with the NVA image.|
           |VNET Peering|Deploy a virtual machine VM1 using the NVA image, with 1 NIC in a virtual network VNET1. In another virtual network VNET2, deploy a virtual machine VM2 using any Linux image, say ubuntu, with 1 NIC, and VM settings as Dynamic IP allocation method and basic SKU. Create [VNET peering](../virtual-network/virtual-network-manage-peering.md) between VNET1 and VNET2 and **Traffic to remote virtual network** is configured as *Allow (default)*<br><br>Once the setup is ready, verify that from VM2 we can reach private IP of the NIC on the NVA VM1, using Netcat command.|If the NVA VM1 is unreachable from VM2, then verify that the VNET peering is configured correctly and try again. If it still doesn't work, then there may be an issue with the NVA image.|
           |Accelerated Networking (AN)|Deploy a VM with the NVA and 1 [AN enabled NIC](../virtual-network/create-vm-accelerated-networking-cli.md). You can enable AN on a NIC while creating the VM, or on the NIC properties after creating the VM. Verify that the VM will be up and running.|If the deployment fails, then please verify that the NVA image supports Accelerated Networking.|
           |Multi-NIC Basic|Deploy a VM using the NVA with 3 NICs with Dynamic IP allocation method and basic SKU. Get private IP and MAC address for all the NICs (refer to [view Network Interface](../virtual-network/virtual-network-network-interface.md) for instructions). Then, redeploy the VM, and verify that the private IP and MAC address for all the NICs remain the same as before redeploying.|If the private IP and MAC address for all the NICs change after redeploying, then there may be an issue with the NVA image.|

articles/networking/TOC.yml

@@ -25,7 +25,7 @@
   - name: Plan and design
     items:
     - name: Support for working remotely
-      href: working-remotely-support.md  
+      href: working-remotely-support.md
     - name: Virtual networks
       href: ../virtual-network/virtual-network-vnet-plan-design-arm.md?toc=%2fazure%2fnetworking%2ftoc.json
     - name: Cross-premises connectivity - VPN
@@ -131,7 +131,7 @@
   - name: Tutorials
     items:
     - name: Load balance VMs
-      href: ../virtual-machines/linux/tutorial-load-balancer.md?toc=%2fazure%2fnetworking%2ftoc.json
+      href: ../load-balancer/quickstart-load-balancer-standard-public-portal.md
     - name: Connect a computer to a virtual network
       href: ../vpn-gateway/vpn-gateway-howto-point-to-site-resource-manager-portal.md?toc=%2fazure%2fnetworking%2ftoc.json
 - name: Reference

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

@@ -1,5 +1,15 @@
 {
     "redirections": [
+        {
+            "source_path_from_root": "/articles/virtual-machines/linux/tutorial-load-balancer.md",
+            "redirect_url": "/previous-versions/azure/virtual-machines/linux/tutorial-load-balancer",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/virtual-machines/windows/tutorial-load-balancer.md",
+            "redirect_url": "/previous-versions/azure/virtual-machines/windows/tutorial-load-balancer",
+            "redirect_document_id": false
+        },
         {
             "source_path_from_root": "/articles/virtual-machines/linux/freebsd-pf-nat.md",
             "redirect_url": "/previous-versions/azure/virtual-machines/linux/freebsd-pf-nat",

articles/virtual-machines/TOC.yml

@@ -45,40 +45,40 @@
   items:
   - name: Linux
     items:
-    - name: 1 - Create / manage VMs
+    - name: Create / manage VMs
       href: ./linux/tutorial-manage-vm.md
-    - name: 2 - Create / manage disks
+    - name: Create / manage disks
       href: ./linux/tutorial-manage-disks.md
-    - name: 3 - Automate configuration
+    - name: Automate configuration
       href: ./linux/tutorial-automate-vm-deployment.md
-    - name: 4 - Create VM images
+    - name: Create VM images
       href: ./linux/tutorial-custom-images.md
-    - name: 5 - Highly available VMs
+    - name: Manage networking
+      href: ./linux/tutorial-virtual-network.md
+    - name: Highly available VMs
       href: ./linux/tutorial-availability-sets.md
-    - name: 6 - Create a scale set
+    - name: Load Balance VMs
+      href: ../load-balancer/quickstart-load-balancer-standard-public-cli.md
+    - name: Create a scale set
       href: ./linux/tutorial-create-vmss.md
-    - name: 7 - Load balance VMs
-      href: ./linux/tutorial-load-balancer.md
-    - name: 8 - Manage networking
-      href: ./linux/tutorial-virtual-network.md
   - name: Windows
     items:
-    - name: 1 - Create / manage a VM
+    - name: Create / manage a VM
       href: ./windows/tutorial-manage-vm.md
-    - name: 2 - Create / manage disks
+    - name: Create / manage disks
       href: ./windows/tutorial-manage-data-disk.md
-    - name: 3 - Automate configuration
+    - name: Automate configuration
       href: ./windows/tutorial-automate-vm-deployment.md
-    - name: 4 - Create VM images
+    - name: Create VM images
       href: ./windows/tutorial-custom-images.md
-    - name: 5 - Highly available VMs
+    - name: Manage networking
+      href: ./windows/tutorial-virtual-network.md  
+    - name: Highly available VMs
       href: ./windows/tutorial-availability-sets.md
-    - name: 6 - Create a scale set
+    - name: Load Balance VMs
+      href: ../load-balancer/quickstart-load-balancer-standard-public-powershell.md
+    - name: Create a scale set
       href: ./windows/tutorial-create-vmss.md
-    - name: 7 - Load balance VMs
-      href: ./windows/tutorial-load-balancer.md
-    - name: 8 - Manage networking
-      href: ./windows/tutorial-virtual-network.md
 - name: Develop
   items:
   - name: REST API
@@ -1583,7 +1583,7 @@
       href: ../ddos-protection/manage-ddos-protection-template.md?context=/azure/virtual-machines/context/context
   - name: Open ports and filter traffic
     items:
-    - name: CLI 
+    - name: CLI
       href: ../virtual-network/tutorial-filter-network-traffic-cli.md
     - name: PowerShell
       href: ../virtual-network/tutorial-filter-network-traffic-powershell.md

articles/virtual-machines/availability.md

@@ -33,7 +33,7 @@ An [availability set](availability-set-overview.md) is a logical grouping of VMs
 
 
 ## Load balancer
-Combine the [Azure Load Balancer](../load-balancer/load-balancer-overview.md) with an availability zone or availability set to get the most application resiliency. The Azure Load Balancer distributes traffic between multiple virtual machines. For our Standard tier virtual machines, the Azure Load Balancer is included. Not all virtual machine tiers include the Azure Load Balancer. For more information about load balancing your virtual machines, see **Load Balancing virtual machines** for [Linux](linux/tutorial-load-balancer.md) or [Windows](windows/tutorial-load-balancer.md).
+Combine the [Azure Load Balancer](../load-balancer/load-balancer-overview.md) with availability zones and scale sets to get the most application resiliency. The Azure Load Balancer distributes traffic between multiple virtual machines. For our Standard tier virtual machines, the Azure Load Balancer is included. Not all virtual machine tiers include the Azure Load Balancer. For more information about load balancing your virtual machines, see the Load Balancer quickstarts using the [CLI](../load-balancer/quickstart-load-balancer-standard-public-cli.md) or [PowerShell](../load-balancer/quickstart-load-balancer-standard-public-powershell.md).
 
 
 ## Azure Storage redundancy

articles/virtual-machines/linux/media/tutorial-load-balancer/running-nodejs-app.png

@@ -179,7 +179,7 @@ In this tutorial, you created a Virtual Machine Scale Set. You learned how to:
 > * Open port 80 to HTTP traffic.
 > * Test the scale set.
 
-Advance to the next tutorial to learn more about load balancing concepts for virtual machines.
+Advance to the next topic to learn more about load balancing concepts for virtual machines.
 
 > [!div class="nextstepaction"]
-> [Load balance virtual machines](tutorial-load-balancer.md)
+> [Load balance virtual machines](../../load-balancer/quickstart-load-balancer-standard-public-cli.md)