App Services Are Failing to Deploy!!!! Need Help from Microsoft Engineers!

Hi PatrickG

To help us better assist you, could you please clarify whether you’re working with Azure Container Apps or App Service (Web App)?

It would also be helpful if you could share some additional details, such as:

• Your deployment method (e.g., Azure DevOps, GitHub Actions, Visual Studio, CLI, etc.)
• The environment or configuration you are using
• The exact error messages or logs you’re seeing during deployment

With this information, we’ll be in a better position to guide you toward a solution.

Hi PatrickG,
Thank you for your question on Microsoft Q&A.

After reviewing your deployment error and the behavior of your application, here is a summary of the main issues and suggested solutions:

Key Issues

1. Quota Error: SubscriptionIsOverQuotaForSku

This error means your subscription does not have enough quota to deploy the selected App Service Plan (SKU) in the East US region.

Possible Solutions:

• Deploy to a region with available quota, such as Central US or West US.
• Choose a lower-tier SKU, like F1 (Free) or S1 (Standard), if suitable.
• Request a quota increase for SKU B1 in East US through
• Azure Portal > Help + Support > New Support Request.

Here is your modified ARM parameters file with the following changes:

• Region changed from "East US" to "Central US"
• SKU changed from "Basic" (B1) to "Standard" (S1)

{
  "$schema": "https://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#",
  "contentVersion": "1.0.0.0",
  "parameters": {
    "subscriptionId": {
      "value": "aaa23d74-e212-4684-804b-1ca551b3eb3a"
    },
    "resourceGroupName": {
      "value": "sa-cp-rg-dev"
    },
    "name": {
      "value": "sa-cp-service-dev"
    },
    "location": {
      "value": "Central US"
    },
    "hostingPlanName": {
      "value": "ASP-sacprgdev-a15c"
    },
    "serverFarmResourceGroup": {
      "value": "sa-cp-rg-dev"
    },
    "alwaysOn": {
      "value": false
    },
    "ftpsState": {
      "value": "FtpsOnly"
    },
    "autoGeneratedDomainNameLabelScope": {
      "value": "TenantReuse"
    },
    "sku": {
      "value": "Standard"
    },
    "skuCode": {
      "value": "S1"
    },
    "numberOfWorkers": {
      "value": "1"
    },
    "workerSize": {
      "value": "0"
    },
    "workerSizeId": {
      "value": "0"
    },
    "linuxFxVersion": {
      "value": "sitecontainers"
    },
    "siteContainerName": {
      "value": "main"
    }
  }
}

2. App Service Startup Failure (Container Timeout)

The containerized app is not starting within the 10-minute limit.

Common Causes:

• Incorrect linuxFxVersion or missing startup command.
• Problems with the container image, such as accessibility or tagging issues.
• App not listening on port 80.
• Resource limitations, especially with B1 SKU.

Solutions:

• Ensure the container image is accessible and correctly tagged.
• Set the startUpCommand if needed.
• Make sure the app listens on port 80.
• Consider using a higher SKU like S1 for longer startup times.

3. Enabling and Accessing Logs

App Service Logs:

1. Go to App Service > Monitoring > App Service Logs.
2. Enable Application Logging (Filesystem), Web Server Logging, Detailed Error Messages, and Failed Request Tracing.
3. Use the Kudu Console at https://<app-name>.scm.azurewebsites.net/DebugConsole and check the /LogFiles directory for logs.

SQL Database Logs:

1. Go to SQL Database > Auditing.
2. Select a destination: Log Analytics, Event Hubs, or Azure Storage.
3. View logs with Log Analytics ("SQLSecurityAuditEvents"), Azure Storage Explorer (sqldbauditlogs container), or SSMS (sys.fn_get_audit_file).

Template Validation Troubleshooting:

• Check all required parameters are included.
• Verify resource types and names.
• Ensure there are no quota or policy restrictions.
• Use the Activity Log in Azure Portal to view detailed error JSON [5].

Recommended Actions:

1. Review quota in Azure Portal under Subscriptions > Usage + Quotas.
2. Try deploying to Central US or West US.
3. Enable diagnostic logs using App Service Logs and Kudu Console.
4. Check container image accessibility and confirm the app listens on port 80.
5. Request a quota increase if necessary.

To request a quota increase in Azure for App Service Plans or other resources, follow these steps:

Steps to Request a Quota Increase in Azure Portal:

1. Access the Azure Portal

• Go to https://portal.azure.com

2. Go to Help + Support

• Click “Help + support” in the left menu

3. Start a New Support Request

• Select “+ New support request”

4. Complete the Request Form

• Issue type: Quota
• Subscription: Choose your subscription (aaa23d74-e212-4684-804b-1ca551b3eb3a)
• Quota type: App Service
• Region: Pick the relevant region (e.g., East US)
• SKU: Select the required SKU (e.g., B1, S1, etc.)
• New limit: Enter the number of instances needed

5. Add a Justification

• Briefly state the reason for the quota increase (e.g., production deployment, performance needs)

6. Submit the Request

• Click “Create” to send the support ticket

Notes:

• Quota increases are free, but approval may take several hours to a day.
• You can check the status in Help + Support > Support Requests.
• Enterprise agreement or CSP users might require admin approval.

Kindly let us know if the above comment helps or you need further assistance on this issue.

Please "upvote" if the information helped you. This will help us and others in the community as well.

I have tried increasing the B1 quota and it didn't resolve the issue. I tried different tier SKU's and they all failed with the same error.

Hi PatrickG

Just checking—could you please try opening Azure Resource Explorer?

From the left pane, navigate to:

Providers → Microsoft.Web → Sites / Serverfarms

In the JSON, look for "resourceType": "validate" and check the "location" value.

If possible, please share the JSON file with me in a private message.

Hi PatrickG

Just checking in to see if my earlier comment was helpful or if you still need any assistance.