Merge pull request #291714 from aspreadbury/aocp-retirement-20241216

PMEds28 · web-flow · commit 5221ed8f4d8e · 2024-12-11T10:31:06.000Z
Changes to ACG documentation to remove references to AOCP
diff --git a/articles/communications-gateway/breadcrumb/toc.yml b/articles/communications-gateway/breadcrumb/toc.yml
@@ -6,9 +6,6 @@ items:
   - tocHref: /security/benchmark/azure/baselines/
     name: Communications Gateway
     topicHref: /azure/communications-gateway/
-  - tocHref: /azure/operator-call-protection/
-    name: Communications Gateway
-    topicHref: /azure/communications-gateway/
   - tocHref: /azure/communications-gateway/
     name: Communications Gateway
     topicHref: /azure/communications-gateway/
diff --git a/articles/communications-gateway/deploy.md b/articles/communications-gateway/deploy.md
@@ -38,7 +38,7 @@ Use the Azure portal to create an Azure Communications Gateway resource.
 1. Select the communications services that you want to support in the **Communications Services** configuration tab, use the information that you collected in [Collect configuration values for each communications service](prepare-to-deploy.md#collect-configuration-values-for-each-communications-service) to fill out the fields, and then select **Next: Test Lines**.
 1. Use the information that you collected in [Collect values for service verification numbers](prepare-to-deploy.md#collect-values-for-service-verification-numbers) to fill out the fields in the **Test Lines** configuration tab and then select **Next: Tags**.
     - Don't configure numbers for integration testing.
-    - Microsoft Teams Direct Routing and Azure Operator Call Protection Preview don't require service verification numbers.
+    - Microsoft Teams Direct Routing doesn't require service verification numbers.
 1. (Optional) Configure tags for your Azure Communications Gateway resource: enter a **Name** and **Value** for each tag you want to create.
 1. Select **Review + create**.
 
@@ -74,7 +74,6 @@ When your resource has been provisioned, you can connect Azure Communications Ga
     * Depending on your network, you might need to configure SBCs, softswitches, and access control lists (ACLs).
     > [!IMPORTANT]
     > When configuring SBCs, firewalls, and ACLs, ensure that your network can receive traffic from both of the /28 IP ranges provided to you by your onboarding team because the IP addresses used by Azure Communications Gateway can change as a result of maintenance, scaling or disaster scenarios.
-    * If you are using Azure Operator Call Protection Preview, a component in your network (typically an SBC), must act as a SIPREC Session Recording Client (SRC).
     * Your network needs to send SIP traffic to per-region FQDNs for Azure Communications Gateway. To find these FQDNs:
         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.
diff --git a/articles/communications-gateway/get-started.md b/articles/communications-gateway/get-started.md
@@ -50,9 +50,6 @@ For Zoom Phone Cloud Peering, also read:
 - [Overview of interoperability of Azure Communications Gateway with Zoom Phone Cloud Peering](interoperability-zoom.md).
 - [Emergency calling for Zoom Phone Cloud Peering with Azure Communications Gateway](emergency-calls-zoom.md).
 
-For Azure Operator Call Protection Preview, also read:
-- [Overview of deploying Azure Operator Call Protection Preview](../operator-call-protection/deployment-overview.md).
-
 As part of your planning, ensure your network can support the connectivity and interoperability requirements in these articles.
 
 Read through the procedures in [Deploy Azure Communications Gateway](#deploy-azure-communications-gateway) and [Integrate with your chosen communications services](#integrate-with-your-chosen-communications-services). Use those procedures as input into your planning for deployment, testing and going live. You need to work with an onboarding team (from Microsoft or one that you arrange yourself) during these phases, so ensure that you discuss timelines and requirements with this team.
@@ -84,9 +81,6 @@ Use the following procedures to integrate with Zoom Phone Cloud Peering.
 1. [Connect Azure Communications Gateway to Zoom Phone Cloud Peering](connect-zoom.md) describes how to connect Azure Communications Gateway to Zoom servers.
 1. [Prepare for live traffic with Zoom Phone Cloud Peering and Azure Communications Gateway](prepare-for-live-traffic-zoom.md) describes how to test your deployment and launch your service.
 
-Use the following procedures to integrate with Azure Operator Call Protection Preview.
-- [Set Up Azure Operator Call Protection Preview](../operator-call-protection/set-up-operator-call-protection.md).
-
 ## Next steps
 
 - Learn about [your network and Azure Communications Gateway](role-in-network.md).
diff --git a/articles/communications-gateway/includes/communications-gateway-deployment-prerequisites.md b/articles/communications-gateway/includes/communications-gateway-deployment-prerequisites.md
@@ -23,7 +23,6 @@ Service | Numbers for integration testing | Service verification numbers |
 |Teams Phone Mobile | 1 (minimum) | - Production deployments: 6<br/> - Lab deployments: 3 |
 |Microsoft Teams Direct Routing | 1 (minimum) |  None (not applicable) |
 |Zoom Phone Cloud Peering | 1 (minimum) | - US and Canada: 6<br/>- Rest of world: 2 |
-|Azure Operator Call Protection Preview | 1 (minimum) | None (not applicable) |
 
 > [!IMPORTANT]
 > Service verification numbers must be usable throughout the lifetime of your deployment.
diff --git a/articles/communications-gateway/integrate-with-provisioning-api.md b/articles/communications-gateway/integrate-with-provisioning-api.md
@@ -24,7 +24,6 @@ Whether you integrate with the Provisioning API depends on your chosen communica
 |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). |
 |Zoom Phone Cloud Peering |Supported (as alternative to the Number Management Portal) |- Indicating that numbers are enabled for Zoom. <br>- (Optional) Configuring a custom header for messages to your network.|
-| Azure Operator Call Protection Preview |Supported (as alternative to the Number Management Portal) |-  Indicating that numbers are enabled for Azure Operator Call Protection.<br> - Automatic provisioning of Azure Operator Call Protection. |
 
 > [!TIP]
 > Azure Communications Gateway's Number Management Portal provides equivalent function for manual provisioning. However, you can't use the Number Management Portal for flow-thorough provisioning of Operator Connect and Teams Phone Mobile after you launch your service.
diff --git a/articles/communications-gateway/overview.md b/articles/communications-gateway/overview.md
@@ -12,20 +12,19 @@ ms.date: 10/22/2024
 # What is Azure Communications Gateway?
 
 > [!IMPORTANT]
-> The Azure Communications Gateway service will retire on October 30, 2025. To prevent any service disruption, please transition to another [Microsoft Teams Direct Routing certified Session Border Controller (SBC)](https://learn.microsoft.com/microsoftteams/direct-routing-border-controllers) solution before October 30, 2025.
+> The Azure Communications Gateway service will retire on October 30, 2025. To prevent any service disruption, please transition to another [Microsoft Teams Direct Routing certified Session Border Controller (SBC)](/microsoftteams/direct-routing-border-controllers) solution before October 30, 2025.
 
 Azure Communications Gateway provides quick, reliable and secure integration with multiple services for telecommunications operators:
 
 - Microsoft Teams calling through the Operator Connect, Teams Phone Mobile and Microsoft Teams Direct Routing programs
 - Zoom calling through the Zoom Phone Cloud Peering program
-- Fraudulent and scam call detection with Azure Operator Call Protection Preview
 
 It provides Voice and IT integration with these communications services across both fixed and mobile networks. It's certified as part of the Operator Connect Accelerator program.
 
 [!INCLUDE [communications-gateway-tsp-restriction](includes/communications-gateway-tsp-restriction.md)]
 
 :::image type="complex" source="media/azure-communications-gateway-overview.svg" alt-text="Diagram that shows Azure Communications Gateway between Microsoft Phone System, Zoom Phone, and your networks. Your networks can be fixed and/or mobile.":::
-    Diagram that shows how Azure Communications Gateway connects to the Microsoft Phone System, Zoom Phone, Azure Operator Call Protection and to your fixed and mobile networks. Microsoft Teams clients connect to Microsoft Phone System. Zoom clients connect to Zoom Phone. Your fixed network connects to PSTN endpoints. Your mobile network connects to Teams Phone Mobile users. Azure Communications Gateway connects Microsoft Phone System, Zoom Phone, Azure Operator Call Protection and your fixed and mobile networks.
+    Diagram that shows how Azure Communications Gateway connects to the Microsoft Phone System, Zoom Phone and to your fixed and mobile networks. Microsoft Teams clients connect to Microsoft Phone System. Zoom clients connect to Zoom Phone. Your fixed network connects to PSTN endpoints. Your mobile network connects to Teams Phone Mobile users. Azure Communications Gateway connects Microsoft Phone System, Zoom Phone and your fixed and mobile networks.
 :::image-end:::
 
 Azure Communications Gateway provides advanced SIP, RTP, and HTTP interoperability functions (including SBC function certified by Microsoft Teams and Zoom) so that you can integrate with your chosen communications services quickly, reliably and in a secure manner.
@@ -46,7 +45,6 @@ Traffic from all enterprises shares a single SIP trunk, using a multitenant form
 
 > [!IMPORTANT]
 > Azure Communications Gateway only stores data inside the Azure regions where you deploy it.
-> Data may be processed outside these regions for calls using Azure Operator Call Protection Preview; please contact your onboarding team for more details.
 
 ## Voice features
 
@@ -89,10 +87,6 @@ Microsoft Teams Direct Routing's multitenant model for carrier telecommunication
 
 Microsoft Teams Direct Routing allows a customer admin to assign any phone number to a user, even if you don't assign that number to them. This lack of validation presents a risk of caller ID spoofing. Azure Communications Gateway automatically screens all Direct Routing calls originating from Microsoft Teams. This screening ensures that customers can only place calls from numbers that you assign to them. However, you can disable this screening on a per-customer basis if necessary. For more information, see [Support for caller ID screening](interoperability-teams-direct-routing.md#support-for-caller-id-screening).
 
-## Scam call detection and alerting with Azure Operator Call Protection Preview
-
-Azure Operator Call Protection Preview uses AI to detect fraudulent and scam calls in real time and alert subscribers when they are at risk of being scammed. It helps telecommunications operators protect their customers from unwanted calls. For more information, see [What is Azure Operator Call Protection Preview?](../operator-call-protection/overview.md?toc=/azure/communications-gateway/toc.json&bc=/azure/communications-gateway/breadcrumb/toc.json).
-
 ## Next steps
 
 - Learn how to [get started with Azure Communications Gateway](get-started.md).
diff --git a/articles/communications-gateway/plan-and-manage-costs.md b/articles/communications-gateway/plan-and-manage-costs.md
@@ -34,7 +34,7 @@ The meters for production deployments include:
 - A "Fixed Network Service Fee" or a "Mobile Network Service Fee" meter.
     - This meter is charged hourly and includes the use of 999 users for testing and early adoption.
     - Operator Connect, Microsoft Teams Direct Routing and Zoom Phone Cloud Peering are charged as fixed networks.
-    - Teams Phone Mobile and Azure Operator Call Protection Preview are charged as mobile networks.
+    - Teams Phone Mobile is charged as a mobile network.
     - If your deployment includes fixed networks and mobile networks, you're charged the Mobile Network Service Fee.
 - A series of tiered per-user meters that charge based on the number of users that are assigned to the deployment. These per-user fees are based on the maximum number of users during your billing cycle, excluding the 999 users included in the service availability fee.
 
diff --git a/articles/communications-gateway/provisioning-platform.md b/articles/communications-gateway/provisioning-platform.md
@@ -16,7 +16,7 @@ You can configure Azure Communications Gateway with the details of your customer
 
 - Associate numbers with backend services.
 - Provision backend services with customer configuration (sometimes called _flow-through provisioning_).
-- Add custom header configuration (available for all communications services except Azure Operator Call Protection Preview and Teams Phone Mobile).
+- Add custom header configuration (available for all communications services except Teams Phone Mobile).
 
 You can provision Azure Communications Gateway with the:
 
@@ -31,7 +31,6 @@ The following table shows how you can provision Azure Communications Gateway for
 |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 |
 |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 |
 |Zoom Phone Cloud Peering | Required | Not supported | Supported |
-| Azure Operator Call Protection Preview | Required | Automatic | 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.
 
@@ -40,7 +39,7 @@ Flow-through provisioning of Operator Connect and Teams Phone Mobile with the Pr
 
 ## Associating numbers with specific communications services
 
-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:
+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:
 
 - Route calls to the correct communications service.
 - 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).
diff --git a/articles/communications-gateway/reliability-communications-gateway.md b/articles/communications-gateway/reliability-communications-gateway.md
@@ -142,9 +142,6 @@ Choose a management region from the following list:
 
 Management regions can be colocated with service regions. We recommend choosing the management region nearest to your service regions.
 
-> [!NOTE]
-> If you are enabling Azure Operator Call Protection Preview, the service region you select may not be the Azure region where supporting resources are deployed. See [Azure Products by Region](https://azure.microsoft.com/explore/global-infrastructure/products-by-region/?products=operator-call-protection) for the list of currently supported Azure Operator Call Protection service regions and speak to your onboarding team if you have any questions about which region is selected.
-
 ## Service-level agreements
 
 The reliability design described in this document is implemented by Microsoft and isn't configurable. For more information on the Azure Communications Gateway service-level agreements (SLAs), see the [Azure Communications Gateway SLA](https://www.microsoft.com/licensing/docs/view/Service-Level-Agreements-SLA-for-Online-Services).
diff --git a/articles/communications-gateway/request-changes.md b/articles/communications-gateway/request-changes.md
@@ -44,9 +44,6 @@ If you're providing Zoom service, you'll need to raise a separate support reques
 
 ## 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**.
-
 1. Concisely describe your problem or the change you need in the **Summary** box.
 1. Select an **Issue type** from the drop-down menu.
 1. 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.
diff --git a/articles/communications-gateway/role-in-network.md b/articles/communications-gateway/role-in-network.md
@@ -68,7 +68,7 @@ To allow Azure Communications Gateway to identify the correct service for a call
 - Required for Microsoft Teams Direct Routing and Zoom Phone Cloud Peering.
 - Not required for Operator Connect (because Azure Communications Gateway defaults to Operator Connect for fixed line calls) or Teams Phone Mobile.
 
-You can also configure Azure Communications Gateway to add a custom header to messages associated with a number. You can use this feature to indicate the service and/or the enterprise associated with a call. This feature is available for all communications services except Azure Operator Call Protection Preview and Teams Phone Mobile.
+You can also configure Azure Communications Gateway to add a custom header to messages associated with a number. You can use this feature to indicate the service and/or the enterprise associated with a call. This feature is available for all communications services except Teams Phone Mobile.
 
 This configuration requires you to use Azure Communication Gateway's browser-based Number Management Portal (preview) or the [Provisioning API (preview)](provisioning-platform.md).
 
diff --git a/articles/communications-gateway/toc.yml b/articles/communications-gateway/toc.yml
@@ -88,12 +88,6 @@ items:
     href: emergency-calls-zoom.md
   - name: Manage Zoom Phone Cloud Peering customers
     href: manage-enterprise-zoom.md
-- name: Integration with Azure Operator Call Protection
-  items:
-    - name: Overview of Operator Call Protection
-      href: ../operator-call-protection/overview.md?toc=/azure/communications-gateway/toc.json&bc=/azure/communications-gateway/breadcrumb/toc.json
-    - name: Set up Operator Call Protection
-      href: ../operator-call-protection/set-up-operator-call-protection.md?toc=/azure/communications-gateway/toc.json&bc=/azure/communications-gateway/breadcrumb/toc.json
 - name: Maintenance
   items:
   - name: Set up user roles
diff --git a/articles/communications-gateway/whats-new.md b/articles/communications-gateway/whats-new.md
@@ -20,12 +20,6 @@ From April 2024, you can set up private networking between your on-premises envi
 
 For more information about private networking, see [Connecting to Azure Communications Gateway](./connectivity.md). For deployment instructions, see [Prepare to connect Azure Communications Gateway to your own virtual network](./prepare-for-vnet-injection.md).
 
-### Support for Azure Operator Call Protection Preview
-
-From April 2024, you can use Azure Communications Gateway to provide Azure Operator Call Protection Preview. Azure Operator Call Protection uses AI to perform real-time analysis of consumer phone calls to detect potential phone scams and alert subscribers when they are at risk of being scammed. It's built on Azure Communications Gateway.
-
-For more information about Azure Operator Call Protection, see [What is Azure Operator Call Protection Preview?](../operator-call-protection/overview.md?toc=/azure/communications-gateway/toc.json&bc=/azure/communications-gateway/breadcrumb/toc.json). For deployment instructions, see [Set up Azure Operator Call Protection Preview](../operator-call-protection/set-up-operator-call-protection.md?toc=/azure/communications-gateway/toc.json&bc=/azure/communications-gateway/breadcrumb/toc.json).
-
 ## March 2024
 
 ### Lab deployments
