Retire LB troubleshoot set and add support-help page

Author: mbender-ms

articles/load-balancer/TOC.yml

@@ -261,24 +261,10 @@
           href: load-balancer-manage-health-status.md
 - name: Troubleshoot
   items:
-    - name: Troubleshoot Azure Load Balancer
-      href: load-balancer-troubleshoot.md
+    - name: Support and troubleshooting for Azure Load Balancer
+      href: load-balancer-support-help.md
     - name: Testing inbound frontend IP address reachability
       href: load-balancer-test-frontend-reachability.md
-    - name: Health Probe status
-      href: load-balancer-troubleshoot-health-probe-status.md
-    - name: Backend pool (VM) traffic
-      href: load-balancer-troubleshoot-backend-traffic.md
-    - name: Troubleshoot SNAT exhaustion and connection timeouts
-      href: troubleshoot-outbound-connection.md
-    - name: Resource health and inbound availability issues
-      href: troubleshoot-rhc.md
-    - name: Common error codes for Azure Instance Metadata Service (IMDS)
-      href: troubleshoot-load-balancer-imds.md
-    - name: Common deployment errors
-      href: load-balancer-common-deployment-errors.md
-    - name: Troubleshoot load balancer health event logs
-      href: load-balancer-troubleshoot-health-event-logs.md
 - name: Reference
   items:
     - name: Code samples

articles/load-balancer/howto-load-balancer-imds.md

