Share via

Premium v3 P1mv3 vs Premium v3 P1v3 plans

Vladimir Stanojevic 20 Reputation points
2023-12-18T12:06:05.45+00:00

I am currently encountering two distinct scenarios related to Azure service plans:

  1. A service plan, established two years ago, lacks the option to transition to one of the Premium v3 PXmv3 plans.
  2. A service plan initiated three months ago does provide the option to switch to a Premium v3 PXmv3 plan.

I would like to understand if this discrepancy in behavior is expected. Additionally, if I wish to migrate all resources from the service plan created two years ago to a Premium v3 PXmv3 plan, would the recommended approach be to create a new service plan and perform the migration, or is there a more streamlined process available?

Thank you for your assistance.

Azure App Service
Azure App Service

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

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. VenkateshDodda-MSFT 25,251 Reputation points Microsoft Employee Moderator
    2023-12-19T05:44:12.7866667+00:00

    Vladimir Stanojevic Thank you for posting your query in Microsoft Q&A forum. Apologize for any inconvenience caused on this.

    As TP mentioned If you are unable to scale-up the app service plan from premium (p1v3) to (p1mv3) this might be caused either

    • The existing app service plan underlying webspace. By default, Azure deploys each new App Service plan into a deployment unit, internally called a webspace. Each region can have many webspace's is not supported.
    • The region in which existing plan does have support to create this p1mv3 type app service plan as mentioned in this documentation.

    User's image

    You can use the below cmdlet to check which regions does the p1mv3 plans are supported and try recreating a new app service plan in it. 

    az appservice list-locations --sku P1mv3

    Feel free to reach back to me if you have any further questions on this.

  2. TP 155.2K Reputation points Volunteer Moderator
    2023-12-18T13:19:47.2233333+00:00

    Hi Vladimir,

    Yes, unfortunately if the underlying webspace that your plan is in doesn't support it then there is no choice. You need to re-create the web app in a plan that supports the Pxmv3. For example, create a new App Service Plan in new resource group set to P1mv3 and then re-create web app (with different default domain) in that plan with same configuration and restore files to it.

    Please click Accept Answer and upvote if the above was helpful.

    Thanks.

    -TP

Your answer

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