If i script replacing an auto-named kubernetes service loadBalancerIP on an azure AKS cluster it always sits at "attempting to allocate IP" because the new one has been created, but the old one is still consuming the IP so it never completes

You have the option to mark the service as

deleteBeforeReplace: true

. Would that meet you needs?

yea i found that thanks - i ended up turning off autonaming for those resources since i couldn't think of a reason it would be beneficial