Today I’m going to explain about reserved IP with VM’s.
Let’s start with the “Why do I need it…?” Question.
It is a good question, you need it for these examples:
Easy A-Record DNS: Because you want to use and maintain the same public IP after delete/removing/shutdown VMs, you can avoid having to reprogram DNS or other applications depending upon the IP to the newly assigned IP when you restart.
On-Premise Connectivity Security: You can now provide access to your Azure Services from your enterprise network, leveraging the public IP but controlling and ACL’s access through your proxy/firewall on-premises. You now don’t have to worry about re-programming that each time you start and stop your VM.
And now. To the “How to do it…?” Question.
Currently you can do it only from the Azure PowerShell by using this command:
New-AzureVMConfig -Name “WebAppVM” -InstanceSize Large -ImageName $images.ImageName | Add-AzureProvisioningConfig -Windows -AdminUsername $username -Password $password | New-AzureVM -ServiceName “Web” -ReservedIPName “MyWebIP” -Location “West Europe”
There are a few points that you need to know about:
Shutdown VM: Previously, when all the Virtual Machine instances are moved to the Shutdown state, the public IP would be released and a new public IP will be assigned when one of the Virtual Machines instances is started. However, with this release, if the VM uses a Reserved IP, then the Reserved IP can be used when re-deploying the VMs.
Delete VM: When you delete all the Virtual Machines that were using a Reserved IP, the Reserved IP will continue be reserved in your subscription so that it can be used for future VM deployment in the region.
Senior Infrastructure Engineer @ AgileIT