Get support or request changes to your Azure Communications Gateway
If you notice problems with Azure Communications Gateway or you need Microsoft to make changes, you can raise a support request (also known as a support ticket) in the Azure portal.
When you raise a request, we'll investigate. If we think the problem is caused by traffic from Zoom servers, we might ask you to raise a separate support request with Zoom.
This article provides an overview of how to raise support requests for Azure Communications Gateway. For more detailed information on raising support requests, see Create an Azure support request.
Support tickets for lab deployments have the same acknowledgment SLA targets as tickets for standard deployments. However, we don't guarantee resolving them as quickly as tickets for a standard deployment. You should use Severity 4 for a lab deployment, or in rare cases Severity 3. Don't use Severity 0, 1 or 2 for a lab deployment.
Prerequisites
We strongly recommend a Microsoft support plan that includes technical support, such as Microsoft Unified Support.
You must have an Owner, Contributor, or Support Request Contributor role in your Azure Communications Gateway subscription, or a custom role with Microsoft.Support/* at the subscription level.
Confirm that you need to raise an Azure Communications Gateway support request
Perform initial troubleshooting to help determine if you should raise an issue with Azure Communications Gateway or a different component. Raising issues for the correct component helps resolve your issues faster.
Raise an issue with Azure Communications Gateway if you experience an issue with:
- SIP and RTP exchanged by Azure Communications Gateway and your network.
- The Number Management Portal.
- Your Azure bill relating to Azure Communications Gateway.
If you're providing Zoom service, you'll need to raise a separate support request with Zoom for any changes that you need to your Zoom configuration.
Create a support request in the Azure portal
- Sign in to the Azure portal.
- Select the question mark icon in the top menu bar.
- Select the Help + support button.
- Select Create a support request. You might need to describe your issue first.
Enter a description of the problem or the change
Tip
If you know the problem or change affects Azure Operator Call Protection Preview, then you should set Service type to Azure Operator Call Protection instead. If unsure, keep it as Azure Communications Gateway.
- Concisely describe your problem or the change you need in the Summary box.
- Select an Issue type from the drop-down menu.
- Select your Subscription from the drop-down menu. Choose the subscription where you're noticing the problem or need a change. The support engineer assigned to your case can only access resources in the subscription you specify. If the issue applies to multiple subscriptions, you can mention other subscriptions in your description, or by sending a message later. However, the support engineer can only work on subscriptions to which you have access.
- In the new Service option, select My services.
- Set Service type to Azure Communications Gateway.
- In the new Problem type drop-down, select the problem type that most accurately describes your issue.
- Select API Bridge Issue if your Number Management Portal is returning errors when you try to gain access or carry out actions (only for Azure Communications Gateway issues).
- Select Configuration and Setup if you experience issues during initial provisioning and onboarding, or if you want to change configuration for an existing deployment.
- Select Monitoring for issues with metrics and logs.
- Select Voice Call Issue if calls aren't connecting, have poor quality, or show unexpected behavior.
- Select Other issue or question if your issue or question doesn't apply to any of the other problem types.
- From the new Problem subtype drop-down menu, select the problem subtype that most accurately describes your issue. If the problem type you selected only has one subtype, the subtype is automatically selected.
- Select Next.
Assess the recommended solutions
Based on the information you provided, we might show you recommended solutions you can use to try to resolve the problem. In some cases, we might even run a quick diagnostic. Solutions are written by Azure engineers and will solve most common problems.
If you're still unable to resolve the issue, continue creating your support request by selecting Return to support request then selecting Next.
Enter additional details
In this section, we collect more details about the problem or the change and how to contact you. Providing thorough and detailed information in this step helps us route your support request to the right engineer. For more information, see Create an Azure support request.
Review and create your support request
Before creating your request, review the details and diagnostic files that you're providing. If you want to change your request or the files that you're uploading, select Previous to return to any tab. When you're happy with your request, select Create.
Next steps
Feedback
https://aka.ms/ContentUserFeedback.
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see:Submit and view feedback for