Merge pull request #246599 from rcdun/remove_api_bridge

Remove API Bridge and API mediation; clarify NMP instructions

Author: JamesJBarnett

articles/communications-gateway/emergency-calling.md

@@ -26,7 +26,7 @@ Microsoft Teams always sends location information on SIP INVITEs for emergency c
   - When Microsoft Teams clients make an emergency call, they obtain their physical location based on their network location.
 - Static locations that you assign to numbers.
   - The Operator Connect API allows you to associate numbers with locations that enterprise administrators have already configured in the Microsoft Teams Admin Center as part of uploading numbers.
-  - Azure Communications Gateway's API Bridge Number Management Portal also allows you to associate numbers with locations during upload. You can also manage the locations associated with numbers after the numbers have been uploaded.
+  - Azure Communications Gateway's Number Management Portal also allows you to associate numbers with locations during upload. You can also manage the locations associated with numbers after the numbers have been uploaded.
 - Static locations that your enterprise customers assign. When you upload numbers, you can choose whether enterprise administrators can modify the location information associated with each number.
 
 > [!NOTE]

articles/communications-gateway/manage-enterprise.md

@@ -1,6 +1,6 @@
 ---
 title: Manage an enterprise in Azure Communications Gateway's Number Management Portal
-description: Learn how to manage enterprises and numbers for Operator Connect and Teams Phone Mobile with Azure Communication Gateway's API Bridge Number Management Portal.
+description: Learn how to manage enterprises and numbers for Operator Connect and Teams Phone Mobile with Azure Communication Gateway's Number Management Portal.
 author: rcdun
 ms.author: rdunstan
 ms.service: communications-gateway

articles/communications-gateway/media/azure-communications-gateway-architecture.png

@@ -59,30 +59,21 @@ Azure Communications Gateway's voice features include:
 
 ## API features
 
-Azure Communications Gateway includes optional API integration features. These features can help you to:
+Azure Communications Gateway includes optional API integration features. These features can help you to speed up your rollout and monetization of Teams Calling support.
 
-- Adapt your existing systems to meet the requirements of the Operator Connect and Teams Phone Mobile programs with minimal disruption.
-- Provide a consistent look and feel across your Operator Connect and Teams Phone Mobile offerings and the rest of your portfolio.
-- Speed up your rollout and monetization of Teams Calling support.
-
-### CallDuration upload
-
-Azure Communications Gateway can use the Operator Connect APIs to upload information about the duration of individual calls into the Microsoft Teams environment. This allows Microsoft Teams clients to display the call duration recorded by your network, instead of the call duration recorded by Microsoft Teams. Providing this information to Microsoft Teams is a requirement of the Operator Connect program that Azure Communications Gateway performs on your behalf. 
-
-### API Bridge Number Management Portal
+### Number Management Portal
 
 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.
 
 The Number Management Portal is available as part of the optional API Bridge feature.
 
 > [!TIP]
-> The API Bridge Number Management Portal does not allow your enterprise customers to manage Teams Calling. For example, it does not provide self-service portals.
+> The Number Management Portal does not allow your enterprise customers to manage Teams Calling. For example, it does not provide self-service portals.
 
-### API mediation
+### CallDuration upload
 
-Azure Communications Gateway's API Bridge feature includes a flexible custom interface to the Operator Connect APIs. Microsoft Professional Services can create REST or SOAP APIs that adapt the Teams Operator Connect API to your networks' requirements for APIs. These custom APIs can reduce the size of an IT integration project by reducing the changes required in your existing infrastructure.
+Azure Communications Gateway can use the Operator Connect APIs to upload information about the duration of individual calls into the Microsoft Teams environment. This allows Microsoft Teams clients to display the call duration recorded by your network, instead of the call duration recorded by Microsoft Teams. Providing this information to Microsoft Teams is a requirement of the Operator Connect program that Azure Communications Gateway performs on your behalf. 
 
-The API mediation function is designed to map between CRM and BSS systems in your network and the Teams Operator Connect API. Your CRM and BSS systems must be able to handle the information required by Teams Operator Connect. You must work with Microsoft to determine whether you can use the API mediation feature and to scope the project.
 
 ## Next steps
 

articles/communications-gateway/overview.md

@@ -40,7 +40,7 @@ For example, if you have 28,000 users assigned to the deployment each month you'
 > [!TIP]
 > If you receive a quote through Microsoft Volume Licensing, pricing may be presented as aggregated so that the values are easily readable (for example showing the per-user meters in groups of 10 or 100 rather than the pricing for individual users). This does not impact the way you will be billed.
 
