how to get to Live azure support when problem doesn't fit any canned choices

Curtis Steel 0 Reputation points
2026-05-11T20:29:03.4933333+00:00

any clue on how to get to a live azure agent when I cannot create a ticket since none of the canned options fit my problem. Even having issue creating this post due to tag requirement

Community Center | Not monitored
0 comments No comments

1 answer

Sort by: Newest
  1. AI answer

    2026-05-11T20:29:16.0966667+00:00

    To reach a live Azure support engineer when the issue does not match any obvious category, use the generic support entry points and then choose the closest options just to get the ticket created. After creation, the engineer can re-route it if needed.

    1. Verify permissions and support plan
      • Ensure the account has one of these roles on the affected subscription: Owner, Contributor, or Support Request Contributor, or a custom role with Microsoft.Support/* at subscription level.
      • For non-subscription scenarios (for example, Microsoft Entra–only), an Admin role is required.
      • A technical support plan is required for technical issues; subscription management (billing, quotas, account transfers) is supported without a paid plan.
    2. Open Help + support from the Azure portal
      • Sign in to the Azure portal (for commercial: https://portal.azure.com).
      • From anywhere in the portal, select the ? icon in the global header and choose Help + support.
      • Select Create a support request.
    3. Start from the resource if possible
      • If the issue is related to a specific resource (for example, an App Service), open that resource in the portal.
      • In the resource menu, under Help or Support + troubleshooting, select Support + Troubleshooting or New Support Request.
      • This pre-selects some fields for the ticket, but they can be adjusted later.
    4. Work through the “canned” options
      • On the Problem description or initial step, enter a clear summary of the issue.
      • For Issue type, Problem type, and Problem subtype, pick the closest available options; exact match is not required. Use the free-text Problem details field later to fully describe the real problem.
      • Continue to Next: Solutions. If the recommended solutions do not apply, proceed with Next to continue creating the request.
    5. Provide detailed free-text description
      • On the Details or Additional details step, use Problem details to describe:
        • What is happening
        • When it started
        • Exact error messages
        • Steps to reproduce
      • Optionally upload logs, screenshots, or traces as a single file or compressed archive.
      • In the Advanced/Share diagnostic information section, choose whether to allow collection of diagnostic data.
    6. Choose support method and severity
      • In Support method, select the support plan and Severity that reflects business impact.
      • Provide contact information, preferred contact method, availability, and language.
    7. Review and create
      • Use Review + create to verify all details.
      • Select Create to submit the ticket.
      • A support engineer will contact using the chosen method (email/phone) according to the response times for the support plan.

    If the portal initially shows automated solutions and a “Return to support request” option instead of creating a new ticket, use Return to support request and then Next to reach the full ticket form, where the free-text fields allow describing issues that do not fit any canned choice.

    For Enterprise Agreement–related issues, use Issue type = Enrollment administration and follow the same flow; again, the free-text Problem details field is where the real scenario is described.


    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

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.