App Services Support

This article provides comprehensive information on obtaining support for Azure App Services, including common issues, troubleshooting steps, and avenues for further assistance.

Introduction to App Services Support

Azure App Service is a fully managed platform for building, deploying, and scaling web apps, mobile back ends, and connected business logic. When you encounter issues, leveraging the right support channels can significantly speed up resolution. This documentation aims to guide you through the most effective support strategies.

Common Support Scenarios

  • Deployment Failures: Issues related to deploying code from various sources (Git, GitHub, Azure Repos, Docker Hub, etc.).
  • Performance Degradation: Slow response times, high CPU or memory usage, and timeouts.
  • Runtime Errors: Application crashes, unhandled exceptions, and configuration problems specific to the runtime stack (e.g., .NET, Node.js, Python, Java).
  • Connectivity Issues: Problems with inbound or outbound connections, VNet integration, or hybrid connections.
  • Authentication and Authorization: Challenges with configuring identity providers or managing access to the application.
  • Scaling and Availability: Issues with auto-scaling rules, manual scaling, or understanding service level agreements (SLAs).

Troubleshooting Steps

Before seeking direct support, consider these common troubleshooting steps:

1. Review Azure App Service Diagnostics

The Azure portal provides built-in diagnostic tools that can often identify and even resolve issues automatically. Navigate to your App Service in the Azure portal and explore the Diagnose and solve problems section.

2. Check Application Logs

Application logs are crucial for understanding runtime behavior. Enable and review application logs, diagnostic logs, and web server logs. You can stream these logs in real-time or download them for detailed analysis.

Example of how to enable logging:


// In your App Service Configuration in the Azure Portal:
// Go to Settings -> Diagnostic logs
// Enable Application Logging (Filesystem or Blob Storage)
// Enable Web server logging
// Enable Detailed error messages (for development/debugging)
// Enable Failed request tracing

3. Monitor Resource Utilization

Utilize the Metrics blade in the Azure portal to monitor CPU, memory, disk I/O, and network traffic. Sudden spikes or consistently high usage can indicate performance bottlenecks.

4. Test Connectivity

Use Kudu (Advanced Tools) or SSH to test network connectivity from within the App Service instance to external resources or other Azure services.

5. Consult Documentation and Community Forums

Often, your issue may have been encountered and solved by others. Search the official Azure documentation and community forums for similar problems.

Seeking Professional Support

If self-service troubleshooting doesn't resolve your issue, you can leverage Microsoft's professional support channels:

Azure Support Plans

Azure offers various support plans (Developer, Standard, Professional Direct, Premier) that provide different levels of access to Microsoft engineers. The availability of technical support, response times, and severity levels vary by plan.

You can learn more about Azure Support Plans here: Azure Support Plans

Creating a Support Request

To create a support request:

  1. Navigate to your App Service in the Azure portal.
  2. In the left-hand menu, under Help + support, select New support request.
  3. Fill in the required details, including the service (App Services), problem type, severity, and a detailed description of the issue.
  4. Attach relevant logs, screenshots, and any other information that might help diagnose the problem.

Azure Community Support

Engage with the Azure community on platforms like:

  • Microsoft Q&A (formerly Stack Overflow for Microsoft): Azure on Microsoft Q&A
  • Azure Forums: Connect with other Azure users and experts.

Key Information for Support Requests

To help us assist you more effectively, please have the following information ready when you open a support ticket or ask for help:

  • Your Azure Subscription ID.
  • The name of your App Service.
  • The resource group your App Service belongs to.
  • The region where your App Service is deployed.
  • A detailed description of the problem, including steps to reproduce it.
  • The exact error messages you are receiving.
  • Relevant timestamps (including timezone).
  • Any recent changes made to the application or its configuration.
  • Results of the troubleshooting steps you have already taken.

By following these guidelines, you can ensure a smoother and more efficient support experience for your Azure App Services.