201-vmss-internal-loadbalancer should use two balancer to two VMSS

--------------------MESSAGE FROM ADMIN, DELETE BEFORE SUBMITTING----------------------

Sorry to hear you had a bad experience with one of the templates :worried: But, in case you're just asking a question, we're happy to help. You can also check if the question might already have been asked here https://github.com/Azure/azure-quickstart-templates/issues?utf8=%E2%9C%93&q=is%3Aissue

We've created an outline of recommended sections to fill out that will help make this Pull Request awesome!

--------------------MESSAGE FROM ADMIN, DELETE BEFORE SUBMITTING----------------------

[Template Name goes here](Template link goes here)

### Issue Details
I deployed two VMSS and it seems that we cannot use one load balancer to distribute the traffics for two different VMSS. So I deployed two VMSS and two loader balancer successfully, but the problem is I use these two VMSS for a cluster ( with two different nodes ) for the same workloads, so either one of node fails, the workload won't be working correctly. Is there any way to use the same ALB between two VMSS ? Thank you :)

### Repro steps (*if necessary, delete otherwise*)
1.
2.
3.
4.
5.

Start by locating the 201-vmss-internal-loadbalancer template and reviewing how its VM scale sets and load balancer resources are connected. Reproduce the two-VMSS scenario in Azure and verify the supported topology; done means the template behavior or its limitations are clearly established and the issue's requested configuration is addressed.

Written by the indexing model from the issue text.