@Hany Hussein Thank you for your question and we apologize for the delay in getting back to you.
Yes, there is a risk that scaling up from the basic, standard, or premium to the premiumV2 could cause the outbound IP addresses to change.
You can find the set of all possible outbound IP addresses your app can use, regardless of pricing tiers, by looking for the
possibleOutboundIpAddresses property or in the Additional Outbound IP Addresses field in the Properties blade in the Azure portal.
To find the outbound IP addresses currently used by your app in the Azure portal, click Properties in your app's left-hand navigation. They are listed in the Outbound IP Addresses field.
Before you scale up, you can add all of the
possibleOutboundIpAddresses to your code or external resources. For example, if your traffic flows out of your web app into a firewall, you can add all of the IP addresses in
possibleOutboundIpAddresses, then observe what outbound IPs you actually received, then remove any outbound IPs from networking appliances or your code that were not given to you. This will help to avoid downtime.
Your inbound IP address should not change due to scaling so I would not be worried about that.
For more information on IP address changes, please see here.
You mentioned that you are using an A record in your DNS. Do you need an A record? If not, we recommend that you use a CNAME instead of an A record because the inbound IP address can change in certain scenarios so by using a CNAME, you never have to worry about inbound IP address changes impacting the availability of your app.
Please let us know if you have further questions or concerns. We look forward to your reply.