CODEWITHSUNDEEP
azureazure-cloud-services
ewitkows
ewitkows

Reputation: 3618

Add Reserved IP to Azure Cloud Service

I have a cloud service in Azure that I want to give a reserved IP to. I basically followed the steps here: https://azure.microsoft.com/en-us/documentation/articles/virtual-networks-reserved-public-ip/

I performed the "New-AzureReservedIP" cmd, giving an ip name of "MyIPName" and a location of the East US - the same location of my current cloud service.

In my service config, I used the following:

    <NetworkConfiguration>
        <AddressAssignments>
        <ReservedIPs>
        <ReservedIP name="MyIPName"/>
      </ReservedIPs>
    </AddressAssignments>
  </NetworkConfiguration>

When I attempted to deploy my cloud service, I got the error "The Reserved IP MyIPName does not exist. Although I just created it, its not recognizing my aptly named reserved ip address. Thoughts?

Upvotes: 3

Views: 1103

Answers (2)

Alistair
Alistair

Reputation: 306

I just had the same problem after creating a Reserved IP through the Azure Portal. The answer from June 2015 did not work for me. For me the solution was to use Powershell to connect to the Azure subscription and then get the FULL name of the Reserved IP and use it in the service config. The full name of my Reserved IP was in the format "Group {Resource Name} {Reserved IP Name}".

Publishing from Visual Studio 2013 then worked.

To confirm that this wasn't a timing issue I then tried again using only the {Reserved IP Name} value and found that it still did not work (ie received Error: The Reserved IP xyz does not exist.). Hence it would seem that the full Reserved IP name must be used when it has been created from the Azure Portal and then publishing from Visual Studio.

Note: I am using a Classic app service.

Upvotes: 6

ewitkows
ewitkows

Reputation: 3618

This is working now. 2 things happened on my end.

  1. Father Time eventually passed, I think it took some time from the Azure side to recognize that this Reserved IP was created and that my subscription had a reserved IP named MyIPName
  2. When I published my cloud service, I used Visual Studio 2013, and in the publish settings I chose "Advanced Settings", checked the "Deployment update" checkbox, chose Settings next to that checkbox, and chose "If deployment can't be updated, do a full deployment". That allowed the VM instances to be recreated with the Reserved IP Address applied.

Upvotes: 1

Related Questions