An Azure service that provides an event-driven serverless compute platform.
The remaining actionable path is an Azure Functions support case requesting backend Flex Consumption startup and scale-controller investigation; the evidence provided does not establish which platform-side condition is terminating these hosts.
The pattern is consistent with a host startup/platform allocation failure, a documented error class that includes placeholder specialization and container-allocation failures, but 503 Function host not running does not identify the underlying cause by itself.^1^
Customer-visible diagnostics that remain
- Run the startup detector on one current specimen
- Function App → Diagnose and solve problems
- Search for Function App Down or Reporting Errors (Preview).
- Export or capture every startup event, offline-history entry, hosting-plan result, and configuration result.
- Query workspace-level resource logs, not only Application Insights Flex documentation identifies
FunctionAppLogsas the fallback when Application Insights is absent or incomplete, including host/control-plane failures. It also identifiesAzureActivityfor start, stop, list-keys, and SyncTrigger operations.^2^
An empty result is itself useful escalation evidence: record the exact UTC interval during whichunion isfuzzy=true FunctionAppLogs, AzureActivity | where TimeGenerated > ago(24h) | where _ResourceId has "/providers/Microsoft.Web/sites/<APP_NAME>" or ResourceId has "/providers/Microsoft.Web/sites/<APP_NAME>" | project TimeGenerated, Type, OperationName, ActivityStatusValue, ResultType, Message, CorrelationId | order by TimeGenerated ascAutomatic Scaling Instance CountandMemory working setshowed the short-lived process. Those metrics are documented Flex signals for instance allocation and process resource use.^3^ - Do not expect Kudu/SCM logs on Flex Microsoft’s Functions troubleshooting documentation explicitly excludes Flex Consumption from Kudu log availability.^1^ If the host exits before emitting Application Insights or resource logs, there is no documented customer-facing equivalent of the platform’s startup/scale-controller logs.
- Check Flex quota once as a discriminator
- Function App → Diagnose and solve problems
- Search for Flex Consumption Quota
- Select each affected region and export current quota plus historical usage.
Support request scope and payload
Open Support + Troubleshooting → Create a support request from an affected Function App. Classify it under Azure Functions, app down/startup or provisioning, and request escalation to the Flex Consumption platform team.
Include:
- One surviving app resource ID per region, plan
FC1, stack/version, instance memory, and creation timestamp in UTC. - A tight UTC reproduction window showing:
- successful ARM deployment;
- first
503; - SyncTrigger failure;
- instance-count/memory appearance and disappearance.
- Deployment operation IDs and Activity Log
correlationIdvalues. Obtain the latter from Resource group → Activity log → event → JSON →correlationId.^5^ - Detector export, quota output, resource-log query results, metric screenshots/CSV, and deployment command with verbose output.
- The cross-region/cross-stack matrix and the earlier Flex plus current EP1 controls.
- Explicit request: correlate the UTC windows with Flex specialization, worker-startup, container-allocation, deployment-controller, and scale-controller logs, and check subscription-level Flex provisioning enforcement.
Microsoft’s support preparation guidance specifically asks for the deployment method, verbose CLI/PowerShell output, and deployment correlation details.^6^
A backend subscription restriction is possible but not proven. A previous case required Microsoft to remove an automated App Service subscription restriction; however, that case failed plan creation/update, whereas these resources provision successfully and fail later during host initialization.^7^ Ask support to check this condition rather than treating it as the established cause.
The available public material does not identify a matching November 2026 multi-region incident or a customer-side remediation for this exact successful-provisioning/early-host-death signature. Further daily app creation is unlikely to expose the terminating event; retaining one specimen per region with precise timestamps will provide better backend correlation.
References
- Troubleshoot Azure Functions app down or reporting errors
- Create and manage function apps in the Flex Consumption plan (programming-language-typescript)
- Azure Functions monitoring data reference
- Azure Functions Flex Consumption plan hosting | Microsoft Learn
- Get operation correlation ID from Activity Log for Microsoft Discovery
- Resolve issues when creating, deleting, or restoring Azure Functions
- Function App deployment stuck with BadGateway error on Microsoft.Web/serverfarms resource - Microsoft Q&A