Merge pull request #273051 from GemmaWakeford/ADO_1513815

prmerger-automator[bot] · web-flow · commit cf4df4b2386b · 2024-04-23T15:03:46.000Z
1513815 TPM no Custom Header
diff --git a/articles/communications-gateway/integrate-with-provisioning-api.md b/articles/communications-gateway/integrate-with-provisioning-api.md
@@ -22,7 +22,7 @@ Whether you integrate with the Provisioning API depends on your chosen communica
 |---------|---------|---------|
 |Microsoft Teams Direct Routing |Supported (as alternative to the Number Management Portal) |- 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. |
+|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. |
 
diff --git a/articles/communications-gateway/manage-enterprise-operator-connect.md b/articles/communications-gateway/manage-enterprise-operator-connect.md
@@ -21,7 +21,7 @@ You can:
 * Manage your agreement with an enterprise customer.
 * Manage numbers for the enterprise.
 * View civic addresses for an enterprise.
-* Configure a custom header for a number.
+* Configure a custom header for a number (not available for Teams Phone Mobile).
 
 ## Prerequisites
 
@@ -138,7 +138,6 @@ Uploading numbers for an enterprise allows IT administrators at the enterprise t
             | `serviceDetails_teamsPhoneMobile_configuration_locationId` | The ID of a location associated with the civic address | An existing ID |
             | `serviceDetails_teamsPhoneMobile_configuration_allowTenantAddressUpdate` | Whether the enterprise can update the civic address | `true` or `false` |
             | `serviceDetails_teamsPhoneMobile_configuration_displayedCountryCode` | The country code to display for the number. Required if you're uploading a North American Toll-Free number, otherwise optional. | A valid country code |
-            | `configuration_customSipHeader`| Optional: the value for a SIP custom header. | Can only contain letters, numbers, underscores, and dashes. Can be up to 100 characters in length. |
 
     1. Select **Create numbers**.
     1. Select **File Upload**.
@@ -163,7 +162,7 @@ You can view civic addresses for an enterprise. The enterprise configures the de
 
 ## Configure a custom header for a number
 
-You can specify a custom SIP header value for an enterprise telephone number, which applies to all SIP messages sent and received by that number.
+You can specify a custom SIP header value for an enterprise telephone number, which applies to all SIP messages sent and received by that number. This feature is available for all communications services except Azure Operator Call Protection Preview and Teams Phone Mobile.
 
 1. In the sidebar, locate the **Number Management (Preview)** section and select **Numbers**.
 1. Select the **Phone number** checkbox then select **Manage number**.
diff --git a/articles/communications-gateway/provisioning-platform.md b/articles/communications-gateway/provisioning-platform.md
@@ -15,7 +15,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.
+- Add custom header configuration (available for all communications services except Azure Operator Call Protection Preview and Teams Phone Mobile).
 
 You can provision Azure Communications Gateway with the:
 
@@ -28,7 +28,7 @@ The following table shows how you can provision Azure Communications Gateway for
 |---|---|---|---|
 |Microsoft Teams Direct Routing | Required | Not supported | Supported |
 |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) | 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 |
 
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.
+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.
 
 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/whats-new.md b/articles/communications-gateway/whats-new.md
@@ -48,10 +48,6 @@ Provisioning Azure Communications Gateway and the Operator Connect and Teams Pho
 
 Before you launch your Operator Connect or Teams Phone Mobile service, you can also use the [Number Management Portal (preview)](manage-enterprise-operator-connect.md).
 
-### Custom headers for Teams Phone Mobile calls
-
-From February 2024, you can use the Provisioning API (preview) to set a custom header on Teams Phone Mobile calls. This enhancement extends the function introduced in [November 2023](#custom-header-on-messages-to-operator-networks) for configuring a custom header for Operator Connect, Microsoft Teams Direct Routing, and Zoom Phone Cloud Peering.
-
 ### Connectivity metrics
 
 From February 2024, you can monitor the health of the connection between your network and Azure Communications Gateway with new metrics for responses to SIP INVITE and OPTIONS exchanges. You can view statistics for all INVITE and OPTIONS requests, or narrow your view down to individual regions, request types, or response codes. For more information on the available metrics, see [Connectivity metrics](monitoring-azure-communications-gateway-data-reference.md#connectivity-metrics). For an overview of working with metrics, see [Analyzing, filtering and splitting metrics in Azure Monitor](monitor-azure-communications-gateway.md#analyzing-filtering-and-splitting-metrics-in-azure-monitor).
