Bring Your Own Public IP Address space and Internet subnet routing in Azure Virtual Networks
When you own a public address space IPv4 and/or IPv6, Windows Azure should provide a way to use it (via LISP and/or classic routing).
When you don't own a public address space, you should be able to rent it for your virtual network on Windows Azure both via Microsoft or via Tunnel Broker providers
Olivier Hault (Level IT)
shared this idea
Due to increased interest in BYOIP to Azure, we are reviewing design options however we do not yet have timelines to share. Thank you for your interest in BYOIP- your comments here help us make the case.
11 comments
-
Michael D
commented
+1
-
Steve
commented
+1 we are nearly all Azure public cloud however have had to keep some on-premis hosting in EMEA, UK and US for this reason that we cannot use our current /21 ranges in Azure. This would be a huge plus to us if we could do this, possibly with a reduced data egress cost when using our own IP ranges as this is the other blocker for us not putting these workloads in Azure. Seems like AWS have just released their version of this also.
-
Michael Rogan
commented
+1
-
Guven
commented
+1
-
Anonymous
commented
+1
-
Anonymous
commented
A +1 for this feature. I'm looking for a cloud provider that I can bring my own /24 network range to.
-
Mike
commented
Just as AWS announce it
-
Anonymous
commented
How can I bring my own IP addresses to Azure??
-
Anonymous
commented
This is marked as completed, but with no other information?
-
Olivier Hault (Level IT)
commented
And what's about LISP and http://opencontrail.org/about/ support ?
-
Updated the subject a bit to further clarify the ask.
Thanks!
Yushun [MSFT]
