Active subscription not recognised when creating a Flex Consumption Function App Hello Azure Support,

Francisca Mensah 0 Reputation points
2026-11-06T16:45:57.57+00:00

I’m unable to create a Node.js 22 Flex Consumption Function App in West US 3. Creation of its hosting plan fails with:

Cannot find Subscription with name 6e24b43d-a57c-46d6-b88f-ea154e345c72.

I have confirmed that the subscription is Active, my account has the Owner role, and Microsoft.Web is Registered. The storage, managed identity, and monitoring resources were created successfully.

Deployment details:

  • Subscription: Subscription for DeskPilot
  • Subscription ID: 6e24b43d-a57c-46d6-b88f-ea154e345c72
  • Resource group: rg-deskpilot-dev
  • Failed resource: ASP-rgdeskpilotdev-9141 (Microsoft.Web/serverfarms)
  • Deployment: Microsoft.Web-FunctionApp-Portal-7ee631e2-a4f2
  • Error code: NotFound
  • Correlation ID: 59f5e15a-0786-4821-9fca-3815d7323f8a

Please investigate why Microsoft.Web cannot recognise this active subscription and advise how to complete the deployment.

Thank you.

Azure Functions
Azure Functions

An Azure service that provides an event-driven serverless compute platform.

0 comments No comments

1 answer

Sort by: Newest
  1. AI answer

    2026-11-06T16:47:10.11+00:00

    Create the app through the documented Flex Consumption CLI flow after confirming that West US 3 is currently returned as supported; if the same NotFound occurs at Microsoft.Web/serverfarms, open an Azure support request because the remaining failure is at the subscription/provider control plane.

    1. Validate the region and required Flex provider

    Flex Consumption availability is region-dependent. Also, Microsoft.App must be registered even when virtual-network integration is not currently enabled, because the portal and CLI enforce that prerequisite during app creation.^1^

    Run this in Azure Cloud Shell, or with Azure CLI 2.60.0 or later:

    az account set --subscription "<subscription-ID>"
    
    az functionapp list-flexconsumption-locations \
      --query "sort_by(@, &name)[].{Region:name}" -o table
    
    az provider show --namespace Microsoft.App \
      --query registrationState -o tsv
    
    • Continue with West US 3 only if it appears in the location output.
    • If Microsoft.App is not Registered, register it and wait until registration completes:
    az provider register --namespace Microsoft.App
    
    az provider show --namespace Microsoft.App \
      --query registrationState -o tsv
    

    This is separate from the Microsoft.Web registration you already confirmed.

    2. Retry using the Flex-specific creation operation

    Since the portal deployment failed specifically while creating the generated server farm, bypass that portal deployment and create the Node.js 22 app directly with az functionapp create. This command creates the app in a Flex Consumption plan; it does not require a separate plan-first command.^2^

    Use the storage account that was already created:

    az functionapp create \
      --resource-group rg-deskpilot-dev \
      --name <globally-unique-function-app-name> \
      --storage-account <existing-storage-account-name> \
      --flexconsumption-location westus3 \
      --runtime node \
      --runtime-version 22
    

    Expected result: the command returns the new function-app resource and its associated Flex Consumption plan.

    If West US 3 is not listed, select one of the regions returned by list-flexconsumption-locations. Do not assume that general Azure Functions availability means Flex Consumption is available in that region.^2^

    3. Escalate if the CLI reproduces the same plan failure

    If the CLI command still returns Cannot find Subscription with name or another rejection while creating Microsoft.Web/serverfarms, this is no longer isolated to the portal-generated deployment. Similar Consumption/Flex cases where an active subscription was blocked from creating a server farm required Microsoft to correct subscription-side backend state.^3^

    Create a support request under:

    Azure portal → Help + support → Create a support request → Technical → Azure Functions → Creating or Deleting Function Apps

    Include:

    • Subscription ID and resource group
    • Region, runtime, and Flex Consumption hosting choice
    • Failed deployment and server-farm resource names
    • Complete CLI command and error output
    • Portal deployment error JSON
    • Correlation ID and UTC failure timestamp
    • Confirmation that Microsoft.Web and Microsoft.App show Registered
    • Output showing that West US 3 is returned by list-flexconsumption-locations

    For ARM deployment failures, Microsoft’s troubleshooting guidance specifically requests the failed operation details and correlation ID from Resource group → Deployments. It also recommends trying an alternative creation tool such as Azure CLI when portal creation fails.^4^

    The successfully created storage, identity, and monitoring resources do not establish that the Microsoft.Web plan operation is enabled; leave them in place if retrying with the CLI, but remove unused resources afterward to avoid charges.


    References

    1. Azure Functions Flex Consumption plan hosting
    2. Create and Manage Function Apps in a Flex Consumption Plan
    3. I am unable to deploy any Function App (Consumption or Flex Consumption) because the subscription returns: ServerFarmCreationNotAllowed Please enable App Service Plan creation for this subscription. I need to run Azure Function Apps for API endpoints and - Microsoft Q&A
    4. Resolve issues when creating, deleting, or restoring Azure Functions
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.