How do I submit a technical support request by using Azure Support Benefits?

Access to Azure technical support requires a paid support plan. However, some Microsoft programmes could give you access to Azure technical support via Support Benefits, even if you don’t have a paid support plan. If you have these benefits, then from Azure portal Support Request Submission, select “Additional Options” under the “Support Plan” step and enter your Access ID and Contract ID information to proceed. If you have not activated your technical support benefits yet, please do so by following these steps, depending on which programme entitles you to support benefits. You will need your Access ID and Contract ID to take advantage of your Azure Support Benefits. MSDN/BizSpark – Log in to the MSDN Management Portal and activate your support benefit by clicking the technical support link at the bottom of the page. The option listed below is only displayed if you are entitled to Technical Support Benefits. MPN/SCS – Contact the MPN Regional Support Centre by going to From there, sign in to your MPN Account and contact support. Support for billing and subscription management issues is included with your Microsoft Azure subscription at no additional charge, so you don’t need to use your technical support benefits to receive support from Microsoft for billing or subscription-related issues.

Related questions and answers

  • For new conversational experiences, use Bot Framework SDK V4. Whereas customers found the dialogue 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’ll 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, such as an FAQ page. Learn more about how QnA Maker works