How can we improve Azure Virtual Machines?

Allow adding a reservered IP address to an existing VM

32 votes
Sign in
(thinking…)
Password icon
Signed in as (Sign out)

We’ll send you updates on this idea

Anonymous shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

4 comments

Sign in
(thinking…)
Password icon
Signed in as (Sign out)
Submitting...
  • Jason Turnbull commented  ·   ·  Flag as inappropriate

    This will convert an existing dynamic IP address to reserved IP address:

    New-AzureReservedIP -ReservedIPName $ReservedIP -Location “West Europe” -ServiceName $serviceName

    This is not documented anywhere

  • Anonymous commented  ·   ·  Flag as inappropriate

    This is a problem not only for existing VMs, but also for existing Cloud services. It seems like the only way currently to get a Reserved IP for an existing cloud service is to delete it and recreate it. This kind of downtime is not acceptable in production applications.

    A reserved IP is essential for SAAS applications to create firewall rules for our corporate customers. Finally this feature is available on Azure, but we have not been able to use it cause we cannot afford the downtime.

  • Anonymous commented  ·   ·  Flag as inappropriate

    More than six months ago everybody was promising this (people from Microsoft on blogs and forums: "it is a very critical scenario and we are working on this functionality"... "you can expect to hear from us on the capability to reserve the IP of an existing deployment"...)

    What happened?

    Your most loyal customers are those who already had systems running when these announcements were made. Systems are still being carefully rebooted without external shutdowns to avoid losing virtual IPs, but this is not how a modern system should be managed, is it? This sounds a lot like "Sorry, if you badly wanted this feature you should have done this on Amazon."

Feedback and Knowledge Base