SkuCode I4v2 is invalid. (Azure App Service)

[zboldyga]

We've already opened a support ticket for this item, but I'm raising here as well in case anyone has insight. This is an urgent issue for us because an app is redlining memory at the I3v2 instance, causing crashes. Leveraging the I4v2 or higher instances would be an impactful option, but it doesn't seem to work.

The following command is failing for us, several people in our team have tried across multiple resource groups, different app service plans. We've tried this via the az CLI (latest version 2.49.0), as well as the terraform azurerm provider (latest version 3.59.0). We are in the US South Central region. This has only been tried on Windows instances.

az appservice plan update --name XYZ --sku I4v2 -g ABC

All return this error message: SkuCode 'I4V2' is invalid.

Note that we are always passing in "I4v2", but the error message comes back in all caps: "I4V2". This is consistent across both of those tools... This happens for all of the new SKUs (I4v2, I5v2, I6v2).

We were not able to try this action in the Azure Portal (UI) because only I1v2, I2v2, I3v2 are available options in the UI. I figure the UI may be lagging in implementation, since this feature was initially released in December 22'.

I see the code in both of these tools where the update was added, both seem valid:

• https://github.com/Azure/azure-cli/pull/24877
• https://github.com/hashicorp/terraform-provider-azurerm/pull/21371/files

Also, listing the available regions:

az appservice list-locations --sku I4v2
[
  {
    "name": "East US"
  },
  {
    "name": "North Europe"
  },
  {
    "name": "West Europe"
  },
  {
    "name": "Southeast Asia"
  },
  {
    "name": "East Asia"
  },
  {
    "name": "West US"
  },
  {
    "name": "Japan West"
  },
  {
    "name": "Japan East"
  },
  {
    "name": "East US 2"
  },
  {
    "name": "North Central US"
  },
  {
    "name": "South Central US"
  },
  {
    "name": "Brazil South"
  },
  {
    "name": "Australia East"
  },
  {
    "name": "Australia Southeast"
  },
  {
    "name": "Central US"
  },
  {
    "name": "Central India"
  },
  {
    "name": "West India"
  },
  {
    "name": "South India"
  },
  {
    "name": "Canada Central"
  },
  {
    "name": "Canada East"
  },
  {
    "name": "West Central US"
  },
  {
    "name": "West US 2"
  },
  {
    "name": "UK West"
  },
  {
    "name": "UK South"
  },
  {
    "name": "Korea South"
  },
  {
    "name": "Korea Central"
  },
  {
    "name": "France Central"
  },
  {
    "name": "Australia Central"
  },
  {
    "name": "South Africa North"
  },
  {
    "name": "Switzerland North"
  },
  {
    "name": "Germany West Central"
  },
  {
    "name": "UAE North"
  },
  {
    "name": "Norway East"
  },
  {
    "name": "West US 3"
  },
  {
    "name": "Sweden Central"
  },
  {
    "name": "Qatar Central"
  },
  {
    "name": "Poland Central"
  }
]

This leads me to believe there is some issue with the azure resource manager API.

Thoughts?

[RamanathanChinnappan-MSFT]

@zboldyga

Thanks for your feedback! We will investigate and update as appropriate.

[RamanathanChinnappan-MSFT]

@zboldyga

We are going to close this thread. if there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation.