Share via

Azure support, what escalation paths exist for a ticket that support won't... support.

TechnicianTate 6 Reputation points
2026-04-08T20:55:08.9633333+00:00

I have a dead ticket where I've done what support asked me to do, posted to the ticket, and waited. The last response took 1 month, and now its been another month with no response from support.

This isn't a complex problem, Its a standard bastion instance that is failing to allow Entra auth into some new server 2025 vms. The ticket was opened Feb 2 2026 and now its April 8... The Bastion team threw their hands up and said that I have to talk to the Entra team, but the Entra team took a month before they gave me a boiler plate X is required for it to work list, which I responded to that I had done those steps and its still not working. Now its been another month, and no response from support.

Maybe this is one of those topics that neither support team wants to own?

Azure Bastion
Azure Bastion

An Azure service that provides private and fully managed Remote Desktop Protocol (RDP) and Secure Shell (SSH) access to virtual machines.


1 answer

Sort by: Most helpful
  1. Q&A Assist
    2026-04-08T20:55:23.54+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    For an Azure technical issue where a support ticket is stalled or bouncing between product teams, the documented escalation path is to formally escalate the case through Microsoft support rather than trying to re-open the same dead thread indefinitely.

    From the available guidance, there are three main approaches depending on how the subscription is held and who manages it:

    1. Standard Azure support ticket escalation
      For issues that cannot be resolved in-house or are stuck, the documented guidance for Azure Stack Edge and related services applies as a pattern: open or re-open a support ticket and have Microsoft assess and, if needed, escalate internally. If the current ticket is not progressing, the practical options are:
      • Open a new Azure support ticket referencing the existing ticket ID, clearly stating that the original ticket is stalled and requires escalation.
      • Ask explicitly for escalation to the appropriate backend/product team in the ticket notes.
    2. If the environment is managed via a partner (CSP)
      If the Azure subscription is under a Cloud Solution Provider (CSP), the correct escalation path is through the partner:
      • The CSP partner (with Admin agent / appropriate GDAP role) should file or re-file a Service request for the affected customer via Partner Center → Service RequestsNew request, which routes to the workload-specific portal with the correct support entitlement.
      • Partners can then use their support plan (for example, Advanced Support for Partners or Premier Support for Partners) to escalate the case on the customer’s behalf. These plans are explicitly intended for higher-touch and escalated technical support across Azure and other cloud products.
    3. If using Business Central / Power Platform–style admin centers as a pattern
      For other Microsoft cloud services, the documented pattern for stuck issues is similar: from the relevant admin center (for example, Business Central administration center or Power Platform admin center), submit a New Support Request and, if the organization has Advanced Support for Partners (ASfP) or Premier, use that contract to ensure the case is handled and escalated properly. While this example is for Business Central/Power Platform, the same principle applies in Azure: use the admin portal’s support entry point and, where available, a higher-tier support plan to drive escalation.

    In short, the supported escalation paths are:

    • Re-open or create a new Azure support ticket and explicitly request escalation.
    • If the subscription is under a CSP, have the CSP partner open and escalate the ticket via Partner Center using their support entitlements (ASfP, Premier, or Partner cloud support).
    • Where applicable, use higher-tier partner support plans to ensure the case is routed and escalated to the correct product team.

    References:

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.