Edit

Share via

Plan for inbound and outbound internet connectivity

  • Article

This article lists considerations and recommendations for inbound and outbound connectivity between Azure and the public internet.

Design considerations

  • Azure native network security services such as Azure Firewall, Azure Web Application Firewall (WAF) on Azure Application Gateway, and Azure Front Door are fully managed. You don't incur the operational and management costs and complexity of infrastructure deployments at scale.

  • If your organization prefers to use non-Azure network virtual appliance (NVAs), or for situations where native services don't satisfy specific requirements, the Azure landing zone architecture is fully compatible with partner NVAs.

  • Azure provides several direct internet outbound connectivity methods, such as network address translation (NAT) gateways or load balancers, for virtual machines (VMs) or compute instances on a virtual network. Azure NAT Gateway is recommended as the default for enabling outbound connectivity as it is operationally the simplest to set up, and is the most scalable and efficient option among all outbound connectivity methods available in Azure. For more information, see Azure outbound connectivity methods.

Design recommendations

  • Use Azure NAT Gateway for direct outbound connectivity to the internet. A NAT gateway is a fully managed, highly resilient NAT service that provides scalable and on-demand SNAT.

    • Use a NAT gateway for:

      • Dynamic or large workloads sending traffic to the internet.
      • Static and predictable public IP addresses for outbound connectivity. NAT gateway can be associated with up to 16 public IP addresses or a /28 public IP prefix.
      • Mitigation of issues with SNAT port exhaustion commonly experienced with Load balancer outbound rules, Azure Firewall, or Azure App Services.
      • Security and privacy of resources within your network. Only outbound and return traffic can pass through NAT gateway.

  • Use Azure Firewall to govern:

    • Azure outbound traffic to the internet.
    • Non-HTTP/S inbound connections.
    • East-west traffic filtering, if your organization requires it.

  • Use Azure Firewall Premium for advanced firewall capabilities, such as:

    • Transport Layer Security (TLS) inspection.
    • A network intrusion detection and prevention system (IDPS).
    • URL filtering.
    • Web categories.

  • Azure Firewall Manager supports both Azure Virtual WAN and regular virtual networks. Use Firewall Manager with Virtual WAN to deploy and manage Azure firewalls across Virtual WAN hubs or in hub virtual networks.

  • If you use multiple IP addresses and ranges consistently in Azure Firewall rules, set up IP Groups in Azure Firewall. You can use the IP groups in Azure Firewall DNAT, network, and application rules for multiple firewalls across Azure regions and subscriptions.

  • If you use a custom user defined route (UDR) to manage outbound connectivity to Azure platform as a service (PaaS) services, specify a service tag as the address prefix. Service tags update underlying IP addresses automatically to include changes, and reduce the overhead of managing Azure prefixes in a route table.

  • Create a global Azure Firewall policy to govern security posture across the global network environment. Assign the policy to all Azure Firewall instances.

  • Allow granular policies to meet specific region requirements by using Azure role-based access control to delegate incremental policies to local security teams.

  • Use WAF within a landing-zone virtual network for protecting inbound HTTP/S traffic from the internet.

  • Use Azure Front Door and WAF policies to provide global protection across Azure regions for inbound HTTP/S connections to a landing zone.

  • To use Azure Front Door and Azure Application Gateway to help protect HTTP/S applications, use WAF policies in Azure Front Door. Lock down Azure Application Gateway to receive traffic only from Azure Front Door.

  • If you need partner NVAs for inbound HTTP/S connections, deploy them within a landing-zone virtual network, together with the applications that they protect and expose to the internet.

  • For outbound access, don't use Azure's default internet outbound access for any scenario. Issues experienced with default outbound access include:

    • Increased risk of SNAT port exhaustion.
    • Insecure by default.
    • Can't depend on default access IPs. They aren't owned by the customer and subject to change.

  • Use a NAT gateway for online landing zones, or landing zones not connected to the hub virtual network. Compute resources that need outbound internet access and don't need the security of Azure Firewall standard or premium, or a third-party NVA, can use online landing zones.

  • If your organization wants to use software-as-a-service (SaaS) security providers to help protect outbound connections, configure supported partners within Firewall Manager.

  • If you use partner NVAs for east-west or north-south traffic protection and filtering:

    • For Virtual WAN network topologies, deploy the NVAs to a separate NVA virtual network. Connect the virtual network to the regional Virtual WAN hub and to the landing zones that need access to the NVAs. For more information, see Scenario: Route traffic through an NVA.
    • For non-Virtual WAN network topologies, deploy the partner NVAs in the central hub virtual network.

  • Don't expose VM management ports to the internet. For management tasks:

  • Use Azure DDoS Protection protection plans to help protect the public endpoints you host within your virtual networks.

  • Don't try to replicate on-premises perimeter network concepts and architectures into Azure. Although Azure has similar security capabilities, the implementation and architecture are adapted to the cloud.