Multiple Function Apps in a single Consumption Plan?

Question

When I create an Azure Function App via the portal, it's not possible to select whether an existing Consumption Plan is used or a new one gets created.

However, it is possible to do so via ARM Templates.

Azure Function Apps: Organizing the Azure Function Apps under same Consumption Plan discusses this, but it does suggest no implications.

What are the practical differences between having 1-on-1 mapping between Consumption Plans and Function Apps vs. many Apps in a single Plan?

i think scaling might be funky, but since its consumption plan there is no real reason to collocate them, right? consumption plan is free — 4c74356b41
@4c74356b41 Would love to understand the "funky" bit. No financial reason to collocate, but I saw this done just to keep ARM template simpler / reduce the number of resources to manage. — Mikhail Shilkov
Yeah, especially when you have several Function Apps inside a single resource group, having additional resources to manage simply does not make much sense. — kamil-mrzyglod
i think they are scaled in a linked fashion, i'm not sure about that, you probably need to ask David Ebbo, he is pretty active here. also, talking about management is pretty weak argument, you dont really touch those, right — 4c74356b41

Fabio Cavalcante Fabio Cavalcante · Accepted Answer · 2018-10-31T22:57:32

In practice, for apps in a consumption plan, there really is no difference whether they're in a plan created for that app only (trying to avoid the word dedicated here to avoid confusion :) ) or sharing with other apps. The behavior will be the same.

Multiple Function Apps in a single Consumption Plan?

2 Answers