The pricing tier 'PremiumMV3' is not allowed in this resource group

Richard D 5 Reputation points
2024-01-24T14:27:41.4766667+00:00

I am looking to upgrade some Windows Service Plans from P1v3 to P1mv3, or create new service plans on this tier, while keeping them on the same resource group and region as our entire environment

However, I am receiving an error through UI/Portal and API/Terraform:
performing CreateOrUpdate: unexpected status 409 with response: {"Code":"Conflict","Message":"The pricing tier 'PremiumMV3' is not allowed in this resource group. Use this link to learn more: https://aka.ms/app-service-plan-scale-not-allowed

I have observed the following scenarios while creating the Service Plan:

  • New Resource Group / Same Region (USEAST2) / Windows = Success
  • Same Resource Group / Same Region (USEAST2) / Linux = Success
  • Same Resource Group / Same Region (USEAST2) / Windows = Fail (My Goal) - Yellow
  • Same Resource Group / Another Region (USEAST) / Windows = *Success - Green

These are the Service Plans I have on this resource group:*
User's image

Any suggestion or way that I can create or upgrade this service plan?

Azure App Service
Azure App Service
Azure App Service is a service used to create and deploy scalable, mission-critical web apps.
6,907 questions
{count} vote

1 answer

Sort by: Most helpful
  1. TP 76,601 Reputation points
    2024-01-24T14:55:32.9066667+00:00

    Hi Richard,

    Unfortunately you cannot switch to Pxmv3 Windows SKU in your same resource group and region combination. The reason is, the underlying webspace (aka Deployment Unit) doesn't support it. If you want them all in same resource group and region you would need to redeploy all to a new resource group.

    Scale up from an unsupported resource group and region combination

    https://learn.microsoft.com/en-us/azure/app-service/app-service-configure-premium-tier#scale-up-from-an-unsupported-resource-group-and-region-combination

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

    Thanks.

    -TP

    0 comments No comments