Max apps per app service plan sku - azure recommendations differs

[roofiq]

Hello,

We were trying to follow guideline on this document, that is about max app vs ASP SKU. What we have observed is that in Azure those recommendations are different. It treats SKU as different type of worker, when it comes to it size. Let me show you on example.

We have app service plan on P2V3 sku. Following doc, we should be able to host up to 32 apps. We host 18 apps, of which 16 have slots. So it's 34 in total.

When we go to one of the app service, in diagnose and solve problems here is a warning displayed:

It is recommending to run up to 16 apps, and not 32 as is told in the document.

Either the document is outdated or the Azure diagnostic info. Which guidance should we follow?

Thanks, Rafal

---

Document Details

⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

• ID: 09a9696e-10fd-a74e-4957-0d7ed9ef5a0f
• Version Independent ID: dad3cbd5-b2d0-9cc4-261f-97b95cf811c6
• Content: App Service plans - Azure App Service
• Content Source: articles/app-service/overview-hosting-plans.md
• Service: app-service
• GitHub Login: @cephalin
• Microsoft Alias: cephalin

[YashikaTyagii]

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

[roofiq]

Great @YashikaTyagi-MSFT, do you know which guideline we should take as a reference?

Additionaly, are the performance tests or metric somewhere published based on which those recommendations/limits were made?

[YashikaTyagii]

@roofiq I have assigned the issue to responsible service area engineer who will update accordingly. @BryanTrach-MSFT Kindly provide an update

[BryanTrach-MSFT]

@roofiq Thank you for your question.

Both the documentation and the diagnostic advisor are correct.

The documentation is the MAX number of apps that you can run. This means that all of the apps would be small in size. This maximum number starts to drop though if you start to run web apps that are beefier and need more memory. Ultimately, these maximum guidelines were added as the pricing page states you can have unlimited apps on most tiers. This of course is not physically possible. At the end of the day, these parameters are just guidelines and set expectations as to what you can expect in a best-case scenario. There are too many variables at play when calculating max apps.

In regard to tests or parameters, there are too many variables at play. Your apps are highly unique in the coding, the stack, what OS it's running, how many users are connected, external dependencies, and lots more. There is no basis as to where these numbers are based off of other than best case scenarios.

The diagnostic tool is also correct in that it's reporting your app service plan is feeling resource pressure, likely due to the number of apps in your app service plan.

I hope this helps to provide some clarity. I will be taking this thread as an action item to share with the product group as we never used to make these recommendations due to the number of variables. We don't want these recommendations to cause more frustration than help.

We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.