Azure Functions Linux Consumption Plan creation thorttled after just 5 Function Apps created in a subscription

Question

I've run into a peculiar issue with resource creation throttling as I've been moving some test instances of my Function Apps into a new subscription.

My Function Apps are being deployed with an ARM template, but after moving 5 (of 10 in total) Function Apps by recreating them via ARM in the new subscription, I started receiving the following error:

"App Service Plan Create operation is throttled for subscription xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx. Please contact support if issue persists."

I've very surprised to be hitting this limit after just creating 5 consumption app service plans in the whole subscription. In addition I'm even more surprised to be hitting this kind of message considering they are dynamic app service plans intended for Azure Functions on the Linux consumption plan, so it's not like these app service plans are tying up dedicated resources as per a conventional app service plan.

Microsoft's own recommendation is 1 Function Apps per Consumption App Service Plan (https://learn.microsoft.com/en-us/azure/azure-functions/consumption-plan#multiple-apps-in-the-same-plan) feels like Consumption App Service Plans (used in Function Apps) are falling foul of a rule written with dedicated App Service Plans (used in Function Apps or App Service) in mind? i.e. a bug because all this suggests the design limit is 5 consumption based Function Apps in 1 region in a whole subscription if your adhering to Microsoft guidance.

This is just a personal project, but I know this isn't the intended design as I have significantly larger serverless setups running for clients.

Not sure if a recent change has kicked in as I haven't had any problems tearing down and redeploying this project before?

Here is the app service plan snippet from the template:

    {  
      "type": "Microsoft.Web/serverfarms",  
      "apiVersion": "2021-02-01",  
      "name": "[variables('hostingPlanName')]",  
      "location": "[resourceGroup().location]",  
      "tags": "[variables('serviceTags')]",  
      "sku": {  
        "name": "Y1",  
        "tier": "Dynamic",  
        "size": "Y1",  
        "family": "Y"  
      },  
      "properties": {  
        "computeMode": "Dynamic",  
        "reserved": true  
      }  
    }  

I also tried updating it to a slightly newer version of the Linux based consumption plan based on this (https://github.com/Azure-Samples/function-app-arm-templates/blob/main/function-app-linux-consumption/azuredeploy.json)

        {  
          "type": "Microsoft.Web/serverfarms",  
          "apiVersion": "2022-03-01",  
          "name": "[variables('hostingPlanName')]",  
          "location": "[resourceGroup().location]",  
          "tags": "[variables('serviceTags')]",  
          "sku": {  
            "name": "Y1",  
            "tier": "Dynamic",  
            "size": "Y1",  
            "family": "Y"  
          },  
          "properties": {  
            "reserved": true  
          }  
        }  

But no change, still the same error

P.S. in my googling I've seen that some people receiving an indication of a period of time to wait in there error, not the case for me, but in either case I can't believe the limit per subscription is 5 Function Apps (and associated Linux consumption app service plan) that doesn't make building anything serious realistically possible without deviating from Microsoft guidance which probably throws up it's own set of issues.

Thanks in advance! And Happy New Year!