ServerFarmCreationNotAllowed

Question

Brand-new Azure Plan subscription (paid invoice #… on 9/27). Microsoft.Web is registered and no policy assignments exist, but deployment of a Function App fails with ServerFarmCreationNotAllowed.

I paid for the service yet of course Microsoft doesn't feel obligated to deliver it.

Why is this happening? I can't even submit a support ticket. I get sent in circles. Horrible service. Beyond horrible.

Answer 1

Hey Nick,

Hope you're well!

This error almost always happens because:

New subscription restrictions

When you create a brand-new paid subscription, Microsoft applies initial resource restrictions to prevent fraud/abuse.

  By default, App Service Plans (which back Function Apps) may be blocked until the subscription passes verification.
  
     These restrictions are at the **subscription level**, not due to policies you control.
     
     **Service/region availability**
     
        Certain SKUs or regions may not be enabled yet for new subscriptions. If you try to create a Consumption Plan or Premium Plan in a region where it’s restricted, you’ll hit this error.
        
        **Missing quota unlock**
        
           The subscription doesn’t yet have quota enabled for App Service. Quota unlocks typically require a support request or a few days’ wait after billing is verified.
           

---

Steps to fix it

1. Verify the subscription type
   • Go to Subscriptions → Overview. Make sure it shows Pay-As-You-Go or CSP Azure Plan and not a free/trial type.
2. Check service availability in region
   • Try deploying the Function App in another region (e.g., West Europe, East US).
   • If it succeeds in another region, your issue is regional capacity or restriction.
3. Manually request quota unlock for Microsoft.Web
   • In the portal: Subscriptions → Usage + quotas → Request Increase.
   • Select App Service or App Service Plan (ServerFarm) and request quota.
   • This effectively “unlocks” Server Farm creation for the subscription.
4. If quota request UI isn’t available
   • Use the Azure CLI/PowerShell to check quota:

          az vm list-usage --location "westeurope" --output table
     

     (replace with your target region; App Service quotas may not show here, but this confirms subscription limits).
5. Wait for subscription verification
   • Sometimes Microsoft needs 24–72h after your first invoice to fully enable all PaaS services. If steps above don’t fix it immediately, it often resolves itself after verification.This error almost always happens because:
   1. New subscription restrictions
      • When you create a brand-new paid subscription, Microsoft applies initial resource restrictions to prevent fraud/abuse.
      • By default, App Service Plans (which back Function Apps) may be blocked until the subscription passes verification.
      • These restrictions are at the subscription level, not due to policies you control.
   2. Service/region availability
      • Certain SKUs or regions may not be enabled yet for new subscriptions. If you try to create a Consumption Plan or Premium Plan in a region where it’s restricted, you’ll hit this error.
   3. Missing quota unlock
      • The subscription doesn’t yet have quota enabled for App Service. Quota unlocks typically require a support request or a few days’ wait after billing is verified.

Give these a check and if there's still an issue - drop a message here, there's a few more things we can try. It may be the case however that Microsoft may need to apply right-to-deploy from their side, but we'll find out.

Cheers

Scott