Microsoft has finally enabled the ability to associate a reserved IP to an already created cloud service (VMs). This is great news as we have a few VMs that are externally accessible that were either built prior to this functionality or we just plumb forgot during build.
While logical, Microsoft doesn’t comment that this will cause an outage, and should be done during a normal change window. Sadly, while the IP change takes very little time, DNS updates are typically 20 minute TTL.
Other items that cause small network blips that may require a downtime window (all V1):
- Adding new endpoints to a VM
- Adding subnets to an already created virtual network