Deploy Microsoft.Web/serverfarms function app InternalServerError

Question

Since Friday October 1 we've experienced issues with deployments of our service plan.

Example
{
"status": "Failed",
"error": {
"code": "InternalServerError",
"message": "There was an unexpected InternalServerError. Please try again later. x-ms-correlation-request-id: bfbe09b0-b1bb-4578-9c2a-ac167ec06905"
}
}

Answer 1

We've been experiencing the same problem.

Incremental ARM re-deployments of App Plans to the UK South region have been failing with the error above since Friday Oct 01. I can only get the deployment to succeed if I delete the existing App Plan first and then retry.
These deployments have been running fine before for at least a month.

Here is an example of the template being pushed (generated from Bicep):

        {
          "type": "Microsoft.Web/serverfarms",
          "apiVersion": "2021-01-15",
          "name": "[take(variables('appServicePlanName'), 40)]",
          "location": "[parameters('location')]",
          "tags": {
            "org": "[parameters('org')]",
            "env": "[parameters('env')]",
            "proj": "[parameters('proj')]"
          },
          "sku": {
            "name": "[parameters('appPlanSkuName')]"
          },
          "kind": "app",
          "properties": {
            "perSiteScaling": false,
            "elasticScaleEnabled": false,
            "maximumElasticWorkerCount": 1,
            "isSpot": false,
            "reserved": false,
            "targetWorkerCount": 0,
            "targetWorkerSizeId": 0
          }
        }

And the raw error:

{
  "code": "DeploymentFailed",
  "message": "At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.",
  "details": [
    {
      "code": "InternalServerError",
      "message": "There was an unexpected InternalServerError.  Please try again later.  x-ms-correlation-request-id: 65b9766b-f87f-40a8-8fa1-e7bec7e4fea9"
    }
  ]
}

Answer 2

@Tore Paulsson , / @RM ,

Our product engineering team has identified an issue and are actively working on rolling out a fix.

Are you leveraging consumption plan or some other App Service Plan (ASP)? Kindly try switching to another ASP and then re-try. On which region are you provisioning the App?

Once again, we regret the inconvenience that this issue has caused. I’m constantly following up internally and will post back as soon as I have more update and want to ensure that we deliver the support you expect.