Skip to content

Commit 67f845e

Browse files
Merge pull request #276303 from rcdun/1577507_acg_more_context_for_no_nmp
1577507 Add more context for why the NMP can't be used for live provi…
2 parents 360da87 + f1617f2 commit 67f845e

File tree

2 files changed

+5
-5
lines changed

2 files changed

+5
-5
lines changed

articles/communications-gateway/manage-enterprise-operator-connect.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ ms.custom: template-how-to-pattern
1414
Azure Communications Gateway's Number Management Portal (preview) enables you to manage enterprise customers and their numbers through the Azure portal. Any changes made in this portal are automatically provisioned into the Operator Connect and Teams Phone Mobile environments. You can also use Azure Communications Gateway's Provisioning API (preview). For more information, see [Provisioning Azure Communications Gateway](provisioning-platform.md).
1515

1616
> [!IMPORTANT]
17-
> The Operator Connect and Teams Phone Mobile programs require that full API integration to your BSS is completed prior to launch in the Teams Admin Center. This can either be directly to the Operator Connect API or through the Azure Communications Gateway's Provisioning API (preview).
17+
> The Operator Connect and Teams Phone Mobile programs require you to complete full API integration to your BSS before your service launches in the Teams Admin Center. This integration can be directly to the Operator Connect API or through the Azure Communications Gateway's Provisioning API (preview).
1818
1919
You can:
2020

articles/communications-gateway/provisioning-platform.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Learn about customer and number configuration with the Provisioning
44
author: rcdun
55
ms.author: rdunstan
66
ms.service: communications-gateway
7-
ms.topic: conceptual
7+
ms.topic: concept
88

99
#CustomerIntent: As someone learning about Azure Communications Gateway, I want to understand the Provisioning Platform, so that I know whether I need to integrate with it
1010
---
@@ -32,10 +32,10 @@ The following table shows how you can provision Azure Communications Gateway for
3232
|Zoom Phone Cloud Peering | Required | Not supported | Supported |
3333
| Azure Operator Call Protection Preview | Required | Automatic | Not supported |
3434

35-
Flow-through provisioning using the API for Operator Connect and Teams Phone Mobile 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.
35+
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.
3636

3737
> [!IMPORTANT]
38-
> After you launch Operator Connect and Teams Phone Mobile service, you must use the Provisioning API to meet the requirement for API-based provisioning (or provide your own API integration). The Number Management Portal doesn't meet this requirement.
38+
> After you launch Operator Connect or Teams Phone Mobile service, you must use the Provisioning API to meet the requirement for API-based provisioning (or provide your own API integration). The Number Management Portal doesn't meet this requirement.
3939
4040
## Associating numbers with specific communications services
4141

@@ -54,7 +54,7 @@ Flow-through provisioning is when you use Azure Communications Gateway to provis
5454

5555
For Operator Connect and Teams Phone Mobile, you can use the Provisioning API (preview) to provision the Operator Connect and Teams Phone Mobile environment with subscribers (your customers and the numbers you assign to them). This integration is equivalent to separate integration with the Operator Management and Telephone Number Management APIs provided by the Operator Connect environment. It meets the Operator Connect and Teams Phone Mobile requirement to use APIs to manage your customers and numbers after you launch your service.
5656

57-
Before you launch your service, you can also use the Number Management Portal (preview) to provision the Operator Connect and Teams Phone Mobile environment. However, the Number Management Portal doesn't meet the requirement for API-based provisioning after you launch your service.
57+
Before you launch your service, you can also use the Number Management Portal (preview) to provision the Operator Connect and Teams Phone Mobile environment. However, the Operator Connect and Teams Phone Mobile programs require API-based provisioning after you launch your service. The Number Management Portal doesn't meet this requirement.
5858

5959
Azure Communications Gateway doesn't support flow-through provisioning for other communications services.
6060

0 commit comments

Comments
 (0)