SOLVED

why azure vmss with LB require public ip address

%3CLINGO-SUB%20id%3D%22lingo-sub-728673%22%20slang%3D%22en-US%22%3Ewhy%20azure%20vmss%20with%20LB%20require%20public%20ip%20address%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-728673%22%20slang%3D%22en-US%22%3E%3CP%3EI%20am%20trying%20to%20create%20vmss%20with%20load%20balancer%20but%20I%20don't%20need%20public%20ip%20as%20I%20want%20to%20keep%20both%20private%2C%20however%20when%20I%20create%20VMSS%20keep%20creating%20load%20balancer%20with%20public%20ip%20which%20is%20reachable%20from%20internet.%20I%20am%20able%20to%20create%20Loadbalancer%20with%20private%20ip%20as%20stand%20alone%20for%20vm.%20did%20I%20miss%20something%20as%20I%20am%20new%20to%20azure.%20I%20want%20for%20private%20application.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ethanks%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-728673%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Eazure%20vmss%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-729540%22%20slang%3D%22en-US%22%3ERe%3A%20why%20azure%20vmss%20with%20LB%20require%20public%20ip%20address%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-729540%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%20raindrop.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPlease%20go%20with%20this.%20Hope%20this%20will%20Helpful%20for%20you.%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fvirtual-network%2Fvirtual-network-ip-addresses-overview-arm%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fvirtual-network%2Fvirtual-network-ip-addresses-overview-arm%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fgithub.com%2FAzure%2Fazure-cli%2Fissues%2F1685%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fgithub.com%2FAzure%2Fazure-cli%2Fissues%2F1685%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-729778%22%20slang%3D%22en-US%22%3ERe%3A%20why%20azure%20vmss%20with%20LB%20require%20public%20ip%20address%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-729778%22%20slang%3D%22en-US%22%3E%3CP%3EThere%20is%20a%20difference%20between%20an%20internal%20LB%20and%20an%20external%20LB.%20You%20can%20create%20both%20from%20the%20marketplace%20inside%20the%20Azure%20portal.%20The%20main%20difference%20is%20the%20public%20LB%20allows%20you%20to%20assign%20a%20public%20address%20to%20the%20front%20end%20and%20route%20to%20a%20pool%20of%20private%20IP's%20or%20services.%20The%20internal%20LB%20has%20an%20internal%20address%20on%20the%20front%20end%20and%20has%20the%20same%20capability%20to%20route%20to%20IP's%20or%20services%20on%20the%20back%20end.%20I%20would%20suggest%20reviewing%20the%20following%20link%20to%20see%20if%20you%20run%20into%20any%20other%20limitations.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fload-balancer%2Fload-balancer-standard-overview%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fload-balancer%2Fload-balancer-standard-overview%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F368431%22%20target%3D%22_blank%22%3E%40raindrop18%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Deleted
Not applicable

I am trying to create vmss with load balancer but I don't need public ip as I want to keep both private, however when I create VMSS keep creating load balancer with public ip which is reachable from internet. I am able to create Loadbalancer with private ip as stand alone for vm. did I miss something as I am new to azure. I want for private application.

 

thanks

2 Replies
Highlighted
Best Response
Highlighted

There is a difference between an internal LB and an external LB. You can create both from the marketplace inside the Azure portal. The main difference is the public LB allows you to assign a public address to the front end and route to a pool of private IP's or services. The internal LB has an internal address on the front end and has the same capability to route to IP's or services on the back end. I would suggest reviewing the following link to see if you run into any other limitations. 

 

https://docs.microsoft.com/en-us/azure/load-balancer/load-balancer-standard-overview

 

 

 

@Deleted