Azure-docs: Consider noting that Runtime Scale Monitoring is only available with Elastic Premium plans

[oising]

In order to enable Runtime Scale Monitoring, the plan has to be an Elastic Premium functions plan, specifically. This should be stated on the page. The option doesn't appear for any other sort of Premium plan (of which there are several.)

---

Document Details

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

• ID: bc0b34e2-0eb8-fe89-300c-67e6c212ed31
• Version Independent ID: 5d01d8ce-f835-c88c-801c-1d569f24fd9f
• Content: Azure Functions networking options
• Content Source: articles/azure-functions/functions-networking-options.md
• Service: azure-functions
• GitHub Login: @jeffhollan
• Microsoft Alias: jehollan

[HarithaMaddi-MSFT]

@oising - Thanks for your valuable inputs. We are looking into it and will update you shortly.

[PramodValavala-MSFT]

@oising Elastic Premium Plans are the plans referred to as Premium Plans as available when creating a function app. Could you confirm what are the other premium plans you mention? Perhaps you are referring to App Service Plans?

[oising]

Yes, I'm talking about app service plans -- the use case is this: I create a premium app service plan, integrate a vnet and add a few web apps. Later, I add a function to that same plan, and try to configure a non-http trigger. I can't find the setting for runtime scale monitoring [because it's not an _elastic_ plan, but it is _premium_]. I pull out half of my hair in frustration. I create another separate function to test, and this time I create the plan from the function, and end up with an EP plan. Now I find the setting. I pull out the other half of my hair in confusion. Eventually, while looking for a suitable wig on Amazon, I figure out that when you say "premium plan" you actually mean "elastic premium plan."

Please save other people from going bald. I appreciate your responsiveness. Thank you :)

[PramodValavala-MSFT]

@oising Apologies for not getting back on this. We have assigned this issue to the content author as this is a convention used across the docs.

[oising]

@PramodValavala-MSFT Thanks Pramod -- appreciate the update.