need urgent help restoring app

Question

Hi,

My name is Mark Chawla, and I am an engineer at 15Five. I recently submitted a support ticket on behalf of our organization regarding an urgent issue affecting access to our Azure application.

This matter is critical to our business operations, and we kindly request that Support Request ID 2602250040000398 be escalated to high priority if possible.

If upgrading our support plan would help expedite resolution, we are open to doing so. Please let us know the appropriate steps to accelerate the review and recovery process.

Thank you in advance for your assistance. Please let me know if you require any additional information from our side.

Answer 1

Support request priority and escalation can only be changed by Microsoft support after the ticket is created. To accelerate handling of an existing Azure support request:

1. Sign in to the Azure portal and open Help + support.
2. Locate Support Request ID 2602250040000398 under All support requests.
3. Open the request and use the Send a message or update/comments area to:
   • Clearly state that the issue is business‑critical and impacting production.
   • Request an increase in severity and escalation.
   • Provide precise impact details, timelines, and any mitigation steps already taken.
4. If the current severity does not reflect the true business impact, edit the request (if allowed) to set a higher severity that matches the impact. The maximum available severity depends on the support plan.
5. If the current support plan does not allow the severity level needed, upgrade the plan, then return to Help + support and either:
   • Update the existing ticket’s severity (if the portal allows it), or
   • Create a new technical support request for the same issue with the higher severity and reference the original ticket ID in the description.

When creating or updating a technical support request, ensure the following (from the standard Azure support flow):

1. In Problem description, select Technical, choose the correct service, problem type, and problem subtype, and select the exact subscription where the affected App Service resources reside. Selecting the correct service and subscription helps route the case to the right engineer and avoids delays.
2. In Additional details, provide:
   • When the problem started.
   • Exact error messages and affected resource names.
   • Steps to reproduce and any recent configuration or deployment changes.
   • Logs or screenshots as a single attachment (for example, compressed logs). This helps the engineer act faster.
3. In Advanced diagnostic information, consider selecting Yes so Azure support can collect diagnostic data from the affected resources, which can speed up root‑cause analysis.
4. In Support method, choose the highest appropriate Severity level that matches the business impact. The available severity and response times depend on the support plan; upgrading to a higher plan can unlock higher severities and faster response.
5. Complete Contact info with accurate phone and email details and confirm the correct country/region so engineers can reach the right on‑call contact during business hours.

If the issue is extremely urgent and there is concern the ticket is not being processed quickly enough, use the regional Microsoft support phone numbers for Azure to reference the existing Support Request ID and request an escalation through the phone channel.

---

References:

• Create an Azure support request
• Azure region access request process
• Support for Microsoft Marketplace program in Partner Center
• Support for Intelligent Recommendations
• Get support for Microsoft Dev Box
• Accidentally Deleted Resource Group - Microsoft Q&A