Use dynamic and static public IP addresses ​

In Azure Resource Manager, a public IP address is a resource that has its own properties. Some of the resources you can associate a public IP address resource with:

• Virtual machine network interfaces
• Virtual machine scale sets
• Public Load Balancers
• Virtual Network Gateways (VPN/ER)
• NAT gateways
• Application Gateways
• Azure Firewall
• Bastion Host
• Route Server

Public IP addresses are created with an IPv4 or IPv6 address, which can be either static or dynamic.

Public IP addresses are created with either Standard or Basic SKU

Dynamic public IP address ​

A dynamic public IP address is an assigned address that can change over the lifespan of the Azure resource. The dynamic IP address is allocated when you create or start a VM. The IP address is released when you stop or delete the VM. In each Azure region, public IP addresses are assigned from a unique pool of addresses. The default allocation method is dynamic.

Dynamic public IP addresses can only be configured using the Basic SKU

Static public IP address ​

A static public IP address is an assigned address that won't change over the lifespan of the Azure resource. To ensure that the IP address for the resource remains the same, set the allocation method explicitly to static. In this case, an IP address is assigned immediately. It's released only when you delete the resource or change the IP allocation method to dynamic.

Static public IP addresses can only be configured using the Standard SKU

Choose the appropriate SKU for a public IP address ​

Public IP addresses are created with either Standard or Basic SKU

Key aspects of Standard ​

Allocation method

• Static

Idle Timeout

• Same as Basic
• adjustable inbound of 4-30 minutes
• default of 4 minutes
• fixed outbound originated flow idle timeout of 4 minutes

Security

• Secure by default
• closed to inbound traffic when used as a frontend
• Allow traffic with network security group (NSG) is required

Availability zones

• Supported. Standard IPs can be non-zonal, zonal, or zone-redundant.
• Zone redundant IPs can only be created in regions where 3 availability zones are live.
• IPs created before zones are live won't be zone redundant.

Routing preference

• Supported to enable more granular control of how traffic is routed between Azure and the Internet.

Global tier

• Supported via cross-region load balancers.

Key aspects of Basic ​

Allocation method

• IPv4: Dynamic or Static
• IPv6: Dynamic

Idle Timeout

• Same as Standard
• adjustable inbound of 4-30 minutes
• default of 4 minutes
• fixed outbound originated flow idle timeout of 4 minutes

Security

• Open by default
• Network security groups are recommended but optional

Availability zones

• Not supported.

Routing preference

• Not supported.

Global tier

• Not supported.

Create a public IP address prefix ​

Public IP prefixes are assigned from a pool of addresses in each Azure region. You create a public IP address prefix in an Azure region and subscription by specifying a name and prefix size. The prefix size is the number of addresses available for use. Public IP address prefixes consist of IPv4 or IPv6 addresses. In regions with Availability Zones, Public IP address prefixes can be created as zone-redundant or associated with a specific availability zone. After the public IP prefix is created, you can create public IP addresses.

Custom IP address prefix (BYOIP) ​

Addresses from a custom IP address prefix can be used in the same way as Azure owned public IP address prefixes. Addresses from a custom IP address prefix can be associated to Azure resources, interact with internal/private IPs and virtual networks, and reach external destinations outbound from the Azure Wide Area Network.