Why is submitting a request online the preferred method of contacting Azure Support?

Submitting support requests online allows us to deliver fast and deep technical expertise in the most effective and efficient manner possible. Due to the detailed nature of the requests, it is much easier to provide relevant information online, compared to reading this information over the phone. This model also eliminates unproductive hold time for a simple, intuitive online process. As a result, customer problems are routed more quickly, to the most qualified engineer.

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’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, like an FAQ page. Learn more about how QnA Maker works