How can we improve Azure Networking?

← Networking

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

587 votes
Vote
Sign in
(thinking…)
Sign in with: Microsoft
Forgot password?
Create a password
Signed in as (Sign out)
Close
Close
You have left! (?) (thinking…)
Olivier Hault (Level IT) shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

22 comments

Sign in
(thinking…)
Sign in with: Microsoft
Forgot password?
Create a password
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • Anonymous commented  ·   ·  Flag as inappropriate

    This is an absolute requirement. I can see AWS and GCP support it. Come on Azure....

  • Wesley commented  ·   ·  Flag as inappropriate

    Hello, how are you?
    I wonder if Microsoft has predicted when it will have the BYOIP service and if it will?
    Thank you

  • Anonymous commented  ·   ·  Flag as inappropriate

    Guys any update on the possible release date? Even alpha release date is good 🙂

  • Mattias S commented  ·   ·  Flag as inappropriate

    +1 - we have several sourcing customers with a hybrid approach (or cloud-only) who request this feature on Azure - as of today we have to route them to our own datacenters and then pass the traffic on to Azure. AFAIK AWS is supporting this (since about a year) making the clients obvoisly wondering why Azure doesn't.

    Thanks!

  • Jamie Evans commented  ·   ·  Flag as inappropriate

    Clients often need to whitelist specific addresses for outbound communications to Azure hosted resources. This is fine until making considerations for migration to Azure, and continuity / disaster recovery. BYOIP would be extremely helpful as clients are using upstream services for POP.

  • Steve commented  ·   ·  Flag as inappropriate

    +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.

  • Anonymous commented  ·   ·  Flag as inappropriate

    A +1 for this feature. I'm looking for a cloud provider that I can bring my own /24 network range to.

← Previous 1

Networking: IP addresses

Categories

Feedback and Knowledge Base

(thinking…)
Hosted by UserVoice