P1mV3 not recognized as a premium App service plan.

Björn Hasselberg 66

I have created a app service plan with P1mV3 computing. The plan is not recognized as a premium plan. Anyone having similar issues?

P1mV3 3.jpg

P1mV3 2.jpg

P1mV3 1.jpg

KR,
Bjørn Hasselberg

VenkateshDodda-MSFT 19,616 Reputation points Microsoft Employee

2023-04-27T06:42:07.7333333+00:00

@Björn Hasselberg Thank you for reaching out to Microsoft Q&A, apologize for any inconvenience caused on this.

To test this behavior, I have created a New App Service with app service plan sku as P1V3 with 1 instance and I dont see the same behavior that you have added in the screenshot while selecting the certificates widget and application settings.

Looks like the behavior that you are facing might be transient. I would suggest you try signing out and signing back to portal from the same browser post clearing the cache or logging to portal from different browser.

Looking forward for your response.
Björn Hasselberg 66 Reputation points

2023-04-27T08:08:00.0966667+00:00

Have tried with Edge and Chrome + incognito window, no difference.
Björn Hasselberg 66 Reputation points

2023-04-27T08:09:01.66+00:00

P1V3 works fine (have that as well), it is P1mV3 that's not working.
VenkateshDodda-MSFT 19,616 Reputation points Microsoft Employee

2023-04-27T09:40:54.8333333+00:00

@Björn Hasselberg Thanks for the response. Could you please help us in sharing more information like App Service plan name (which you are facing issue), last four digits of your subscription id, Issue timestamp (UTC) to check and assist you further on this.
Björn Hasselberg 66 Reputation points

2023-04-27T11:35:01.21+00:00

@VenkateshDodda-MSFT

Subscription ID, last four digits: 1530
App Service Plan: Pro4uLXplan
Creation: Wed Apr 26 2023 00:48:29 GMT+0200 (Central European Summer Time)
VenkateshDodda-MSFT 19,616 Reputation points Microsoft Employee

2023-04-28T04:44:36.5266667+00:00

@Björn Hasselberg Thanks for sharing the requested information will check and assist you further accordingly.
Björn Hasselberg 66 Reputation points

2023-04-29T06:26:08.5366667+00:00

@VenkateshDodda-MSFT

Did some further investigation today by creating a new testplan, then getting this error message:
{"code":"DeploymentFailed","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-deployment-operations for usage details.","details":[{"message":"Requested features 'Linux Worker, MV3 Series Worker' not available in resource group Pro4uApps. Please try using a different resource group or create a new one."}]}

I realize that I did get this message the first time and created the plan in a new resource group.
Then I wanted to move one app service to the new plan, but could not do it because the plans where in different resource groups. I know realize that this might be of the premium features used, that did not get recognized in the new plan.
I then moved the new plan to the old resource group, and this was possible and did not create en error.
But I guess the error message from creation regarding the "MV3 Series Worker" must still have applied and created the issues at hand.

New testplan
This time I created a new web service in my new testplan. After creation I did a restore on a web app from a P1V3 plan, but without moving the plan to the old resource group. I got the same error situation again, where the P1mV3 plan is not recognized as a premium plan when trying to configure the new web service.
The apps created in the P1mV3 plans are all displayed as Standard in the App Service overview i the Azure Portal.

P1mV3 4.jpg
VenkateshDodda-MSFT 19,616 Reputation points Microsoft Employee

2023-05-02T05:12:49.9033333+00:00

@Björn Hasselberg Thanks for your patience.

I have checked with App service engineering team on this and sharing the below,

Upon investigating deeper on this issue, Our engineering team has identified a bug and they are working on fixing it we don't have any ETA at the moment.

Alternative, workaround at the moment is to create the app service plan P1mV3 using either through Az CLI cmdlets or through the Azure management REST API.

Feel free to reach out to me if you have any further questions on this.
VenkateshDodda-MSFT 19,616 Reputation points Microsoft Employee

2023-05-03T04:24:10.52+00:00

Hello @Björn Hasselberg ,

Following up to see if you have a chance to check my previous response and helped. Do let us know if you have any further questions on this.
Björn Hasselberg 66 Reputation points

2023-05-03T18:02:41.83+00:00

@VenkateshDodda-MSFT

I will try it out shortly and will provide feedback here.

KR,

Björn H
Björn Hasselberg 66 Reputation points

2023-05-03T19:30:26.92+00:00

@VenkateshDodda-MSFT
Workaround did not help.
First I created the plan using CLI.
Next I created two web apps in the plan, one through CLI and one through Portal GUI. Both turned out as Standard, not Premium.
P1mV3 5.jpg

KR,

Bjørn H
VenkateshDodda-MSFT 19,616 Reputation points Microsoft Employee

2023-05-04T10:24:42.9933333+00:00

@Björn Hasselberg Thanks for checking and follow-up response.

