Azure fixed VIP for already existing cloud services

In a previously done project, the pre-customer did not put forward the need for fixed IP features, customer application system has been launched after the customer put forward their public IP will change, resulting in the entire application paralysis, need to re-change the configuration file to use, where the customer's application can only identify IP, do not recognize DNS. Before encountering the requirements of their own to do is to add a virtual machine under the same cloud service in the same availability cluster, so as far as possible to make two virtual machines do not have the same downtime to ensure that the public IP is not re-updated, not only increases the cost, itself also has a great risk.

Note: We will get a VIP when we create a new cloud service, this VIP may change.

Recently updated in the background by Microsoft, using the latest PowerShell to secure the VIP of existing cloud Service

Latest PowerShell now Address: http://azure.microsoft.com/en-us/downloads/

1. Fixed IP for existing cloud services:

   New-azurereservedip-servicename ' Maccloudservice '-reservedipname ' maccloudservicevip '-Location ' China East '

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M02/5C/02/wKioL1UZEWTyCn3MAAJYdEnejDo094.jpg "style=" float: none; "title=" Lhh@ll0bd1up7m_ci5$2}9m.png "alt=" Wkiol1uzewtycn3maajydenejdo094.jpg "/>

2. View the IP that has been assigned:

Get-azurereservedip-reservedipname "MACCLOUDSERVICEVIP"

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M02/5C/08/wKiom1UZECnj4Cx3AAIyWYWk7QA284.jpg "style=" float: none; "title=" Tengc3]h80faj6q$z10p55b.png "alt=" Wkiom1uzecnj4cx3aaiywywk7qa284.jpg "/>

This article references: http://www.cnblogs.com/threestone/p/4335382.html

This article is from the "jeff-Microsoft Public Cloud" blog, be sure to keep this source http://jeffcsc.blog.51cto.com/8669937/1626485

Azure fixed VIP for already existing cloud services