Bring Your Own IP to Microsoft Azure with Custom IP Prefix
Use your own IP address space in Azure. Maintain ownership, improve visibility, and reduce recurring costs.
What is Azure Custom IP Prefix?
Azure Custom IP Prefix (BYOIP) allows you to bring IP ranges that you own and register them for use inside Azure. These IPs are integrated with Azure services similarly to Microsoft-assigned public IPs, but you retain full control.
Supported for IPv4 and IPv6 (with limitations)
Must be registered with a recognized RIR (e.g., RIPE, ARIN)
Requires creation of a Route Origin Authorization (ROA) for Microsoft ASN
IPXO is a trusted partner for businesses across 75+ industries
Why Use IPXO for Azure BYOIP?
IPXO helps you bring your own IPs to Azure faster and more cost-effectively.
- Simplified ROA/RPKI Management: IPXO handles Route Origin Authorizations and routing policy validation for Microsoft ASN (8075)
- No Hourly Billing: Flat-rate IP leasing helps reduce cost unpredictability
- Announcing IP ranges under IPXO’s existing policies if required
- Reverse DNS Support: Full rDNS configuration for BYOIP blocks (something Azure doesn’t offer natively)
- Reducing time-to-propagation and complexity
- IP Health Monitoring: Track blacklisting and reputation in real time
This is useful if:
You don’t want to deal with BGP and ROA mechanics
You lease IPs and want them quickly deployable in Azure
You want to integrate multiple clouds (AWS, Azure) under one platform
Cost Benefits of using BYOIP
(Custom IP Prefix)
Using BYOIP in Azure avoids public IP address charges.
| Cost Comparison | Azure Native IP | BYOIP (Custom IP Prefix) |
| Public IP monthly fee |  |  |
| Retention after use | Released | Persistent (owned) |
| IP Reputation | Shared pool | Under your control |
Significant monthly savings
Up to 70% reduction vs Azure-assigned IPs, depending on the size of your IP pool and usage patter.
Microsoft Azure’s IP costs vs. IPXO’s IP lease costs
Discover how much you can save by leasing IPs via IPXO compared to paying for IPs supplied by your infrastructure provider.
Enter your IP address count or subnet size
Price per IP offered by your infrastructure provider vs. IPXO*
1 month
12 months
1 month
12 months
1 month
12 months
1 month
12 months
Supported Azure Services
You can use BYOIP (via Custom IP Prefix) with the following Azure services:
| Azure Service | BYOIP Support | Buying |
| Virtual Machines (VMs) | | Assign BYOIP to NICs as static IPs |
| Standard Public Load Balancer | | Frontend IPs supported |
| Azure Firewall | | Use BYOIP for SNAT and public IP |
| Application Gateway (v2 SKU) | | Frontend IP assignment supported |
| VPN Gateway (AZ SKU) | | Use BYOIP as gateway public IP |
| NAT Gateway | | Supported for outbound IP configuration |
| Virtual Machine Scale Sets (VMSS) | | Assign BYOIP to instances |
| Azure DDoS Protection | | Supported for protected IPs |
| Azure DNS (Reverse DNS) | Partial | Requires own reverse zone; Azure-managed zones not supported |
Requirements to Use BYOIP in Azure
To onboard your own IP addresses into Azure:
You also need to decide how the IPs will be allocated: either directly as public IPs or via Public IP Prefix resources.
Limitations to Consider
Azure does not allow BYOIP addresses to be used for mailing services (SMTP). If you’re planning to send emails from your IPs, Azure is not a suitable platform for this use case.
Get in Touch
Not sure where to start? Request a demo, a tailored offer or let’s just chat.
Tell us a bit about yourself, and we’ll be in touch with you to discuss how IPXO will help unlock your business full potential by meeting all your IP address needs.
Certified and Accredited Provider
Leave your contact details below
FAQ
BYOIP (Bring Your Own IP) in Azure is implemented through Custom IP Prefix, a feature that lets you use IP address ranges you own with Azure services. These IPs are treated like native Azure IPs but allow full control over routing and reputation.