Public IP address uses basic SKU
March 21, 2025 ยท View on GitHub
SYNOPSIS
The basic SKU is being retired on 30 September 2025, and does not include several reliability and security features.
DESCRIPTION
Public IP addresses allow Internet resources to communicate inbound to Azure resources. Currently two SKUs are supported: Basic and Standard.
The Standard SKU additionally offers security and redundancy improvements over the Basic SKU. Including:
- Secure by default model and be closed to inbound traffic when used as a frontend. Network security groups are required to allow inbound traffic.
- Support for zone-redundancy and zonal deployments at creation. Zone-redundancy should mach the zone-redundancy of the resource it is attached to.
- Have an adjustable inbound originated flow idle timeout.
- More granular control of how traffic is routed between Azure and the Internet.
RECOMMENDATION
Consider using Standard SKU for Public IP addresses deployed in production.
EXAMPLES
Configure with Azure template
To configure Standard SKU for a Public IP address.
- Set
sku.nametoStandard.
For example:
{
"type": "Microsoft.Network/publicIPAddresses",
"apiVersion": "2024-01-01",
"name": "[parameters('name')]",
"location": "[parameters('location')]",
"sku": {
"name": "Standard",
"tier": "Regional"
},
"properties": {
"publicIPAddressVersion": "IPv4",
"publicIPAllocationMethod": "Static",
"idleTimeoutInMinutes": 4
},
"zones": [
"1",
"2",
"3"
]
}
Configure with Bicep
To configure Standard SKU for a Public IP address.
- Set
sku.nametoStandard.
For example:
For example:
resource pip 'Microsoft.Network/publicIPAddresses@2024-01-01' = {
name: name
location: location
sku: {
name: 'Standard'
tier: 'Regional'
}
properties: {
publicIPAddressVersion: 'IPv4'
publicIPAllocationMethod: 'Static'
idleTimeoutInMinutes: 4
}
zones: [
'1'
'2'
'3'
]
}