We recently, through our own actions, lost our public facing IP address on a cloud service we ran in Microsoft Azure. Most of our customers rely on DNS to resolve the IP address and were not affected by the newly assigned IP address. However, a few of
our customers were using the static IP address provided by Microsoft to punch holes through their firewall. We now have to require those customers to use a new IP address.
The solution we were given by the support rep while trying to unsuccessfully recover the old IP address was to reserve the IP address within Azure and then bind that IP address to the running service. I had a few questions about this.
I tried the following command in a dev instance and it did reserve the IP address that was currently assigned to the server.
New-AzureReservedIP -ReservedIPName new-service-ip-address -Location "North Central US" -ServiceName my-service-in-azure
I am wondering what deployment slot that IP address will now be assigned to. Will that stick with the production slot, or will it flip when I do a prod/stage swap? I ask that because I was given a bit of service deployment code that suggested I needed to change the service configuration on the cloud service so that the reserved IP would be used during deployment.
The solution we were given by the support rep while trying to unsuccessfully recover the old IP address was to reserve the IP address within Azure and then bind that IP address to the running service. I had a few questions about this.
I tried the following command in a dev instance and it did reserve the IP address that was currently assigned to the server.
New-AzureReservedIP -ReservedIPName new-service-ip-address -Location "North Central US" -ServiceName my-service-in-azure
I am wondering what deployment slot that IP address will now be assigned to. Will that stick with the production slot, or will it flip when I do a prod/stage swap? I ask that because I was given a bit of service deployment code that suggested I needed to change the service configuration on the cloud service so that the reserved IP would be used during deployment.
<ServiceConfiguration serviceName="ReservedIPSample" xmlns="http://schemas.microsoft.com/ServiceHosting/2008/10/ServiceConfiguration" osFamily="4" osVersion="*" schemaVersion="2014-01.2.3"><Role name="WebRole1"><Instances count="1" /><ConfigurationSettings><Setting name="Microsoft.WindowsAzure.Plugins.Diagnostics.ConnectionString" value="UseDevelopmentStorage=true" /></ConfigurationSettings></Role><NetworkConfiguration><AddressAssignments><ReservedIPs><ReservedIP name=" new-service-ip-address"/></ReservedIPs></AddressAssignments></NetworkConfiguration></ServiceConfiguration>
So if I deploy this service into the stage slot, with the above changes made to the service configuration file, will the reserved IP address also deploy into staging? And if that happens, what IP address will be applied to the prod deployment slot? Why is the reserved IP mentioned at all in the service config?
