How to Create an Azure Support Ticket

Creating an Azure support ticket is a straightforward process that can be completed online.

You can access the Azure portal by signing in with your Azure subscription credentials.

To create a new support ticket, navigate to the Azure portal's support page.

From there, click on "New support request" to begin the process.

Make sure you have your Azure subscription details and a clear description of the issue ready to go.

Azure support tickets can be submitted 24/7, so feel free to reach out at a time that suits you.

Creating a support ticket in Azure is a straightforward process that can be done in a few different ways. You can create a support ticket from the Azure portal, using PowerShell, or even from a resource menu.

To create a support ticket from the Azure portal, you can use the "az support in-subscription tickets create" command. This command creates a new support ticket for Quota increase, Technical, Billing, and Subscription Management issues for the specified subscription. You can also use this command to create a support ticket for Subscription and Service limits (Quota) issues for the specified subscription.

You can also create a support ticket using PowerShell. A simple example of creating a test support ticket using PowerShell is available, but keep in mind that this might not directly work with Azure's current API structure. This script sends a dummy support ticket to Azure, demonstrating the process of using PowerShell for such tasks.

If you're having trouble finding the right command or script, don't worry – Azure also provides a support request option from a resource menu. To open a support request from a resource menu, follow these steps:

By following these steps, you'll be able to create a support ticket and get the help you need from Azure.

To configure your Azure support ticket, you'll need to specify the severity level. You can do this by selecting the support request, then choosing Change severity from the menu.

The severity level determines the response time according to your service level agreement. Note that 'Highest critical impact' or 'Emergency - Severe impact' level is reserved only for Premium customers.

To continue, you'll need to provide some required parameters. These include the issue category, which is a unique Id for the type of problem you're experiencing, and the urgency of the case. You'll also need to specify your preferred contact method, which can be phone or another option.

Here's a summary of the required parameters:

Remember to also specify the name or ID of your subscription, which you can configure using the az account set command.

Memory Dump Collection is a feature that allows Azure support to collect a memory dump from your Virtual Machine (VM) to help diagnose certain problem types. This process is optional, but it can be a valuable tool for troubleshooting issues.

To enable memory dump collection, you must create a support case for a specific VM problem type. This will give you the option to allow Azure support to access your VM's memory.

A complete memory dump is the largest kernel-mode dump file, which includes all physical memory used by Windows. This file does not include physical memory used by the platform firmware, by default.

The dump file is created by generating a Hyper-V save state of the VM. During this process, the VM will be paused for up to 10 minutes, after which it will be resumed. The VM is not restarted as part of this process.

Customer data is protected, as the dump file is copied to another server within the same datacenter for debugging. The data does not leave Azure's secure boundary.

Here are the steps to create a support case for memory dump collection:

When you're creating a support ticket, you'll need to provide some essential details to get the help you need. Each Azure service has its own set of issue categories, also known as problem classification.

The unique Id for the type of problem you're experiencing is a required parameter. This is known as the ProblemClassificationId.

To specify the problem classification, you'll need to provide the correct Id. Each Azure service has its own set of issue categories, so make sure to choose the right one for your issue.

Here's a list of the required parameters for a support ticket:

These parameters will help Azure's support team understand the issue and provide the necessary assistance. Make sure to provide accurate and complete information to get the help you need.

When identifying the Technical Resource ID, you'll need to know what it represents.

The Technical Resource ID is the resource Id of the Azure service resource associated with the support ticket.

In the context of Azure services, this ID is crucial for tracking and managing support tickets.

This ID is also referred to as the ServiceId.

You might be wondering how this ID is used.

The Technical Resource ID is used to identify the specific Azure service resource for which the support ticket is created.

For instance, if you're dealing with a virtual machine resource or an HDInsight resource, this ID will be relevant.

This is because the Technical Resource ID is the resource Id of the Azure service resource, such as a virtual machine resource or an HDInsight resource, for which the support ticket is created.

When choosing your preferred language for support, you'll want to select a standard language-country code.

The preferred language you choose will impact the language of support from Azure, which varies based on the severity level of your support ticket.

For English, use 'en-us', for Chinese, use 'zh-hans' or 'zh-tw', and for Spanish, use 'es-es'.

You can also choose 'fr-fr' for French, 'ja-jp' for Japanese, 'ko-kr' for Korean, 'ru-ru' for Russian, 'pt-br' for Portuguese, 'it-it' for Italian, or 'de-de' for German.

When you add an additional email address to a support ticket, it will be copied on any correspondence about the ticket. This means you can keep team members informed without having to manually forward emails.

Additional email addresses are useful for keeping team members or stakeholders in the loop about ongoing support requests.