| description | page_type | products | urlFragment | languages | ||||
|---|---|---|---|---|---|---|---|---|
This template provisions a function app on a Windows Consumption plan, which is a dynamic hosting plan. The app runs on demand and you're billed per execution, with no standing resource committment. |
sample |
|
function-app-windows-consumption |
|
This sample Azure Resource Manager template deploys an Azure Function App on Windows Consumption plan and required resource including ZipDeploy extension to mount zip package for deployment.
This template is for Azure Function app hosted on Windows Consumption plan only.
The Azure Function app provisioned in this sample uses an Azure Functions Consumption plan.
- Microsoft.Web/serverfarms: The Azure Functions Consumption plan (a.k.a. Dynamic plan)
The Function App uses the AzureWebJobsStorage and WEBSITE_CONTENTAZUREFILECONNECTIONSTRING app settings to connect to a Storage Account.
- Microsoft.Web/sites: The function app instance.
The Zip Deploy extension is added along with recommended app setting WEBSITE_RUN_FROM_PACKAGE=1 to mount the zip package for deployment. This is the recommended path for deployment, except for Linux Consumption Plan
- Microsoft.Web/sites/extensions: The ZipDeploy extension.
The Storage account that the Function uses for operation and for file contents.
- Microsoft.Storage/storageAccounts: Azure Functions requires a storage account for the function app instance.
Application Insights is used to provide monitor the Azure Function.
- Microsoft.Insights/components: The Application Insights instance used by the Azure Function for monitoring.
Tags: Microsoft.Storage/storageAccounts, microsoft.insights/components, Microsoft.Web/serverfarms, Microsoft.Web/sites, Microsoft.Web/sites/extensions