Cloud Equivalents

Microsoft Azure → Amazon Web Services

AWS equivalent of Public IP addresses and prefixes

The closest AWS equivalents of Public IP addresses and prefixes are Elastic IP addresses (and BYOIP) and Internet gateway (and egress-only internet gateway).

Last verified: · Edit on GitHub

About Public IP addresses and prefixes

ProviderMicrosoft Azure
StatusGenerally available
What it isStandard SKU static public IPv4 and IPv6 addresses, contiguous public IP prefixes, and custom IP prefixes (bring your own IP). Basic SKU public IPs retired September 30, 2025.
Documentationlearn.microsoft.com
PricingOfficial pricing page

AWS mappings (2)

Virtual networks, subnets & IP addressing(1)

Static public IP addresses Direct match

Elastic IP addresses map to Azure Standard public IP addresses. Public IP prefixes give contiguous ranges, and custom IP prefixes let you bring your own ranges (like AWS BYOIP).

  • Lifecycle. Basic SKU public IPs retired on September 30, 2025, so use Standard (static, zone-redundant, secure by default) on Azure.
  • Charges. AWS charges for every public IPv4 address, whether attached or idle. Azure charges per public IP and prefix, by SKU.

Full comparison →

Routing & internet access(1)

Internet gateway (inbound and outbound internet access) Partial match

Azure has no internet gateway resource. Resources reach the internet through a public IP, NAT Gateway, load balancer outbound rules, or Azure Firewall. Default outbound access (implicit internet access for VMs) is being phased out with private subnets.

  • Control. On AWS, a subnet without a route to an internet gateway has no internet path. On Azure, VMs in older subnets could get implicit default outbound access, which Microsoft is retiring in favor of explicit outbound methods.
  • IPv6 egress-only. AWS has an egress-only internet gateway for IPv6. On Azure, use NAT Gateway StandardV2 (IPv6) or NSG rules.

Full comparison →