How do I submit an Azure support request using my Premier contract?

You need to make sure that your Premier contract appears in the “Support Plan” dropdown when creating a support case. This is possible through the following options: **Microsoft pre-matching: ** In most cases, your Microsoft Premier team will have already matched your Azure subscriptions to your Premier contract and you will see it appear in the Azure Portal when creating a support case. Matching Accounts: If you login to the Azure Portal with the same Microsoft account user/email address (e.g.:,, used to access the Microsoft Premier Online portal (, your Premier contract will automatically show up in the Azure Portal. Manual Input: You can link your Premier contract to your Azure account, by entering your Premier Access ID and Contract ID information in the Azure Portal by selecting “Help + Support” in the Azure Portal and selecting “Link support contract” from the left-hand side menu. This is a one-time process and your Premier contract information will be saved with your Azure account, being accessible from all subscriptions where you have Owner/Administrator privileges. Contact your Technical Account Manager (TAM) if you do not have your access ID and contract ID information. Although Premier customers can continue to use the Microsoft Premier Online portal or phone channels to submit a support request, using the Azure Portal has a number of significant advantages including:

  • Automatically capturing necessary data (account, subscription ID, etc.) and running diagnostics
  • Faster resolution, thanks to the auto-captured data
  • Ability to create severity A/1 cases online
  • Providing you with in-context help regarding the issue you are facing

Related questions and answers

  • For new conversational experiences, use Bot Framework SDK V4. Whereas customers found the dialog models in Bot Framework SDK V3 to be too rigid and constraining, Bot Framework SDK V4 is modular and extensible. It provides the foundation for bot templates and solution accelerators. If you already have Bot Framework SDK V3 bots in production, they will continue to work as-is for the foreseeable future. Learn more on the Bot Framework FAQ page

  • The premium tier of Service Bus messaging provides all the messaging features of Azure Service Bus queues and topics with predictable, repeatable performance, higher throughput and improved availability. The premium tier uses a dedicated resource allocation model to provide workload isolation and consistent performance. Because the compute and memory resources in the premium tier are dedicated, there are no per-message transaction charges as in other tiers. All transactions are included in the message unit allocation.

  • The premium tier of Service Bus messaging is a flat daily rate per messaging unit purchased. Namespaces created as premium can have 1, 2 or 4 messaging units which will each accrue the given number of messaging unit daily rate charges. Premium namespaces can have the number of purchased messaging units changed at any time, but the daily rate is based on the maximum number of message units assigned to the namespace at any time.

  • Active devices are devices eligible to receive notifications. They are defined as unique registration IDs for devices using Google Cloud Messaging or Amazon Device Messaging, channel uniform resource identifiers (URI) for devices using Windows notification service or Microsoft push notification Service or device tokens for devices using Apple push notification service.

  • With Microsoft, you get powerful conversational AI and natural language understanding, open-source Bot Framework, enterprise-grade support and complete ownership and control of your data.

  • QnA Maker helps you create a bot that conversationally answers questions covered in your documentation, like an FAQ page. Learn more about how QnA Maker works