@@ -88,7 +88,7 @@ curl -H "Metadata:true" --noproxy "*" "http://169.254.169.254:80/metadata/loadba
 ```
 
 ## Next steps
-[Common error codes and troubleshooting steps](troubleshoot-load-balancer-imds.md)
+[Support and troubleshooting for Azure Load Balancer](load-balancer-support-help.md)
 
 Learn more about [Azure Instance Metadata Service](/azure/virtual-machines/windows/instance-metadata-service)
 

articles/load-balancer/index.yml

@@ -129,12 +129,12 @@ landingContent:
     linkLists:
         - linkListType: how-to-guide
           links:
-          - text: Troubleshoot Azure Load Balancer
-            url: /azure/load-balancer/load-balancer-troubleshoot
+          - text: Support and troubleshooting for Azure Load Balancer
+            url: /azure/load-balancer/load-balancer-support-help
           - text: Testing reachability of Azure Load Balancer
             url: /azure/load-balancer/load-balancer-test-frontend-reachability
-          - text: Troubleshoot Azure Load Balancer health probe status
-            url: /azure/load-balancer/load-balancer-troubleshoot-health-probe-status
+          - text: Azure Load Balancer troubleshooting documentation
+            url: /troubleshoot/azure/load-balancer/
   # Card
   - title: Related load balancing and content delivery services
     linkLists:

articles/load-balancer/instance-metadata-service-load-balancer.md

@@ -29,7 +29,7 @@ For more information on how to access the load balancer metadata, see [Use Azure
 
 ## Troubleshoot common error codes
 
-For more information on common error codes and their mitigation methods, see [Troubleshoot common error codes when using IMDS](troubleshoot-load-balancer-imds.md). 
+For more information on support and troubleshooting resources, see [Support and troubleshooting for Azure Load Balancer](load-balancer-support-help.md).
 
 ## Support
 

articles/load-balancer/load-balancer-common-deployment-errors.md

@@ -115,7 +115,7 @@ sections:
       - question: |
           Can I access the frontend of my internal load balancer from the participating backend pool VM?
         answer: |
-          No, Azure Load Balancer doesn't support this scenario. To learn more, visit our [troubleshoot page](load-balancer-troubleshoot-backend-traffic.md#cause-4-access-of-the-internal-load-balancer-frontend-from-the-participating-load-balancer-backend-pool-vm).
+          No, Azure Load Balancer doesn't support this scenario. To learn more, visit [Support and troubleshooting for Azure Load Balancer](load-balancer-support-help.md).
 
       - question: |
           What are best practices with respect to outbound connectivity?

articles/load-balancer/load-balancer-faqs.yml

@@ -55,4 +55,4 @@ In this article, you learned about Azure Load Balancer health event logs and hea
 For more information about how to collect, analyze, and create alerts using these logs, along with troubleshooting each health event type, see:
 
 - [Learn to monitor and alert with Azure Load Balancer health event logs](load-balancer-monitor-alert-health-event-logs.md).
-- [Troubleshoot Azure Load Balancer health event logs](load-balancer-troubleshoot-health-event-logs.md)
+- [Support and troubleshooting for Azure Load Balancer](load-balancer-support-help.md)

articles/load-balancer/load-balancer-health-event-logs.md

@@ -147,4 +147,4 @@ In this article, you learned how to collect, analyze, and create alerts using th
 For more information about Azure Load Balancer health event logs and health event types, along with how to troubleshoot each health event type, see:
 
 - [Azure Load Balancer health event logs](load-balancer-health-event-logs.md)
-- [Troubleshoot load balancer health event logs](./load-balancer-troubleshoot-health-event-logs.md)
+- [Support and troubleshooting for Azure Load Balancer](./load-balancer-support-help.md)

articles/load-balancer/load-balancer-monitor-alert-health-event-logs.md

@@ -160,7 +160,7 @@ Outbound connections can burst. A backend instance can be allocated insufficient
 
 For more information about connection pooling with Azure App Service, see [Troubleshooting intermittent outbound connection errors in Azure App Service](../app-service/troubleshoot-intermittent-outbound-connection-errors.md#avoiding-the-problem)
 
-New outbound connections to a destination IP fail when port exhaustion occurs. Connections succeed when a port becomes available. This exhaustion occurs when the 64,000 ports from an IP address are spread thin across many backend instances. For guidance on mitigation of SNAT port exhaustion, see the [troubleshooting guide](./troubleshoot-outbound-connection.md). 
+New outbound connections to a destination IP fail when port exhaustion occurs. Connections succeed when a port becomes available. This exhaustion occurs when the 64,000 ports from an IP address are spread thin across many backend instances. For guidance on mitigation of SNAT port exhaustion, see [Support and troubleshooting for Azure Load Balancer](./load-balancer-support-help.md).
 
 ## Port reuse
 For TCP connections, the load balancer uses a single SNAT port for every destination IP and port. For connections to the same destination IP, a single SNAT port can be reused as long as the destination port differs. Reuse isn't possible when there already exists a connection to the same destination IP and port.
@@ -185,7 +185,6 @@ In the example in the following table, a backend instance with private IP 10.0.0
 *	Each IP address provides 64,000 ports that can be used for SNAT.
 
 *	Each port can be used for both TCP and UDP connections to a destination IP address
-
   *	A UDP SNAT port is needed whether the destination port is unique or not. For every UDP connection to a destination IP, one UDP SNAT port is used.
 
   *	A TCP SNAT port can be used for multiple connections to the same destination IP provided the destination ports are different.
@@ -198,6 +197,6 @@ In the example in the following table, a backend instance with private IP 10.0.0
 
 ## Next steps
 
-*	[Troubleshoot outbound connection failures because of SNAT exhaustion](./troubleshoot-outbound-connection.md)
+*	[Support and troubleshooting for Azure Load Balancer](./load-balancer-support-help.md)
 *	[Review SNAT metrics](./load-balancer-standard-diagnostics.md#how-do-i-check-my-snat-port-usage-and-allocation) and familiarize yourself with the correct way to filter, split, and view them.
 *	Learn how to [migrate your existing outbound connectivity method to NAT gateway](../virtual-network/nat-gateway/tutorial-migrate-outbound-nat.md)

articles/load-balancer/load-balancer-outbound-connections.md

@@ -293,8 +293,8 @@ Health status for the standard load balancer resources is exposed via the existi
 | Resource health status | Description |
 | --- | --- |
 | Available | Your standard load balancer resource is healthy and available. |
-| Degraded | Your standard load balancer has platform or user initiated events impacting performance. The metric for data path availability has reported less than 90% but greater than 25% health for at least two minutes. With this status, you experience moderate to severe performance effect. [Follow the troubleshooting RHC guide](./troubleshoot-rhc.md) to determine whether there are user initiated events causing impacting your availability.
-| Unavailable | Your standard load balancer resource isn’t healthy. The metric for data path availability has reported less the 25% health for at least two minutes. With this status, you experience significant performance effect or lack of availability for inbound connectivity. There may be user or platform events causing unavailability. [Follow the troubleshooting RHC guide](./troubleshoot-rhc.md) to determine whether there are user initiated events impacting your availability. |
+| Degraded | Your standard load balancer has platform or user initiated events impacting performance. The metric for data path availability has reported less than 90% but greater than 25% health for at least two minutes. With this status, you experience moderate to severe performance effect. See [Support and troubleshooting for Azure Load Balancer](./load-balancer-support-help.md) to determine whether there are user initiated events impacting your availability.
+| Unavailable | Your standard load balancer resource isn’t healthy. The metric for data path availability has reported less the 25% health for at least two minutes. With this status, you experience significant performance effect or lack of availability for inbound connectivity. There may be user or platform events causing unavailability. See [Support and troubleshooting for Azure Load Balancer](./load-balancer-support-help.md) to determine whether there are user initiated events impacting your availability. |
 | Unknown | Health status for your load balancer resource hasn’t been updated or hasn’t received information for data path availability for the last 10 minutes. This state should be transient and will reflect correct status as soon as data is received. |
 
 To view the health of your public standard load balancer resources: