Merge pull request #266370 from rcdun/preview_nmp_and_api

Document preview Provisioning API and Number Management Portal

Author: v-ccolin

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

@@ -5,7 +5,7 @@ author: rcdun
 ms.author: rdunstan
 ms.service: communications-gateway
 ms.topic: integration
-ms.date: 11/27/2023
+ms.date: 02/16/2024
 ms.custom:
     - template-how-to-pattern
     - has-azure-ad-ps-ref
@@ -27,17 +27,20 @@ You must [deploy Azure Communications Gateway](deploy.md).
 You must have access to a user account with the Microsoft Entra Global Administrator role.
 
 You must allocate six "service verification" test numbers for each of Operator Connect and Teams Phone Mobile. These numbers are used by the Operator Connect and Teams Phone Mobile programs for continuous call testing.
+
 - If you selected the service you're setting up as part of deploying Azure Communications Gateway, you've allocated numbers for the service already.
 - Otherwise, choose the phone numbers now (in E.164 format and including the country code) and names to identify them. We recommend names of the form OC1 and OC2 (for Operator Connect) and TPM1 and TPM2 (for Teams Phone Mobile).
 
 You must also allocate at least one test number for each service for integration testing.
 
 If you want to set up Teams Phone Mobile and you didn't select it when you deployed Azure Communications Gateway, choose:
+
 - The number used in Teams Phone Mobile to access the Voicemail Interactive Voice Response (IVR) from native dialers.
-- How you plan to route Teams Phone Mobile calls to Microsoft Phone System. Choose from:
-    - Integrated MCP (MCP in Azure Communications Gateway).
-    - On-premises MCP.
-    - Another method to route calls.
+- The method for routing Teams Phone Mobile calls to Microsoft Phone System. Choose from:
+
+  - Integrated MCP (MCP in Azure Communications Gateway).
+  - On-premises MCP.
+  - Another method to route calls.
 
 ## Enable Operator Connect or Teams Phone Mobile support
 
