Skip to content

03 - Configuration (Consumption)

Configure your deployed Consumption (Y1) function app using classic siteConfig.appSettings semantics and CLI app settings commands.

Prerequisites

Tool Version Purpose
Azure CLI 2.61+ Manage function app settings
Deployed Function App Y1 Target app from tutorial 02
Storage account Standard_LRS Runtime state and triggers

What You'll Build

You will configure core app settings for a Linux Consumption Function App, including storage and observability-related values, and validate the app configuration state.

Infrastructure Context

Plan: Consumption (Y1) | Network: Public internet only | VNet: ❌ Not supported

Consumption has no VNet integration or private endpoint support. All traffic flows over the public internet. Storage uses connection string authentication.

flowchart TD
    INET[Internet] -->|HTTPS| FA[Function App\nConsumption Y1\nLinux Python 3.11]

    FA -->|System-Assigned MI| ENTRA[Microsoft Entra ID]
    FA -->|"AzureWebJobsStorage__accountName\n+ connection string"| ST[Storage Account\npublic access]
    FA --> AI[Application Insights]

    subgraph STORAGE[Storage Services]
        ST --- FS[Azure Files\ncontent share]
    end

    NO_VNET["⚠️ No VNet integration\nNo private endpoints"] -. limitation .- FA

    style FA fill:#0078d4,color:#fff
    style NO_VNET fill:#FFF3E0,stroke:#FF9800
    style STORAGE fill:#FFF3E0
flowchart LR
    A[Read current app settings] --> B[Set runtime and custom settings]
    B --> C[Optional identity-based host storage]
    C --> D[Validate effective configuration]

Steps

Step 1 - Set variables

export RG="rg-func-consumption-demo"
export APP_NAME="func-consumption-demo-001"
export STORAGE_NAME="stconsumptiondemo001"
export LOCATION="koreacentral"

Step 2 - Read current app settings

az functionapp config appsettings list \
  --name "$APP_NAME" \
  --resource-group "$RG"

Step 3 - Set required and custom app settings

az functionapp config appsettings set \
  --name "$APP_NAME" \
  --resource-group "$RG" \
  --settings \
    "FUNCTIONS_WORKER_RUNTIME=python" \
    "AzureWebJobsStorage=DefaultEndpointsProtocol=https;AccountName=$STORAGE_NAME;AccountKey=<masked-key>;EndpointSuffix=core.windows.net" \
    "APP_ENV=production" \
    "LOG_LEVEL=Information"

For Consumption, app settings are handled as classic app settings (backed by siteConfig.appSettings), not the Flex-specific configuration model.

Step 4 - Optional: identity-based host storage pattern

Instead of a connection string, you can configure identity-based host storage values (both models are valid on Consumption). On Linux Consumption, content share settings are still required and continue to use a shared-key-backed WEBSITE_CONTENTAZUREFILECONNECTIONSTRING with WEBSITE_CONTENTSHARE.

az functionapp config appsettings set \
  --name "$APP_NAME" \
  --resource-group "$RG" \
  --settings \
    "AzureWebJobsStorage__accountName=$STORAGE_NAME" \
    "AzureWebJobsStorage__credential=managedidentity"

Identity-based storage requires Managed Identity and RBAC

Before using identity-based host storage, you must:

  1. Enable system-assigned managed identity on the Function App: az functionapp identity assign --name "$APP_NAME" --resource-group "$RG"
  2. Grant required data-plane roles on the storage account scope: Storage Blob Data Owner, Storage Queue Data Contributor, and Storage Table Data Contributor.
  3. Keep content share settings configured (WEBSITE_CONTENTAZUREFILECONNECTIONSTRING and WEBSITE_CONTENTSHARE) for Linux Consumption.
  4. Set both AzureWebJobsStorage__accountName and AzureWebJobsStorage__credential=managedidentity app settings.

Step 5 - Confirm runtime limits relevant to configuration

  • Consumption defaults to a 5-minute timeout and supports up to 10 minutes.
  • Memory is fixed at 1.5 GB per instance.
  • Scaling is automatic and event-driven on Consumption.
  • Maximum scale-out is up to 100 instances on Linux Consumption (up to 200 on Windows Consumption).
  • No always-ready instances are available; cold start is typically more noticeable than Premium.

Verification

Verify the updated settings are applied:

az functionapp config appsettings list \
  --name "$APP_NAME" \
  --resource-group "$RG" \
  --output table

App settings update excerpt (values are hidden by the platform for security): 

[
  {
    "name": "FUNCTIONS_WORKER_RUNTIME",
    "slotSetting": false,
    "value": null
  },
  {
    "name": "AzureWebJobsStorage",
    "slotSetting": false,
    "value": null
  },
  {
    "name": "APP_ENV",
    "slotSetting": false,
    "value": null
  }
]

Verify the app is running:

az functionapp show \
  --name "$APP_NAME" \
  --resource-group "$RG" \
  --query "{id:id,kind:kind,state:state}" \
  --output json

App details excerpt:

Next Steps

Now enable operational visibility with logs and monitoring.

Next: 04 - Logging and Monitoring

See Also

Sources