Merge pull request #270081 from robswain/supi-ga

Make SUPI concealment feature GA

Author: prmerger-automator[bot]

articles/private-5g-core/how-to-guide-deploy-a-private-mobile-network-azure-portal.md

@@ -1,7 +1,7 @@
 ---
 title: Deploy a private mobile network - Azure portal
 titleSuffix: Azure Private 5G Core
-description: This how-to guide shows how to deploy a private mobile network through Azure Private 5G Core using the Azure portal 
+description: This how-to guide shows how to deploy a private mobile network through Azure Private 5G Core using the Azure portal. 
 author: robswain
 ms.author: robswain
 ms.service: private-5g-core
@@ -36,7 +36,7 @@ In this step, you'll create the Mobile Network resource representing your privat
 
     :::image type="content" source="media/create-button-mobile-networks.png" alt-text="Screenshot of the Azure portal showing the Create button on the Mobile Networks page.":::
 
-1. Use the information you collected in [Collect private mobile network resource values](collect-required-information-for-private-mobile-network.md#collect-mobile-network-resource-values) to fill out the fields on the **Basics** configuration tab. Once you've done this, select **Next : SIMs >**.
+1. Use the information you collected in [Collect private mobile network resource values](collect-required-information-for-private-mobile-network.md#collect-mobile-network-resource-values) to fill out the fields on the **Basics** configuration tab, then select **Next : SIMs >**.
 
     :::image type="content" source="media/how-to-guide-deploy-a-private-mobile-network-azure-portal/create-private-mobile-network-basics-tab.png" alt-text="Screenshot of the Azure portal showing the Basics configuration tab.":::
 
@@ -58,14 +58,14 @@ In this step, you'll create the Mobile Network resource representing your privat
 1. If you're provisioning SIMs at this point, you'll need to take the following additional steps.
    1. If you want to use the default service and allow-all SIM policy, set **Do you wish to create a basic, allow-all SIM policy and assign it to these SIMs?** to **Yes**, and then enter the name of the data network into the **Data network name** field that appears. 
    1. Under **Enter SIM group information**, set **SIM group name** to your chosen name for the SIM group to which your SIMs will be added.
-   1. Under **Enter encryption details for SIM group**, set **Encryption type** to your chosen encryption type. Once the SIM group is created, you cannot change the encryption type.
+   1. Under **Enter encryption details for SIM group**, set **Encryption type** to your chosen encryption type. Once the SIM group is created, you can't change the encryption type.
    1. If you selected **Customer-managed keys (CMK)**, set the **Key URI** and **User-assigned identity** to those the SIM group will use for encryption.
 1. Select **Review + create**.
 1. Azure will now validate the configuration values you've entered. You should see a message indicating that your values have passed validation.
 
     :::image type="content" source="media/how-to-guide-deploy-a-private-mobile-network-azure-portal/create-private-mobile-network-review-create-tab.png" alt-text="Screenshot of the Azure portal showing validated configuration for a private mobile network.":::
 
-    If the validation fails, you'll see an error message and the configuration tab(s) containing the invalid configuration will be flagged with red dots. Select the flagged tab(s) and use the error messages to correct invalid configuration before returning to the **Review + create** tab.
+    If the validation fails, you'll see an error message, and the configuration tab or tabs containing the invalid configuration will be flagged with red dots. Select the flagged tabs and use the error messages to correct invalid configuration before returning to the **Review + create** tab.
 
 1. Once the configuration has been validated, select **Create** to create the Mobile Network, slice, and any SIM resources.
 1. The Azure portal will now deploy the resources into your chosen resource group. You'll see the following confirmation screen when your deployment is complete.
@@ -91,13 +91,13 @@ You can change the public land mobile network (PLMN) identifier, comprising a Mo
 
 1. Update the MCC and/or MNC as required.
 1. Select **Modify**.
-1. [Reinstall the packet core](reinstall-packet-core.md) to apply the change. If you have multiple packet cores in this mobile network, you will need to reinstall all of them.
+1. [Reinstall the packet core](reinstall-packet-core.md) to apply the change. If you have multiple packet cores in this mobile network, you'll need to reinstall all of them.
 
 ## Next steps
 
 You can begin designing policy control to determine how your private mobile network will handle traffic, create more network slices, enable SUPI concealment, or start adding sites to your private mobile network.
 
 - [Learn more about designing the policy control configuration for your private mobile network](policy-control.md)
 - [Create and manage network slices](create-manage-network-slices.md)
-- [Enable SUPI concealment (preview)](supi-concealment.md)
+- [Enable SUPI concealment](supi-concealment.md)
 - [Collect the required information for a site](collect-required-information-for-a-site.md)

articles/private-5g-core/monitor-private-5g-core-with-platform-metrics.md

@@ -66,4 +66,4 @@ See [Supported metrics with Azure Monitor](/azure/azure-monitor/essentials/metri
 ## Next steps
 
 - [Learn more about the Azure Monitor Metrics](/azure/azure-monitor/essentials/data-platform-metrics)
-- [Monitor UE usage via Azure Event Hubs (preview)](/azure/event-hubs/monitor-event-hubs)
+- [Monitor UE usage via Azure Event Hubs](/azure/event-hubs/monitor-event-hubs)

articles/private-5g-core/private-5g-core-overview.md

@@ -186,7 +186,7 @@ For more information on using Azure Monitor to analyze metrics in your deploymen
 
 Azure Private 5G Core can be configured to integrate with Azure Monitor Event Hubs, allowing you to monitor UE usage.
 
-For more information on using Event Hubs to monitor UE usage in your deployment, see [Monitor UE usage via Azure Event Hubs (preview)](ue-usage-event-hub.md).
+For more information on using Event Hubs to monitor UE usage in your deployment, see [Monitor UE usage via Azure Event Hubs](ue-usage-event-hub.md).
 
 ## Next steps
 

articles/private-5g-core/supi-concealment.md

@@ -1,5 +1,5 @@
 ---
-title: Enable SUPI concealment (preview)
+title: Enable SUPI concealment
 titleSuffix: Azure Private 5G Core
 description: In this how-to guide, learn how to configure SUPI concealment. 
 author: robswain
@@ -10,7 +10,7 @@ ms.date: 02/01/2024
 ms.custom: template-how-to
 ---
 
-# Enable SUPI concealment (preview)
+# Enable SUPI concealment
 
 The **subscription permanent identifier (SUPI)** is a unique, permanent identifier for a device. To avoid transmitting this identifier in plain text, it can be concealed through encryption. The encrypted value is known as the **subscription concealed identifier (SUCI)**. The encryption (SUPI concealment) is performed by the UE on registration, generating a new SUCI each time to prevent the user from being tracked. Decryption (SUCI deconcealment) is performed by the Unified Data Management (UDM) network function in the packet core.
 

articles/private-5g-core/whats-new.md

@@ -22,6 +22,17 @@ To help you stay up to date with the latest developments, this article covers:
 
 This page is updated regularly with the latest developments in Azure Private 5G Core.
 
+## March 2024
+### SUPI concealment
+
+**Type:** New feature
+
+**Date available:** March 22, 2024
+
+The SUPI (subscription permanent identifier) secret needs to be encrypted before being transmitted over the radio network as a SUCI (subscription concealed identifier). The concealment is performed by the UEs on registration, and deconcealment is performed by the packet core. You can now securely manage the required private keys through the Azure Portal and provision SIMs with public keys.
+
+For more information, see [Enable SUPI concealment](supi-concealment.md).
+
 ## February 2024
 ### New Entra ID user role needed for distributed tracing tool