@@ -46,9 +49,9 @@ If you want to set up Teams Phone Mobile and you didn't select it when you deplo
 
 1. Sign in to the [Azure portal](https://azure.microsoft.com/).
 1. In the search bar at the top of the page, search for your Communications Gateway resource and select it.
-1. In the side menu bar, find **Communications services** and select **Operator Connect** or **Teams Phone Mobile** (as appropriate) to open a page for the service.
-1. On the service's page, select **Operator Connect settings** or **Teams Phone Mobile settings**.
-1. Fill in the fields, selecting **Review + create** and **Create**.
+1. In the side menu bar, under **Communications services**, select **Operator Connect** or **Teams Phone Mobile** (as appropriate) to open a page for the service.
+1. Select **Operator Connect settings** or **Teams Phone Mobile settings**.
+1. Fill in the fields, then select **Review + create** and **Create**.
 1. Select the **Overview** page for your resource.
 1. Select **Add test lines** and add the service verification lines you chose in [Prerequisites](#prerequisites). Set the **Testing purpose** to **Automated**.
     > [!IMPORTANT]
@@ -72,7 +75,7 @@ To add the Project Synergy application:
        ```azurepowershell
        Get-Module -ListAvailable
        ```
-    1. If `AzureAD` doesn't appear in the output, install the module:
+    1. If `AzureAD` doesn't appear in the output, install the module.
         1. Close your current PowerShell window.
         1. Open PowerShell as an admin.
         1. Run the following command.
@@ -136,7 +139,7 @@ Do the following steps in the tenant that contains your Project Synergy applicat
        ```azurepowershell
        Get-Module -ListAvailable
        ```
-    1. If `AzureAD` doesn't appear in the output, install the module:
+    1. If `AzureAD` doesn't appear in the output, install the module.
         1. Close your current PowerShell window.
         1. Open PowerShell as an admin.
         1. Run the following command.

articles/communications-gateway/get-started.md

@@ -1,11 +1,11 @@
 ---
 title: Getting started with Azure Communications Gateway
-description: Learn how to plan for and deploy Azure Communications Gateway
+description: Learn how to plan for and deploy Azure Communications Gateway.
 author: rcdun
 ms.author: rdunstan
 ms.service: communications-gateway
 ms.topic: how-to
-ms.date: 11/06/2023
+ms.date: 02/16/2024
 
 #CustomerIntent: As someone setting up Azure Communications Gateway, I want to understand the steps I need to carry out to have live traffic through my deployment.
 ---
@@ -29,13 +29,13 @@ Read the following articles to learn about Azure Communications Gateway.
 - [Onboarding with Included Benefits for Azure Communications Gateway](onboarding.md), to learn about onboarding to Operator Connect or Teams Phone Mobile and the support we can provide.
 - [Connectivity for Azure Communications Gateway](connectivity.md) and [Reliability in Azure Communications Gateway](reliability-communications-gateway.md), to create a network design that includes Azure Communications Gateway.
 - [Overview of security for Azure Communications Gateway](security.md), to learn about how Azure Communications Gateway keeps customer data and your network secure.
-- [Provisioning API for Azure Communications Gateway](provisioning-platform.md), to learn about when you might need or want to integrate with the Provisioning API.
+- [Provisioning API (preview) for Azure Communications Gateway](provisioning-platform.md), to learn about when you might need or want to integrate with the Provisioning API.
 - [Plan and manage costs for Azure Communications Gateway](plan-and-manage-costs.md), to learn about costs for Azure Communications Gateway.
-- [Azure Communications Gateway limits, quotas and restrictions](limits.md), to learn about the limits and quotas associated with the Azure Communications Gateway
+- [Azure Communications Gateway limits, quotas and restrictions](limits.md), to learn about the limits and quotas associated with the Azure Communications Gateway.
 
 For Operator Connect and Teams Phone Mobile, also read:
 
-- [Overview of interoperability of Azure Communications Gateway with Operator Connect and Teams Phone Mobile](interoperability-operator-connect.md)
+- [Overview of interoperability of Azure Communications Gateway with Operator Connect and Teams Phone Mobile](interoperability-operator-connect.md).
 - [Mobile Control Point in Azure Communications Gateway for Teams Phone Mobile](mobile-control-point.md).
 - [Emergency calling for Operator Connect and Teams Phone Mobile with Azure Communications Gateway](emergency-calls-operator-connect.md).
 
@@ -59,10 +59,9 @@ Use the following procedures to deploy Azure Communications Gateway and connect
 
 1. [Prepare to deploy Azure Communications Gateway](prepare-to-deploy.md) describes the steps you need to take before you can start creating your Azure Communications Gateway resource. You might need to refer to some of the articles listed in [Learn about and plan for Azure Communications Gateway](#learn-about-and-plan-for-azure-communications-gateway).
 1. [Deploy Azure Communications Gateway](deploy.md) describes how to create your Azure Communications Gateway resource in the Azure portal and connect it to your networks.
-1. [Integrate with Azure Communications Gateway's Provisioning API](integrate-with-provisioning-api.md) describes how to integrate with the Provisioning API. Integrating with the API is:
+1. [Integrate with Azure Communications Gateway's Provisioning API (preview)](integrate-with-provisioning-api.md) describes how to integrate with the Provisioning API. Integrating with the API is:
     - Required for Microsoft Teams Direct Routing and Zoom Phone Cloud Peering.
-    - Optional for Operator Connect: only required to add custom headers to messages entering your core network.
-    - Not supported for Teams Phone Mobile.
+    - Recommended for Operator Connect and Teams Phone Mobile because it enables flow-through API-based provisioning of your customers both on Azure Communications Gateway and in the Operator Connect environment. This enables additional functionality to be provided by Azure Communications Gateway, such as injecting custom SIP headers, while also fulfilling the requirement from the the Operator Connect and Teams Phone Mobile programs for you to use APIs for provisioning customers in the Operator Connect environment. For more information, see [Provisioning and Operator Connect APIs](interoperability-operator-connect.md#provisioning-and-operator-connect-apis).
 
 ## Integrate with your chosen communications services
 
@@ -86,5 +85,5 @@ Use the following procedures to integrate with Zoom Phone Cloud Peering.
 
 ## Next steps
 
-- Learn about [your network and Azure Communications Gateway](role-in-network.md)
+- Learn about [your network and Azure Communications Gateway](role-in-network.md).
 - Find out about [the newest enhancements to Azure Communications Gateway](whats-new.md).

articles/communications-gateway/integrate-with-provisioning-api.md

@@ -5,23 +5,28 @@ author: rcdun
 ms.author: rdunstan
 ms.service: communications-gateway
 ms.topic: how-to
-ms.date: 10/09/2023
+ms.date: 02/16/2024
 ---
 
-# Integrate with Azure Communications Gateway's Provisioning API
+# Integrate with Azure Communications Gateway's Provisioning API (preview)
 
-This article explains when you need to integrate with Azure Communications Gateway's Provisioning API  and provides a high-level overview of getting started. It's aimed at software developers working for telecommunications operators.
+This article explains when you need to integrate with Azure Communications Gateway's Provisioning API (preview) and provides a high-level overview of getting started. It's aimed at software developers working for telecommunications operators.
 
-The Provisioning API allows you to configure Azure Communications Gateway with the details of your customers and the numbers that you have assigned to them. It's a REST API.
+The Provisioning API allows you to configure Azure Communications Gateway with the details of your customers and the numbers that you have assigned to them. If you use the Provisioning API for *backend service sync*, you can also provision the Operator Connect and Teams Phone Mobile environments with the details of your enterprise customers and the numbers that you allocate to them. This flow-through provisioning allows you to meet the Operator Connect and Teams Phone Mobile requirement to use APIs to manage your customers and numbers after you launch your service.
+
+ The Provisioning API is a REST API.
 
 Whether you need to integrate with the REST API depends on your chosen communications service.
 
 |Communications service  |Provisioning API integration  |Purpose  |
 |---------|---------|---------|
-|Microsoft Teams Direct Routing |Required |- Configure the subdomain associated with each Direct Routing customer<br>- Generate DNS records specific to each customer (as required by the Microsoft 365 environment)<br>- Indicate that numbers are enabled for Direct Routing.<br>- (Optional) Configure a custom header for messages to your network|
-|Operator Connect|Optional|(Optional) Configure a custom header for messages to your network|
-|Teams Phone Mobile|Not supported|N/A|
-|Zoom Phone Cloud Peering |Required |- Indicate that numbers are enabled for Zoom<br>- (Optional) Configure a custom header for messages to your network|
+|Microsoft Teams Direct Routing |Required |- Configuring the subdomain associated with each Direct Routing customer.<br>- Generating DNS records specific to each customer (as required by the Microsoft 365 environment).<br>- Indicating that numbers are enabled for Direct Routing.<br>- (Optional) Configuring a custom header for messages to your network.|
+|Operator Connect|Recommended|- (Recommended) Flow-through provisioning of Operator Connect customers through interoperation with Operator Connect APIs  (using backend service sync). <br>- (Optional) Configuring a custom header for messages to your network. |
+|Teams Phone Mobile|Recommended|- (Recommended) Flow-through provisioning of Teams Phone Mobile customers through interoperation with Operator Connect APIs (using backend service sync). <br>- (Optional) Configuring a custom header for messages to your network. |
+|Zoom Phone Cloud Peering |Required |- Indicating that numbers are enabled for Zoom. <br>- (Optional) Configuring a custom header for messages to your network.|
+
+> [!TIP]
+> You can also use the Number Management Portal (preview) for Operator Connect and Teams Phone Mobile.
 
 ## Prerequisites
 
@@ -37,6 +42,7 @@ Use the *Key concepts* and *Examples* information in the [API Reference](/rest/a
 
 - *Account* resources are descriptions of operator customers (typically, an enterprise), and per-customer settings for service provisioning.
 - *Number* resources belong to an account. They describe numbers, the services that the numbers make use of (for example, Microsoft Teams Direct Routing), and any extra per-number configuration.
+- *Request for Information (RFI)* resources are descriptions of operator customers (typically an enterprise) who have expressed interest in receiving service from the operator through Operator Connect and Teams Phone Mobile.
 
 [!INCLUDE [limits on the Provisioning API](includes/communications-gateway-provisioning-api-restrictions.md)]
 

articles/communications-gateway/interoperability-operator-connect.md

@@ -1,11 +1,11 @@
 ---
 title: Overview of Operator Connect and Teams Phone Mobile with Azure Communications Gateway
-description: Understand how Azure Communications Gateway fits into your fixed and mobile networks and into the Operator Connect and Teams Phone Mobile environments
+description: Understand how Azure Communications Gateway fits into your fixed and mobile networks and into the Operator Connect and Teams Phone Mobile environments.
 author: rcdun
 ms.author: rdunstan
 ms.service: communications-gateway
 ms.topic: conceptual
-ms.date: 01/31/2024
+ms.date: 02/16/2024
 ms.custom: template-concept
 ---
 
@@ -91,14 +91,17 @@ Azure Communications Gateway offers multiple media interworking options. For exa
 
 For full details of the media interworking features available in Azure Communications Gateway, raise a support request.
 
-## Number Management Portal for provisioning with Operator Connect APIs
+## Provisioning and Operator Connect APIs
 
-Operator Connect and Teams Phone Mobile require API integration between your IT systems and Microsoft Teams for flow-through provisioning and automation. After your deployment has been certified and launched, you must not use the Operator Connect portal for provisioning. You can use Azure Communications Gateway's Number Management Portal instead. This Azure portal feature enables you to pass the certification process and sell Operator Connect or Teams Phone Mobile services while you carry out a custom API integration project.
+Operator Connect and Teams Phone Mobile require API integration between your IT systems and Microsoft Teams for flow-through provisioning and automation. After your deployment is certified and launched, you must not use a portal for provisioning. Azure Communications Gateway offers an alternative method for provisioning subscribers with its Provisioning API (preview) that allows flow-through provisioning from your BSS clients to Azure Communications Gateway and the Operator Connect environments. Azure Communications Gateway also provides a Number Management Portal (preview), integrated into the Azure portal, for browser-based provisioning which can be used to get you started while you complete API integration. 
 
-For more information, see [Manage an enterprise with Azure Communications Gateway's Number Management Portal for Operator Connect and Teams Phone Mobile](manage-enterprise-operator-connect.md).
+For more information, see:
+
+- [Provisioning API (preview) for Azure Communications Gateway](provisioning-platform.md) and [Integrate with Azure Communications Gateway's Provisioning API](integrate-with-provisioning-api.md).
+- [Manage an enterprise with Azure Communications Gateway's Number Management Portal (preview) for Operator Connect and Teams Phone Mobile](manage-enterprise-operator-connect.md).
 
 > [!TIP]
-> The Number Management Portal does not allow your enterprise customers to manage Teams Calling. For example, it does not provide self-service portals.
+> These methods do not allow your enterprise customers to manage Teams Calling. For example, they do not provide self-service portals.
 
 ## Providing call duration data to Microsoft Teams