An Azure platform as a service offer that is used to deploy web and cloud applications.
Hello Ian Alejandro Corral Marin
Preserving the same public IP is potentially possible.
Answering your questions
1. Will the IP survive Cloud Service deletion?
Cloud Services (extended support) uses a separately represented public IP and a platform-managed load balancer.
In a similar Microsoft Q&A case, deleting the Cloud Service cleans up its load balancer and that the public IP can be deleted separately afterward. This suggests the IP resource can remain, but it is not a guarantee for every deployment or deletion method. In particular, do not delete the containing resource group.
2. Can the IP be upgraded and moved to another subscription?
Yes, provided the public IP survives as a standalone, unassociated resource and meets the upgrade requirements.
Steps:
- Upgrading a detached static Basic IP to Standard preserves its address.
- A detached Standard public IP can be moved across subscriptions.
- Both subscriptions must belong to the same Microsoft Entra tenant.
The intended sequence would be:
- Safely disassociate and preserve the original IP.
- Verify that the exact IP address remains allocated.
- Upgrade Basic → Standard.
- Move the detached Standard public IP to the destination subscription.
- Associate it with the Windows VM's NIC and configure the NSG to permit your TCP service.
References:
3. Can the IP be detached without deleting the Cloud Service?
This operation replaces a Cloud Service's reserved public IP with another standalone public IP.
Cloud Services FAQ states that reserved IPs cannot normally be changed during deployment updates.
Disassociate Cloud Service Reserved Public IP
4. Will a CanNotDelete lock protect the IP?
A CanNotDelete lock prevents direct deletion of the protected resource, but it is not a documented guarantee that Cloud Service deletion will preserve the associated IP.
If Cloud Service cleanup requires deleting that IP, the lock could cause the deletion operation to fail.
I would not rely on a resource lock as the migration mechanism.
Before changing anything, inspect the current IP:
az network public-ip show \
--resource-group "<resource-group>" \
--name "<public-ip-name>" \
--query "{ip:ipAddress,sku:sku.name,allocation:publicIPAllocationMethod,association:ipConfiguration.id}" \
-o json
Obtain confirmation of the detachment procedure first, then perform the upgrade and subscription move during a planned maintenance window. Do not release or recreate the existing IP the original numeric address cannot be recovered reliably once its resource is deleted.