

Virtual Network NAT (network address translation) simplifies outbound-only Internet connectivity for virtual networks. You can’t attach standalone virtual machines, virtual machines in an availability set resource, or a virtual machine scale set resources to both SKUs simultaneously. You can’t have a mixture of basic SKU resources and standard SKU resources. Matching SKUs must be used for load balancer and public IP resources. Some of the resources you can associate a public IP address resource with are: If a public IP address is not assigned to a resource, the resource can still communicate outbound to the Internet, but Azure dynamically assigns an available IP address that is not dedicated to the resource. The address is dedicated to the resource, until it is unassigned by you. Public IP addresses also enable Azure resources to communicate outbound to Internet and public-facing Azure services with an IP address assigned to the resource. Public IP addresses allow Internet resources to communicate inbound to Azure resources. Remember there is no good or wrong but only different opinions or insights on how to use it. There a several ways on using an external IP in Azure, What method to use is up to you.