I wish to engage with you offline for a much closer look and provide a quick and specialized assistance, please send an email with subject line “Attn:Venkatesh |thread title” to AzCommunity@microsoft.com referencing this thread with your Azure subscription ID and WebApp details, I will follow-up with you.
Björn Hasselberg 66 Reputation points

2023-05-05T06:28:06.97+00:00

Email sent.
VenkateshDodda-MSFT 19,616 Reputation points Microsoft Employee

2023-05-05T06:36:47.4766667+00:00

@Björn Hasselberg Thank you for sharing the requested information will check and update you accordingly.
Thomas Odell Balkeståhl 1 Reputation point

2023-05-09T15:03:47.2466667+00:00

@björn
In what region did you try this? We have waited some time now for the new SKU's (PXmv3 & P0v3) to show up and I have only seen them in Sweden Central so far. In WE we can select them and they can be seen, but creating them fails. According to the latest news from MS they are beeing rolled out globally and should be rolled out before the end of H1
Björn Hasselberg 66 Reputation points

2023-05-09T15:52:37.3+00:00

I have just received positive information from MSFT and confirmed that it is now working in North Europe.
I can scale plan from P1mV3 to F1 and back without problems with a "F1 compatible" web app attached, which I tried just to see if it was possible after the correction.
VenkateshDodda-MSFT 19,616 Reputation points Microsoft Employee

2023-05-10T04:17:29.88+00:00

@Björn Hasselberg Thanks for confirming, I have summarized our discussion and update as an answer.

Please accept as Yes if the answer provided is useful, so that you can help others in the community looking for remediation for similar issues.

Accepted answer

VenkateshDodda-MSFT 19,616 Reputation points Microsoft Employee

2023-05-10T04:15:46.0166667+00:00

@Björn Hasselberg Thanks for your patience on this.

Upon investigating deeper on this issue, Our engineering team has identified a bug and the fix has been deployed as well.

Thanks for revalidating and confirming that now you are able to create the App service plan of p1mv3 sku and able to see it as premium from App service plan blade in the portal.

Feel free to reach back to me if you have any questions on this.
Please sign in to rate this answer.

1 person found this answer helpful.

0 comments No comments
Sign in to comment

1 additional answer

TP 80,981 Reputation points

2023-04-29T07:31:27.5033333+00:00

Hi,

I tested and am seeing the same thing. Tried in North Europe and East US, same results. Any of the linux PXmv3 SKUs show up as Standard.

If I switched the plan to one of the other Premium SKUs, for example, P1V2 or P1V3, it changed over to Premium. When I switched back to one of the PXmv3 SKUs, it changed back to Standard. Interestingly, P0V3 shows up as Standard.

I recommend you open a new support request via the Azure portal for this issue. Meantime you will need to use a different SKU other than one of the PXmv3 SKUs if you want Premium.

If the above is helpful please click Accept Answer.

Thanks.

-TP
Please sign in to rate this answer.
Björn Hasselberg 66 Reputation points

2023-04-29T09:09:38.0533333+00:00

@TP
Thanks for the input and for confirming the issue.
If I wanted to use another SKU I would do so, there is a reason why I want to go to the mV3 series.
Although your answer is correct, it doesn't change my situation. As stated I already have V3 plans.
I will not mark this as an accepted answer until I hear back from MSFT, don't want them to think this is resolved.
KR,
Bjørn H

TP 80,981 Reputation points

2023-05-04T07:30:04.26+00:00

@Björn Hasselberg I just tested by creating new app service plan using the REST api, both Linux and Windows P1mv3, and they were still created as Standard. They don't even seem to be standard since you even can't create an SSL binding which only requires Basic or higher.

My conclusion at this point is the PremiumMV3 (P1mv3 is part of this tier) skus are broken.

As I mentioned above, I recommend you create a new support request via the portal. Yes, I know VenkateshDodda-MSFT has been in touch with engineering, but I think it is important to have an official case where you document that this is blocking you.

TP 80,981 Reputation points

2023-05-04T08:20:13.09+00:00

@Björn Hasselberg Thinking about it a bit more, perhaps the "full workaround description" is that you need to use CLI/PowerShell/REST API for all configuration that is blocked by the portal and it will work. For example, you create the app service plan using cli or REST api, create SSL binding using cli/rest, etc.

Untested.

In other words, the actual created plan is PremiumMV3, but the portal doesn't properly recognize it as a Premium variant, so that is why the portal blocks you and says you need to upgrade. In my tests using the REST api the return JSON does show it is PremiumMV3 P1mv3.

I think it may be worth the trouble so that you can use P1mv3. You just need to use command line to configure certain things.

Björn Hasselberg 66 Reputation points

2023-05-09T15:53:42.86+00:00

As stated above, a fix have now been deployed by MSFT :)
Sign in to comment

Share via

P1mV3 not recognized as a premium App service plan.

1 additional answer