-If you choose to deploy the API Bridge (for API mediation or the API Bridge Number Management Portal), you'll also be charged for your API Bridge usage. Fees for API Bridge work in the same way as the SBC User meters: a service availability meter and a per-user meter. The number of users charged for the API Bridge is always the same as the number of users charged on the SBC User meters.
+If you choose to deploy the Number Management Portal by selecting the API Bridge option, you'll also be charged for the Number Management Portal. Fees work in the same way as the SBC User meters: a service availability meter and a per-user meter. The number of users charged for the Number Management Portal is always the same as the number of users charged on the SBC User meters.
 
 > [!NOTE]
 > A user is any telephone number that meets all the following criteria.

articles/communications-gateway/plan-and-manage-costs.md

@@ -33,7 +33,7 @@ In this article, you learn about the steps you and your onboarding team must tak
 
 ## Methods
 
-In some parts of this article, the steps you must take depend on whether your deployment includes the API Bridge. This article provides instructions for both types of deployment. Choose the appropriate instructions.
+In some parts of this article, the steps you must take depend on whether your deployment includes the Number Management Portal. This article provides instructions for both types of deployment. Choose the appropriate instructions.
 
 ## 1. Connect Azure Communications Gateway to your networks
 
@@ -96,19 +96,21 @@ Your onboarding team must register the test enterprise tenant that you chose in
     1. Select your company in the list of operators, fill in the form and select **Add as my operator**.
 1. In your test tenant, create some test users (if you don't already have suitable users). These users must be licensed for Teams Phone System and in Teams Only mode.
 1. Configure emergency locations in your test tenant.
-1. Upload numbers in the API Bridge Number Management Portal (if you deployed the API Bridge) or the Operator Connect Operator Portal. Use the Calling Profile that you obtained from your onboarding team.
+1. Upload numbers in the Number Management Portal (if you chose to deploy it as part of Azure Communications Gateway) or the Operator Connect Operator Portal. Use the Calling Profile that you obtained from your onboarding team.
 
-    # [API Bridge Number Management Portal](#tab/api-bridge)
+    # [Number Management Portal](#tab/number-management-portal)
 
-    1. Open the API Bridge Number Management Portal from your list of Azure resources.
-    1. Select **Go to Consents**.
+    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.
+    1. Select your Communications Gateway resource.
+    1. On the overview page, select **Consents** in the sidebar.
     1. Select your test tenant.
     1. From the menu, select **Update Relationship Status**. Set the status to **Agreement signed**.
     1. From the menu, select **Manage Numbers**.
     1. Select **Upload numbers**.
     1. Fill in the fields as required, and then select **Review + upload** and **Upload**.
 
-    # [Operator Portal](#tab/no-api-bridge)
+    # [Operator Portal](#tab/no-number-management-portal)
 
     1. Open the Operator Portal.
     1. Select **Customer Consents**.
@@ -183,13 +185,13 @@ Your staff can use a selection of key metrics to monitor Azure Communications Ga
 
 Your onboarding team must provide Microsoft with proof that you have integrated with the Microsoft Teams Operator Connect API for provisioning.
 
-# [API Bridge](#tab/api-bridge)
+# [Number Management Portal](#tab/number-management-portal)
 
-If you have the API Bridge, your onboarding team can obtain proof automatically. You don't need to do anything.
+If you have the Number Management Portal, your onboarding team can obtain proof automatically. You don't need to do anything.
 
-# [Without the API Bridge](#tab/no-api-bridge)
+# [Without the Number Management Portal](#tab/no-number-management-portal)
 
-If you don't have the API Bridge, you must provide your onboarding team with proof that you have made successful API calls for:
+If you don't have the Number Management Portal, you must provide your onboarding team with proof that you have made successful API calls for:
 
 - Partner consent
 - TN Upload to Account

articles/communications-gateway/prepare-for-live-traffic.md

@@ -15,7 +15,7 @@ This article will guide you through how to configure the permissions required fo
 - Deploy Azure Communications Gateway through the portal
 - Raise customer support requests (support tickets)
 - Monitor Azure Communications Gateway
-- Use the API Bridge Number Management Portal for provisioning
+- Use the Number Management Portal for provisioning
 
 ## Prerequisites
 
@@ -32,7 +32,7 @@ Your staff might need different user roles, depending on the tasks they need to
 | Deploying Azure Communications Gateway |**Contributor** access to your subscription|
 | Raising support requests |**Owner**, **Contributor** or **Support Request Contributor** access to your subscription or a custom role with `Microsoft.Support/*` access at the subscription level|
 |Monitoring logs and metrics | **Reader** access to your subscription|
-|Using the API Bridge Number Management Portal| [!INCLUDE [project-synergy-nmp-permissions](includes/communications-gateway-nmp-project-synergy-permissions.md)] permissions for the Project Synergy enterprise application and **Reader** permissions to the Azure portal for your subscription|
+|Using the Number Management Portal| [!INCLUDE [project-synergy-nmp-permissions](includes/communications-gateway-nmp-project-synergy-permissions.md)] permissions for the Project Synergy enterprise application and **Reader** permissions to the Azure portal for your subscription|
 
 ## 2. Configure user roles
 
@@ -44,12 +44,12 @@ You need to use the Azure portal to configure user roles.
     - Know who needs access.
     - Know the appropriate user role or roles to assign them.
     - Are signed in with a user that is assigned a role that has role assignments write permission, such as **Owner** or **User Access Administrator** for the subscription.
-1. If you're managing access to the API Bridge Number Management Portal, ensure that you're signed in with a user that can change permissions for enterprise applications. For example, you could be a Global Administrator, Cloud Application Administrator or Application Administrator. For more information, see [Assign users and groups to an application](../active-directory/manage-apps/assign-user-or-group-access-portal.md).
+1. If you're managing access to the Number Management Portal, ensure that you're signed in with a user that can change permissions for enterprise applications. For example, you could be a Global Administrator, Cloud Application Administrator or Application Administrator. For more information, see [Assign users and groups to an application](../active-directory/manage-apps/assign-user-or-group-access-portal.md).
 
 ### 2.2 Assign a user role
 
 1. Follow the steps in [Assign a user role using the Azure portal](../role-based-access-control/role-assignments-portal.md) to assign the permissions you determined in [1. Understand the user roles required for Azure Communications Gateway](#1-understand-the-user-roles-required-for-azure-communications-gateway).
-1. If you're managing access to the API Bridge Number Management Portal, follow [Assign users and groups to an application](../active-directory/manage-apps/assign-user-or-group-access-portal.md) to assign [!INCLUDE [project-synergy-nmp-permissions](includes/communications-gateway-nmp-project-synergy-permissions.md)] permissions for each user in the Project Synergy application.
+1. If you're managing access to the Number Management Portal, follow [Assign users and groups to an application](../active-directory/manage-apps/assign-user-or-group-access-portal.md) to assign [!INCLUDE [project-synergy-nmp-permissions](includes/communications-gateway-nmp-project-synergy-permissions.md)] permissions for each user in the Project Synergy application.
 
 ## Next steps
 

articles/communications-gateway/provision-user-roles.md

@@ -98,7 +98,7 @@ The SIP peers in Azure Communications Gateway provide OPTIONS polling to allow y
 
 ### Disaster recovery: cross-region failover for management regions
 
-Voice traffic and the API Bridge are unaffected by failures in the management region, because the corresponding Azure resources are hosted in service regions. Users of the API Bridge Number Management Portal might need to sign in again.
+Voice traffic and provisioning through the Number Management Portal are unaffected by failures in the management region, because the corresponding Azure resources are hosted in service regions. Users of the Number Management Portal might need to sign in again.
 
 Monitoring services might be temporarily unavailable until service has been restored. If the management region experiences extended downtime, we'll migrate the impacted resources to another available region.
 

articles/communications-gateway/reliability-communications-gateway.md

@@ -20,8 +20,8 @@ Perform initial troubleshooting to help determine if you should raise an issue w
 
 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.
-- The API Bridge, including the API Bridge Number Management Portal.
 
 You must have an **Owner**, **Contributor**, or **Support Request Contributor** role in your Azure Communications Gateway subscription, or a custom role with [Microsoft.Support/*](../role-based-access-control/resource-provider-operations.md#microsoftsupport) at the subscription level.
 
@@ -40,7 +40,7 @@ You must have an **Owner**, **Contributor**, or **Support Request Contributor**
 1. A new **Service** option will appear giving you the option to select either **My services** or **All services**. Select **My services**.
 1. In **Service type** select **Azure Communications Gateway** from the drop-down menu.
 1. A new **Problem type** option will appear. Select the problem type that most accurately describes your issue from the drop-down menu.
-    * Select **API Bridge Issue** if your API Bridge Number Management Portal is returning errors when you try to gain access or carry out actions.
+    * Select **API Bridge Issue** if your Number Management Portal is returning errors when you try to gain access or carry out actions.
     * 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.