Lease IPv4 for Azure BYOIP
Azure lets you bring your own public range with Custom IP Prefix. If you need stable public IPv4 for Azure and do not want to buy a block right away, leasing gives you a simpler path to start.
Savings per /24
1 month
$998.40
12 months
$11980.80
Azure BYOIP workflow
Validate the range before provisioning
Azure checks that the prefix belongs to you and is ready for routing. Microsoft asks for a ROA that authorizes ASN8075, a public X.509 certificate placed in Whois or RDAP, and a signed authorization message tied to your subscription, prefix, and date.Provision the custom IP prefix in Azure
After validation, you create the prefix in Azure as a Custom IP Prefix resource. You can use the unified model or split the space into global and regional prefixes, then derive public IP prefixes and Standard SKU public IPs from that range.Commission the prefix and cut over cleanly
The range is not reachable until you commission it. Microsoft says regional prefixes should usually be commissioned and tested first, then the global prefix. Do not announce the same range from another network at the same time, or you risk routing issues.
Live Estimate
BYOIP savings calculator
See cloud IPv4 cost vs. leased BYOIP
USD
Public IPv4 estimate
$4.30
/ IP / mo
Microsoft Azure
Public IPv4 pricing
1 month
$1100.80
12 months
$13209.60
IPv4 Online
1 month
$102.40
12 months
$1228.80
Savings
1 month
$998.40
12 months
$11980.80
Estimates use public list pricing and a benchmark lease rate for directional comparison only.
Where Azure Custom IP Prefix earns the extra setup work
Use case 01
Existing allowlists are painful to rebuild
If customers, partners, or branch offices already trust a known address range, bringing that range into Azure is often easier than asking everyone to update firewall rules.
Use case 02
New Azure regions need room from day one
Teams use BYOIP when they want a proper address plan for multi-region Azure instead of adding provider IPs wherever capacity happens to be available.
Use case 03
Azure is part of a larger network plan
Custom IP Prefix is easier to justify when Azure is only one piece of the estate and the same public IP strategy also has to work for on-prem systems or another cloud.
Frequently asked questions
Why use leased IPv4 for Azure BYOIP?
Azure Custom IP Prefix lets you keep your own public range inside Azure. Leasing is a practical option when you want that control now but do not want to commit to a full block purchase yet.
What prefix sizes does Azure accept for BYOIP?
Microsoft says a unified custom IPv4 prefix must be between /21 and /24. In the global and regional model, the parent prefix must be between /21 and /24, while regional child prefixes can be between /22 and /26.
What should I prepare before moving a range into Azure?
Azure checks ownership and routing readiness. In practice that usually means the prefix is registered to you with an RIR, the ROA authorizes Microsoft ASN 8075, the public certificate is visible in Whois or RDAP, and the same range is not announced outside Microsoft during cutover.
Need leased IPv4 for Azure BYOIP?
Tell us how many public IPs you need in Azure and whether you plan to use the unified model or a global and regional rollout.