How can we improve Azure Networking?

Allow assigning and removing (and swapping!) reserved IP's on cloud services

It is unfortunate right now you cannot just assign or remove reserved ips on a cloud service (or use them with cloud services in Affinity Groups).

We have different cloud services for different environments and it would be great to be able to swap the reserved IP to the current production service. Technically it doesn't need to take the VIP from the cloud service it is swapping with rather just obtain a new (or use its old VIP) once the reserved IP is gone.

Right now reserved IP's are extremely immobile.

1,278 votes
Vote
Sign in
(thinking…)
Sign in with: Microsoft
Signed in as (Sign out)
You have left! (?) (thinking…)
MitchC shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

6 comments

Sign in
(thinking…)
Sign in with: Microsoft
Signed in as (Sign out)
Submitting...
  • Kurt Relinger commented  ·   ·  Flag as inappropriate

    Microsoft has made great strides here: http://azure.microsoft.com/en-us/documentation/articles/virtual-networks-reserved-public-ip/ While not seamless (it takes 1-2 minutes of downtime to do a Remove-AzureReservedIPAssociation followed by a Set-AzureReservedIPAssociation ) but finally reserved ips can move between cloud services. Hopefully mirosoft will add a Swap-AzureReservedIPAssociation or Move-AzureReservedIPAssociation to remove any downtime during the move in the future!

  • Robin Art commented  ·   ·  Flag as inappropriate

    Right now it is not possible to do a proper dev/staging/production clusters without relying on just TTL's and updating DNS to swap between them with virtual machines. This is not really an acceptable option for an enterprise cloud platform. The ability to cut traffic over to a new cloud service cluster is definitely a needed feature.

  • MitchC commented  ·   ·  Flag as inappropriate

    Amazon certainly seems to have a great setup for this, hopefully azure can work similarly: https://aws.amazon.com/articles/1346 you can assign a elastic ip from one instance directly to a new instance. The old instance will automatically get a new public ip once it loses the elastic ip.

    This would be the exact desired behavior for azure.

  • Mark Ravion commented  ·   ·  Flag as inappropriate

    Amazon EC2 has had the ability to assign ips like this and change the assignment on the fly for quite awhile. Azure is definitely lacking true production ready support for environments.

  • Kevin commented  ·   ·  Flag as inappropriate

    I couldn't believe that reserved IP's are so restricted. We were told by our azure rep to use Affinity groups however that has blocked the ability to use reserved IPs. In addition the ability to assign to different services once they are created is definitely needed.

Feedback and Knowledge Base