Change Public IP of Cloud Service Extended support from Dynamic to static Fails

Question

I just deployed a Cloud Service-Extended support but I need this to use a static IP, as this needs to be whitelisted.
Because I cannot chose a static IP while creating the CloudService-ES, I though that I could change the created Public-IP address from dynamic to static,... while trying to do so it fails with the message:
Failed to save public IP address changes:
Failed to save configuration changes to public IP address 'my-ip'.
Error: Allocation Type and Idle Timeout settings of the public IP address cannot be changed as it is being used by cloud service

it also adds that warning icon in the yellow banner, but no error/warning message is placed there.

What I have tried...
* Stopping the Cloud service, and doing the allocation type change.... same error.
* Deleting the IP from the LoadBalancer front end configuration.... results in error: the ip is currently being used by the cloud service.
* Creating a new IP configuration with a new static IP in the LoadBalancer... results in error, it creates the IP, but it does not allow to add the new IP configuration.

How can I change the IP to static for Cloud Services Extended Support ???

Answer 1

Hello @Adonis Briceno ,

Welcome to Microsoft Q&A Platform. Thank you for reaching out & hope you are doing well.

I understand that you would like to deploy a Cloud service (extended support) with Static IP or change the Public IP of an existing Cloud Service Extended support from Dynamic to static.

Cloud Services (extended support) supports dynamic & static IP allocation methods. Static IP addresses are referenced as reserved IPs in the cscfg file.
Refer : https://learn.microsoft.com/en-us/azure/cloud-services-extended-support/faq#what-ip-allocation-methods-are-supported-on-cloud-services--extended-support--

To deploy a cloud service with Static IP, you need to create a Reserved Public IP first and then associate it with the Cloud Service. Refer : https://learn.microsoft.com/en-us/previous-versions/azure/virtual-network/virtual-networks-reserved-public-ip

If your Service Configuration (.cscfg) contains a reserved IP address, the allocation type for the public IP must be set tp Static.
Refer : https://learn.microsoft.com/en-us/azure/cloud-services-extended-support/deploy-portal

To know more about Azure Cloud Services (extended support) config schema (cscfg File).
Refer : https://learn.microsoft.com/en-us/azure/cloud-services-extended-support/schema-cscfg-file
https://learn.microsoft.com/en-us/azure/cloud-services/schema-cscfg-networkconfiguration#networkconfiguration-element

To associate a reserved IP to a cloud service by using a service configuration file.
Refer : https://learn.microsoft.com/en-us/previous-versions/azure/virtual-network/virtual-networks-reserved-public-ip#associate-a-reserved-ip-to-a-cloud-service-by-using-a-service-configuration-file

Once you have created a Reserved IP and added that reserved IP to your service configuration (.cscfg) file, you can edit your existing cloud service to use the updated cscfg file and change the Public IP allocation method to Static.

Or my recommendation would be to remove the existing cloud service and recreate a new one after creating a reserved IP address and referencing it in the cscfg file as that would be easier to configure.

Kindly let us know if the above helps or you need further assistance on this issue.

----------------------------------------------------------------------------------------------------------------

Please "Accept the answer" if the information helped you. This will help us and others in the community as well.

Answer 2

Hi @GitaraniSharma-MSFT thanks for your response...

Due to your comment, I started doing a lot of tests and hopefully my 2p will help someone else with similar issues.
@GitaraniSharma-MSFT is correct and pointing to the correct doc, BUT also this is something that is easy findable with a bit of googling which I did but still was confused hence my question here.

The confusing bit is that there seems to be missing a bit of details with the answer, and especially with the MS docs.

There is support for "Cloud Services-Extended Support" static IPs using ReservedIPs, but not the Azure resource "Reserved IP", as this is part of the classic deployment model that is being deprecated, and that's the confusing part.

The solution is to create an azure "Public IP Address" first, making this static, modify the configuration files; on the network configuration attributes include this "Public IP Address" (part of the ARM model) with the "ReservedIP" attribute using the name of the "Public IP Address" previously created.

Hopefully this comment will help anyone else in the case there are more devs thinking that this is very confusing.