Skip to content

Microsoft Azure BYOIP Integration Overview

BYOIP SUPPORTER
ASN 8075
IPv4 support
IPv6 support
LOA support
ROA support
Process Semi-automatic
Locations supported
Atlanta, Chicago, Dallas, Denver, Des Moines, Houston, Los Angeles, Miami, New York, San Francisco, Seattle, Silicon Valley, Washington, D.C., Australia, Brazil, Canada, Chile, France, Germany, India, Ireland, Japan, Mexico, Netherlands, New Zealand, Norway, Singapore, South Korea, Switzerland, United Kingdom

This page outlines the technical and procedural information required for integrating Bring Your Own IP (BYOIP) with Microsoft Azure infrastructure.

Looking for the best IP providers? Azure offers advanced BYOIP capabilities with automation, reputation management, and global availability. This guide covers Azure setup docs, reviews, requirements, benefits, and pricing for seamless BYOIP integration.

Provider Details

FieldInformation
Provider NameMicrosoft Azure
WebsiteCloud Computing Services | Microsoft Azure
ASN(s)AS8075 (Microsoft’s ASN; use your own ASN if required)
Regions SupportedAll Azure public regions
Support ContactAzure Support Options
Tech Article & DateBring your own IP addresses (BYOIP) to Azure with Custom IP Prefix – February 2022
BYOIP ScopeGeneral Availability (IPv4 and IPv6)
Supported VersionsIPv4 and IPv6
Supported ServicesVMs, Load Balancers, Azure Firewall, VPN Gateway, Application Gateway, Azure Front Door, and others using Standard SKU Public IPs

Technical Requirements

RequirementDetails
Prefix SizeIPv4: /21 to /24 (Parent), /22 to /26 (Regional)
IPv6: /48 (Parent), /64 (Regional)
ASN Ownership RequiredNot strictly required; ROA needed for the ASN that originates the route
IRR or RADb ObjectNot required
ROA or LOAROA required; LOA not required
RIR LimitationsPrefixes must be registered with ARIN, RIPE, or APNIC

Step-by-Step BYOIP Process

Estimated Setup Time: Varies by provisioning and prefix validation

Tested By Us: Not tested

1. Preparation

  • Register your IP prefix with ARIN, RIPE, or APNIC
  • Create a ROA using your ASN or Microsoft’s ASN
  • Add a self-signed X.509 certificate to the WHOIS public comment for the prefix

2. Provisioning

  • Create a Custom IP Prefix resource via Azure Portal, CLI, or API
  • Commission the prefix to allow Azure to begin advertising

3. Usage

  • Derive and assign Public IPs from the Custom IP Prefix
  • Use them with supported services like VMs, Load Balancers, Azure Firewall, etc.

Cost and Limitations

ItemDetails
FeesNo additional fees; standard public IP and data transfer rates apply
Bundled or StandaloneBYOIP integrates with DDoS Protection, Azure Firewall, etc.
Traffic/Peering RestrictionsBYOIP not allowed over ExpressRoute Microsoft Peering; no global tier or Internet routing preference
Other LimitationsReverse DNS must be managed externally; cannot move Custom IP Prefix between subscriptions

Automation & Developer Access

  • API Access: Supported via Azure REST API, CLI, and PowerShell

Abuse & Reputation Management

  • IP Reputation Monitoring: Not provided
  • Blacklist Removal Support: Customer-managed

Azure BYOIP Blog Post
IPXO Setup Guide

FAQ

BYOIP, or Bring Your Own IP, is a service that enables organizations to bring their own public IP addresses—whether owned outright or leased from an IP provider—into a service provider’s network infrastructure. Instead of relying on IP addresses assigned by the provider, BYOIP allows businesses to retain control over their IP resources. This ensures continuity, particularly for organizations with established IP-based reputations, branding, or dependencies on specific address blocks. IP providers can assist in streamlining this process, making it easy to integrate your IPs into the desired network environment.

BYOIP offers several compelling advantages. By using your own IPs, you can maintain continuity in your network’s identity, reduce the risk of disruptions to email deliverability or service recognition, and avoid reputational concerns associated with shared IPs. Additionally, BYOIP provides enhanced flexibility and control over your IP resources.

BYOIP is ideal for organizations that either own public IP addresses or lease them from a trusted IP provider with explicit BYOIP support. This includes enterprises, cloud providers, content delivery networks (CDNs), and businesses with compliance requirements or IP reputation needs. Working with a reputable IP provider ensures that leased IPs can be seamlessly integrated into another provider’s infrastructure without ownership concerns.

You must either legally own the IP addresses or have explicit authorization from a leasing IP provider to route and manage them. IP providers who offer BYOIP-ready IP addresses simplify this process, providing documentation and support to ensure compliance with regional internet registry (RIR) policies and service provider requirements. This collaboration ensures smooth implementation without any legal or operational issues.

To use BYOIP, you’ll typically need to present documentation verifying your authority over the IP block. This can include official records from a regional internet registry (RIR) such as ARIN, RIPE NCC, or APNIC. If you are leasing IPs, the IP provider should supply proof of their ownership and grant you permission for BYOIP. Providers that specialize in IP leasing often handle this paperwork for you, reducing administrative burden and ensuring compliance.

Yes, BYOIP is designed to be a secure and reliable solution. Reputable service providers and IP providers implement robust safeguards to prevent unauthorized use or hijacking of IP addresses. Security measures include BGP filtering, route validation, and advanced protocols like Resource Public Key Infrastructure (RPKI). By collaborating with a trusted IP provider, businesses can benefit from additional layers of protection, ensuring that only authorized traffic is routed through their IP blocks.

The setup process for BYOIP varies by provider, typically taking anywhere from a few hours to a few days. Factors include the complexity of your network, the verification process for IP ownership or authorization, and the time needed for global BGP route propagation. IP providers often expedite the preparation and validation stages, ensuring a smooth and timely integration into the desired infrastructure.

Absolutely. Many providers, in partnership with IP providers, support routing IPs across multiple data centers or geographic regions. This feature optimizes performance for global businesses by reducing latency and improving service availability. When working with an IP provider, you can also ensure that your leased or owned IPs are aligned with your geographic requirements for compliance and efficiency.

If you choose to discontinue BYOIP with a provider, your IP addresses will be released from their network, and routing will cease. You can then reallocate these IPs for use with a different service provider or project.