Summary
Every newly created Azure Functions Flex Consumption app in our subscription fails to start its host runtime — including minimal hello-world apps. Apps provisioned earlier in 2025 on the identical shape (same resource group, region, storage account) run normally, and an Elastic Premium (EP1) app created today as a control starts immediately. We are asking Microsoft to establish whether this is (i) a subscription-level provisioning restriction, (ii) a regional Flex Consumption infrastructure issue, or (iii) another platform-side failure — and what diagnostic surface exists when the host produces no telemetry and no storage footprint at all.
- Subscription: c85e8e05-3c96-4a7d-8873-afb85195ba5c
- Tenant: e57dbbb2-9548-4cac-a1ac-43b91dd6942b
- Resource group: tcr-prod
The specimen matrix (all Flex Consumption FC1, all created 2026-11-13)
- ts-worker-func-staging — East US 2 — Python 3.11, managed identity — shared storage — dark (destroyed + recreated: identical)
- ts-worker-flex-probe — East US 2 — Python 3.11, key auth — shared storage — dark
- ts-worker-func-wus2 — West US 2 — Python 3.11, managed identity — fresh dedicated storage — dark
- probe cell A — West US 2 — Node 20 — dark
- probe cell B — Central US — Python 3.11 — dark
- ts-probe-ftp — East US 2 — Python 3.11, HTTP function — fresh storage — dark; host never started; both CLI deploy routes failed at the platform layer and the deployment container stayed empty
Control: ts-worker-func (production worker) — East US 2 — Python 3.11 — shared storage — runs normally (provisioned earlier in 2025)
Control: EP1 probe — East US 2 — Python 3.11, Elastic Premium — fresh storage — starts first try: root 200, functions enumerate, timer fires, telemetry flows
The signature (identical on every new Flex host)
- ARM state "Running"; root URL returns HTTP 503 ("Function host is not running")
- Functions enumeration returns "Encountered an error (InternalServerError) from host runtime"; sync triggers returns ServiceUnavailable
- Zero Application Insights telemetry from the new hosts (connection strings verified against the working app's workspace)
- Zero host storage footprint: no azure-webjobs-hosts container/instance, no host keys; restarts, cold stop/start, and destroy + recreate all reproduce it identically
- Storage diagnostic logging on the shared account shows the new hosts never issue a single host-side storage operation — the only record is the deployment-side package fetch (GetBlob 200). The failure sits above the storage layer.
- Azure Monitor metrics discriminate further: for two specimens, InstanceCount reads 1-2 and MemoryWorkingSet sits at ~459-469 MB for ~11-15 minutes, then stops — compute is assigned and a process starts, then dies in early host initialization, before any observable act. The healthy production host sustains 0.98-1.18 GB. The final read (why the process dies) sits in scale-controller logs customers cannot see.
Deployment correlation IDs (all status Success): staging twin instance 1 01e4dfcb-f115-4cac-b5ca-d4ccc1dea4df · twin instance 2 b47eb98c-1c24-4f5b-ab1d-6ea916429745 · probe 0edcfa65-6bb4-4ef3-a9a5-ce6fb18aa73c · test env graded deploy b91671a0-6fc4-4a41-9712-302aa2e2d0c0 (byte-identical package, sha256-verified).
What we have ruled out
- Package/content: the production workload package imports and builds cleanly (remote build succeeds, deployment records Success); the hello-world package (one timer or one HTTP function, azure-functions only) fails identically. Not a stack fault (Python + Node both dark), not a regional fault (East US 2 / West US 2 / Central US all dark).
- Storage auth form: managed identity and account-key forms both fail; the published azurerm empty-AccountKey poison string is absent.
- RBAC/grants: identity principals hold Storage Blob Data Owner + Key Vault Secrets User, verified by-scope before and after recreate; DB principals registered with verified grant censuses.
- App settings / Key Vault: 27/27 settings verified name- and value-level on the twin; every Key Vault reference resolves.
- Service health: zero ServiceIssue events on the subscription in the window; the app's own detector headlines "Functions runtime is unreachable" over empty measurement tables. Resource Health is not available for Consumption-plan apps.
Question
What prevents a newly provisioned Flex Consumption host in this subscription from starting, when earlier-provisioned Flex apps run and a Premium app on the same shape starts immediately? Is there any customer-visible diagnostic surface for a host that dies in early initialization — no telemetry, no storage footprint, no host keys?
We are re-running a minimal provisioning attempt daily and will update this thread with each result (region/stack labeled) until a new Flex host starts.