How to setup IP bound SSL after upgrading app service plan from S3 to P2V2 with IP bound SSL

RichardAD 1 Reputation point
2020-08-26T05:32:20.763+00:00

We have production web app that we can only afford very minimal down time (e.g. 60 minutes).
We need to upgrade the app service plan from S3 to P2V2 which forces a change of IP address.
We have a custom domain and an IP bound SSL certificate.
When we try to do the upgrade we get the following error
20407-annotation-2020-08-26-151854.png

Having not done this before, we need to know if setting up the IP bound SSL is as simple as choosing the existing certificate after the plan change is done and the new IP address is assigned or are there any more steps that could break and leave us without an active site?

Azure App Service
Azure App Service
Azure App Service is a service used to create and deploy scalable, mission-critical web apps.
7,679 questions

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Krish G 2,331 Reputation points
    2020-08-26T15:33:38.317+00:00

    @RichardAD , both of the below options are fine considering you have sufficient downtime allowance (60 minutes). However, I strongly recommend to do a same scenario simulation in your NON-PRODUCTION environment first before touching PRODUCTION to have the confidence when you actually do it in production.

    Option 1: Disable SSL binding -> Site not accessible from this moment -> Upgrade to new plan -> Enable binding with new IP and same certificate -> Site up

    Option 2: Switch to SNI based SSL binding -> Site not accessible momentarily and up again -> Upgrade to new plan. (And you are staying with SNI based binding from this moment)

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.