Azure Functions Failed to Start: Diagnosis and Fixes

Symptom: what failure looks like

When a Function App fails to start you typically see one of these in the Azure portal or logs:

Microsoft.Azure.WebJobs.Script.WebHost.WebJobsScriptHostService: A host error has occurred during startup operation
System.InvalidOperationException: The host has not been fully configured yet.

-- or --

Function host is not running.

-- or --

Host Status: {
  "id": "...",
  "state": "Error",
  "errors": [
    "Microsoft.Azure.WebJobs.Host: Error indexing method 'Functions.MyFunction'. ..."
  ]
}

In Application Insights, look for exceptions of type FunctionIndexingException, HostInitializationException, or any exception with “startup” in the stack trace in the 5-minute window around when the failure began.

Step 1: Verify required app settings are present

The most common cause of Functions startup failure is a missing app setting that the code expects to be present. Functions throw a startup exception when a required environment variable or Key Vault reference is not resolvable.

# List all app settings for the Function App
az functionapp config appsettings list \
  --resource-group myRG \
  --name myFunctionApp \
  --query "[].{Key:name, Value:value}" \
  --output table

# Add a missing app setting
az functionapp config appsettings set \
  --resource-group myRG \
  --name myFunctionApp \
  --settings MyRequiredSetting=value AnotherSetting=value2

# Add a Key Vault reference instead of a plain value
az functionapp config appsettings set \
  --resource-group myRG \
  --name myFunctionApp \
  --settings "MySecret=@Microsoft.KeyVault(SecretUri=https://mykeyvault.vault.azure.net/secrets/MySecret/)"

Step 2: Verify storage account connectivity

Azure Functions relies on a storage account for its host lock, timer trigger state, and durable functions state. If the function app cannot reach the storage account, the host will not start.

# Check the current AzureWebJobsStorage setting
az functionapp config appsettings list \
  --resource-group myRG \
  --name myFunctionApp \
  --query "[?name=='AzureWebJobsStorage'].value" \
  --output tsv

# Verify the storage account exists and is accessible
STORAGE_ACCOUNT="mystorageacct"
az storage account show \
  --name $STORAGE_ACCOUNT \
  --resource-group myRG \
  --query "{Name:name, Status:statusOfPrimary, NetworkRules:networkRuleSet.defaultAction}"

# Check if the storage account firewall is blocking the function app
# (If default action is Deny, the function app's IP or VNet must be in the allow list)
az storage account network-rule list \
  --account-name $STORAGE_ACCOUNT \
  --resource-group myRG

If the storage account uses a private endpoint or firewall rules, the function app must be VNet-integrated and the storage account’s private endpoint must be in a subnet the function app can reach. For Consumption plan function apps, VNet integration requires the Premium plan or deploying the app in a specific configuration.

Step 3: Validate host.json and function.json

A syntax error or invalid configuration value in host.json will prevent the host from starting. The error is usually logged but can be subtle.

# Download the current host.json from the Function App
az functionapp deployment source config-local-git \
  --name myFunctionApp \
  --resource-group myRG

# Or use the Kudu API to fetch the file
FUNC_APP_NAME="myFunctionApp"
curl -u '$myFunctionApp:DEPLOYMENT_PASSWORD' \
  "https://$FUNC_APP_NAME.scm.azurewebsites.net/api/vfs/site/wwwroot/host.json"

A valid minimal host.json for Functions v4 (.NET isolated) looks like this:

{
  "version": "2.0",
  "logging": {
    "applicationInsights": {
      "samplingSettings": {
        "isEnabled": true,
        "excludedTypes": "Request"
      }
    }
  },
  "extensionBundle": {
    "id": "Microsoft.Azure.Functions.ExtensionBundle",
    "version": "[4.*, 5.0.0)"
  }
}

Common host.json errors: missing version field, invalid JSON (trailing comma, unquoted keys), extension bundle version range that does not resolve to any available bundle, or a logging level set to a value that causes excessive telemetry and throttling.

Step 4: Extension bundle resolution failures

Extension bundles provide triggers (Service Bus, Event Hubs, Cosmos DB) without requiring individual NuGet packages. If the extension bundle cannot be downloaded at startup, functions using those triggers will fail to index.

[2026-03-19 10:15:32] A host error has occurred:
Microsoft.Azure.WebJobs.Script: Failed to download extension bundle
from https://functionscdn.azureedge.net/public/ExtensionBundles/...
System.Net.Http.HttpRequestException: Connection refused

Causes: the function app’s outbound internet is blocked (by NSG, Azure Firewall, or user-defined routes), or the extension bundle CDN endpoint is temporarily unavailable. If outbound internet is blocked by design, use WEBSITE_RUN_FROM_PACKAGE with a pre-built package that includes all extensions compiled in, or configure extension bundle offline using a custom feed URL pointing to an internal mirror.

# Check if the Function App can reach the extension bundle CDN
# (Run from Kudu console or SSH into the function app)
curl -I "https://functionscdn.azureedge.net/public/ExtensionBundles/Microsoft.Azure.Functions.ExtensionBundle/index.json"

# If outbound access is blocked, pre-build extensions and use package deployment
# Set WEBSITE_RUN_FROM_PACKAGE to deploy a zip that includes all binaries
az functionapp config appsettings set \
  --resource-group myRG \
  --name myFunctionApp \
  --settings WEBSITE_RUN_FROM_PACKAGE=1

Step 5: Corrupt or incomplete deployment package

If the function app was deployed with a corrupt zip, a failed deployment, or is missing the function.json files (for out-of-process models), the host will start but find no functions to index, or will fail to load the worker process.

# Trigger a fresh deployment from source control
az functionapp deployment source sync \
  --resource-group myRG \
  --name myFunctionApp

# Restart the function app after a fresh deployment
az functionapp restart \
  --resource-group myRG \
  --name myFunctionApp

# Check deployment logs for errors
az functionapp log deployment show \
  --resource-group myRG \
  --name myFunctionApp

# List the files in the wwwroot via Kudu to verify deployment is complete
curl -u '$myFunctionApp:DEPLOYMENT_PASSWORD' \
  "https://myFunctionApp.scm.azurewebsites.net/api/vfs/site/wwwroot/" \
  --output -

Step 6: Runtime version mismatch

A function app built for Functions v4 runtime will not start on a v1 or v2 runtime host. Check that the FUNCTIONS_EXTENSION_VERSION app setting matches the version your code targets.

# Check current runtime version
az functionapp config appsettings list \
  --resource-group myRG \
  --name myFunctionApp \
  --query "[?name=='FUNCTIONS_EXTENSION_VERSION'].value" \
  --output tsv
# Should return: ~4 for v4 (current stable)

# Set the correct runtime version
az functionapp config appsettings set \
  --resource-group myRG \
  --name myFunctionApp \
  --settings FUNCTIONS_EXTENSION_VERSION=~4

# Check and set the language worker version (e.g., for .NET isolated)
az functionapp config appsettings set \
  --resource-group myRG \
  --name myFunctionApp \
  --settings FUNCTIONS_WORKER_RUNTIME=dotnet-isolated \
             DOTNET_VERSION=8.0