Merge pull request #241006 from James-Green-Microsoft/event-hub-ue-usage

Outbound ports for UE usage

Author: prmerger-automator[bot]

articles/private-5g-core/complete-private-mobile-network-prerequisites.md

@@ -156,6 +156,8 @@ You must set these up in addition to the [ports required for Azure Stack Edge (A
 | Port | ASE interface | Description|
 |--|--|--|
 | TCP 443 Inbound      | Management (LAN)        | Access to local monitoring tools (packet core dashboards and distributed tracing). |
+| 5671 In/Outbound    | Management (LAN) | Communication to Azure Event Hub, AMQP Protocol |
+| 5672 In/Outbound    | Management (LAN) | Communication to Azure Event Hub, AMQP Protocol |
 | SCTP 38412 Inbound   | Port 3 (Access network) | Control plane access signaling (N2 interface). </br>Only required for 5G deployments. |
 | SCTP 36412 Inbound   | Port 3 (Access network) | Control plane access signaling (S1-MME interface). </br>Only required for 4G deployments. |
 | UDP 2152 In/Outbound | Port 3 (Access network) | Access network user plane data (N3 interface for 5G, S1-U for 4G). |
@@ -174,6 +176,8 @@ You must set these up in addition to the [ports required for Azure Stack Edge (A
 | Port | ASE interface | Description|
 |--|--|--|
 | TCP 443 Inbound      | Management (LAN)        | Access to local monitoring tools (packet core dashboards and distributed tracing). |
+| 5671 In/Outbound    | Management (LAN) | Communication to Azure Event Hub, AMQP Protocol |
+| 5672 In/Outbound    | Management (LAN) | Communication to Azure Event Hub, AMQP Protocol |
 | SCTP 38412 Inbound   | Port 5 (Access network) | Control plane access signaling (N2 interface). </br>Only required for 5G deployments. |
 | SCTP 36412 Inbound   | Port 5 (Access network) | Control plane access signaling (S1-MME interface). </br>Only required for 4G deployments. |
 | UDP 2152 In/Outbound | Port 5 (Access network) | Access network user plane data (N3 interface for 5G, S1-U for 4G). |

articles/private-5g-core/ue-usage-event-hub.md

@@ -13,7 +13,7 @@ ms.custom: template-concept
 
 Azure Private 5G Core can be configured to integrate with [Event Hubs](/azure/event-hubs), allowing you to monitor UE usage. Event Hubs is a modern big data streaming platform and event ingestion service that can seamlessly integrate with AP5GC. The service can process millions of events per second with low latency. The data sent to an Event Hubs instance can be transformed and stored by using any real-time analytics providers or batching or storage adapters.
 
-You can [monitor UE usage](/azure/event-hubs/monitor-event-hubs) based on the monitoring data generated by Azure Event Hubs, and analyze or alert on this data with [Azure Monitor](/azure/azure-monitor/overview).
+You can monitor UE usage based on the monitoring data generated by Azure Event Hubs, and analyze or alert on this data with [Azure Monitor](/azure/azure-monitor/overview).
 
 > [!IMPORTANT]
 > Azure Private 5G Core integration with Event Hubs is currently in [public preview](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
@@ -24,6 +24,8 @@ UE usage monitoring can be configured during site creation or at a later stage.
 
 Once configured for the site, you must add the [UE usage schema](#ue-usage-schema) to a Schema Registry in order to use monitor UE usage in your deployment - see [Azure Schema Registry in Azure Event Hubs](/azure/event-hubs/schema-registry-overview).
 
+Once Event Hubs is receiving data from your AP5GC deployment you can write an application, using SDKs [such as .NET](/azure/event-hubs/event-hubs-dotnet-standard-getstarted-send?tabs=passwordless%2Croles-azure-portal), to consume event data and produce useful metric data.
+
 ## Reported UE usage data
 
 When configured, AP5GC will send data usage reports per QoS flow level for all PDU sessions. The following data is reported: