Is assigning a static public IP address only possible on initial deployment of Cloud Service (Extended Support)?

Question

When deploying and updating a Cloud Service (Extended Support) instance from Visual Studio using the "Publish (Extended Support)" wizard, does the assignment of a static public IP address (Basic SKU that was migrated from a classic reserved IP) have to be done on the initial creation/deployment, and cannot be assigned during a later update or by other means such as PowerShell (using Set-AzLoadBalancerFrontendIpConfig)?

Also, within the service configuration file (.cscfg), is the following all that is needed in the Network Configuration to make this make this assignment, or does some load balancer information need to be specified as well?

<NetworkConfiguration>
  <AddressAssignments>
    <ReservedIPs>
      <ReservedIP name="GROUP <ResourceGroupNameOfReservedIP> <reserved-ip-name>"/>
    </ReservedIPs>
  </AddressAssignments>
</NetworkConfiguration>

A similar question is asked here, but it isn't clear what happens if the load balancer information is omitted from the .cscfg file:

https://learn.microsoft.com/en-us/answers/questions/810307/how-to-associate-public-ip-to-classic-load-balance

Does the default load balancer still get created?

Answer 1

Hello CityLightsRBrite

Welcome to Microsoft Q&A Platform, thanks for posting your query here.

Usually deploying below CSCFG config, The LB is always created.

Hope that helps.