You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/communications-gateway/provisioning-platform.md
+2-3Lines changed: 2 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,7 +16,7 @@ You can configure Azure Communications Gateway with the details of your customer
16
16
17
17
- Associate numbers with backend services.
18
18
- Provision backend services with customer configuration (sometimes called _flow-through provisioning_).
19
-
- Add custom header configuration (available for all communications services except Azure Operator Call Protection Preview and Teams Phone Mobile).
19
+
- Add custom header configuration (available for all communications services except Teams Phone Mobile).
20
20
21
21
You can provision Azure Communications Gateway with the:
22
22
@@ -31,7 +31,6 @@ The following table shows how you can provision Azure Communications Gateway for
31
31
|Operator Connect | Automatically set up if you use the API for flow-through provisioning or you use the Number Management Portal | Recommended (with API) | Supported |
32
32
|Teams Phone Mobile | Automatically set up if you use the API for flow-through provisioning or you use the Number Management Portal | Recommended (with API) | Not Supported |
Flow-through provisioning of Operator Connect and Teams Phone Mobile with the Provisioning API interoperates with the Operator Connect APIs. It therefore allows you to meet the requirements for API-based provisioning from the Operator Connect and Teams Phone Mobile programs.
37
36
@@ -40,7 +39,7 @@ Flow-through provisioning of Operator Connect and Teams Phone Mobile with the Pr
40
39
41
40
## Associating numbers with specific communications services
42
41
43
-
For Microsoft Teams Direct Routing, Zoom Phone Cloud Peering, and Azure Operator Call Protection, you must provision Azure Communications Gateway with the numbers that you want to assign to each of your customers and enable each number for the chosen communications service. This information allows Azure Communications Gateway to:
42
+
For Microsoft Teams Direct Routing and Zoom Phone Cloud Peering, you must provision Azure Communications Gateway with the numbers that you want to assign to each of your customers and enable each number for the chosen communications service. This information allows Azure Communications Gateway to:
44
43
45
44
- Route calls to the correct communications service.
46
45
- Update SIP messages for Microsoft Teams Direct Routing with the information that Microsoft Phone System requires to match calls to tenants. For more information, see [Identifying the customer tenant for Microsoft Phone System](interoperability-teams-direct-routing.md#identifying-the-customer-tenant-for-microsoft-phone-system).
0 commit comments