Skip to content

Commit abd777d

Browse files
authored
Remove refs to AOCP
1 parent 502cb72 commit abd777d

File tree

1 file changed

+0
-1
lines changed

1 file changed

+0
-1
lines changed

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

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,6 @@ Whether you integrate with the Provisioning API depends on your chosen communica
2424
|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. |
2525
|Teams Phone Mobile|Recommended|- (Recommended) Flow-through provisioning of Teams Phone Mobile customers through interoperation with Operator Connect APIs (using backend service sync). |
2626
|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.|
27-
| 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. |
2827

2928
> [!TIP]
3029
> 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.

0 commit comments

Comments
 (0)