Allow adding a reservered IP address to an existing VM
Vaclav Elias commented
As Jason mentioned, you should be able to do this now. Check for example these instructions http://clemmblog.azurewebsites.net/convert-existing-dynamic-vip-reserved-ip-addresses-azure/
Jason Turnbull commented
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
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.
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"...)
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."