Upgrade from S2 to P2V2 - Downtime IP change

[benjennings]

Hello all,

We have used S1 and then upgraded to S2 easily, no change of platform etc, however we now need to move from S2 to a P2V2 plan and the message box says that the IP address will change. This will then have to be changed on the 60 or websites we host via their DNS.

As and when this process is started, does the IP changing immediately kill the websites hosted on our azure, or is there some lead time before propogation. ie if we click confirm to upgrade and then change the IP address on all the hosted websites within say 12 hours, would the websites see no dow-time, or are they down "offline" until the IP address change is complete?

Many thanks

Ben

[#2]

Hi Ben,

This is defiantly not my subject of expertise, so take my comments with a tablespoon of salt.

When upgrading from S2 to P2V2 in Azure, the IP address of your instance will indeed change. This will not necessarily kill your websites immediately, but there may be some lead time before propagation occurs. It is difficult to predict exactly how long it will take for the IP address change to propagate, as this can depend on a variety of factors such as DNS caching by ISPs and other factors.

However, it is generally recommended to plan for some downtime during an IP address change. You may want to consider setting a short TTL on your DNS records ahead of time, which can help to minimize the propagation delay. Additionally, it may be helpful to communicate the planned downtime to your users in advance, to minimize any potential impact.

I hope this helps!, might be something worth talking to a Microsoft SME about.

Kind regards,

Luke Madden

[#3]

When you are upgrading an App Service plan in Azure and changing the service tier or plan size, it can result in a new IP address being assigned to the web app. The IP address change may result in a temporary downtime, which can last up to several minutes or longer depending on how long it takes for the DNS changes to propagate.

In terms of the timeline for the IP address change, it can vary depending on the DNS propagation time for the domain names of the websites hosted on your Azure environment. Typically, DNS propagation time can take anywhere from several minutes to 24 hours or more. During this time, some users may experience intermittent connectivity issues when trying to access the websites.

To minimize the impact of the IP address change, it is recommended to prepare for the change ahead of time by notifying any relevant stakeholders or customers, updating DNS records as soon as possible, and performing the upgrade during a low-traffic period. Additionally, it may be helpful to set up a temporary redirect from the old IP address to the new IP address to ensure that users can still access the website during the transition period.

Hope that answers your query.

Best Regards
ShankerH