Merge pull request #274664 from isabella-smales/isabella-smales-resource-health

Add resource health to private-5g-core

Author: prmerger-automator[bot]

articles/private-5g-core/modify-packet-core.md

@@ -81,6 +81,11 @@ In this step, you'll navigate to the **Packet Core Control Plane** resource repr
 
     :::image type="content" source="media/packet-core-field.png" alt-text="Screenshot of the Azure portal showing the Packet Core field.":::
 
+1. Verify the system is healthy before making any changes.
+   - Select **Resource Health** under the **Help** section on the left side.
+   - Check that the resource is healthy and there are no unexpected alerts.
+   - If there are any unexpected alerts, follow the recommended steps listed to recover the system.
+   - To learn more about health and the status types that may appear, see [Resource Health overview](../service-health/resource-health-overview.md).
 1. Select **Modify packet core**.
 
     :::image type="content" source="media/modify-packet-core/modify-packet-core-configuration.png" alt-text="Screenshot of the Azure portal showing the Modify packet core option.":::
@@ -168,6 +173,12 @@ This change will require a manual packet core reinstall to take effect, see [Nex
 
     - If you made changes to the packet core configuration, check that the fields under **Connected ASE device**, **Azure Arc Custom Location** and **Access network** contain the updated information.
     - If you made changes to the attached data networks, check that the fields under **Data networks** contain the updated information.
+  
+1. Select **Resource Health** under the **Help** section on the left side.
+
+    - Check that the resource is healthy and there are no unexpected alerts.
+    - If there are any unexpected alerts, follow the recommended steps listed to recover the system.
+    - To learn more about health and the status types that may appear, see [Resource Health overview](../service-health/resource-health-overview.md).
 
 ## Remove data network resource
 

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

@@ -184,6 +184,10 @@ Azure Private 5G Core is integrated with Azure Monitor Metrics Explorer, allowin
 
 For more information on using Azure Monitor to analyze metrics in your deployment, see [Monitor Azure Private 5G Core with Azure Monitor platform metrics](monitor-private-5g-core-with-platform-metrics.md).
 
+Azure Private 5G Core is integrated with Azure Resource Health, which reports on the health of your control plane resources and allows you to diagnose and get support for service issues.
+
+For more information on using Azure Resource Health to monitor the health of your deployment, see [Resource Health overview](../service-health/resource-health-overview.md).
+
 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](ue-usage-event-hub.md).
@@ -192,4 +196,4 @@ For more information on using Event Hubs to monitor UE usage in your deployment,
 
 - [Learn more about the key components of a private mobile network](key-components-of-a-private-mobile-network.md)
 - [Learn more about the design requirements for deploying a private mobile network](private-mobile-network-design-requirements.md)
-- [Learn more about the prerequisites for deploying a private mobile network](complete-private-mobile-network-prerequisites.md)
+- [Learn more about the prerequisites for deploying a private mobile network](complete-private-mobile-network-prerequisites.md)

articles/private-5g-core/reinstall-packet-core.md

@@ -86,6 +86,11 @@ Reconfigure your deployment using the information you gathered in [Back up deplo
 ## Verify reinstall
 
 1. Navigate to the **Packet Core Control Plane** resource and check that the **Packet core installation state** field contains **Installed**, as described in [View the packet core instance's installation status](#view-the-packet-core-instances-installation-status).
+1. Select **Resource Health** under the **Help** section on the left side.
+
+    - Check that the resource is healthy and there are no unexpected alerts.
+    - If there are any unexpected alerts, follow the recommended steps listed to recover the system.
+    - To learn more about health and the status types that may appear, see [Resource Health overview](../service-health/resource-health-overview.md).
 1. Use [Azure Monitor platform metrics](monitor-private-5g-core-with-platform-metrics.md) or the [packet core dashboards](packet-core-dashboards.md) to confirm your packet core instance is operating normally after the reinstall.
 
 ## Next steps

articles/private-5g-core/upgrade-packet-core-arm-template.md

@@ -24,7 +24,7 @@ If your environment meets the prerequisites, you're familiar with using ARM temp
 
 ## Prerequisites
 
-- You must have a running packet core. Use Azure monitor platform metrics or the packet core dashboards to confirm your packet core instance is operating normally.
+- You must have a running packet core. Refer to [Verify the packet core is running](#verify-the-packet-core-is-running) for details on how to check this.
 - Ensure you can sign in to the Azure portal using an account with access to the active subscription you used to create your private mobile network. This account must have the built-in Contributor or Owner role at the subscription scope.
 - Identify the name of the site that hosts the packet core instance you want to upgrade.
 - If you use Microsoft Entra ID to authenticate access to your local monitoring tools, ensure your local machine has core kubectl access to the Azure Arc-enabled Kubernetes cluster. This requires a core kubeconfig file, which you can obtain by following [Core namespace access](set-up-kubectl-access.md#core-namespace-access).
@@ -50,6 +50,28 @@ In addition, consider the following points for pre- and post-upgrade steps you m
 - Prepare a testing plan with any steps you'll need to follow to validate your deployment post-upgrade. This plan should include testing some registered devices and sessions, and you'll execute it as part of [Verify upgrade](#verify-upgrade).
 - Review [Restore backed up deployment information](#restore-backed-up-deployment-information) and [Verify upgrade](#verify-upgrade) for the post-upgrade steps you'll need to follow to ensure your deployment is fully operational. Make sure your upgrade plan allows sufficient time for these steps.
 
+## Verify the packet core is running
+
+Use [Azure Monitor platform metrics](monitor-private-5g-core-with-platform-metrics.md), [packet core dashboards](packet-core-dashboards.md), or Azure Resource Health to confirm your packet core instance is operating normally.
+
+To use Azure Resource Health to confirm the packet core instance is healthy:
+1. Sign in to the [Azure portal](https://portal.azure.com/).
+1. Search for and select the **Mobile Network** resource representing the private mobile network.
+
+    :::image type="content" source="media/mobile-network-search.png" alt-text="Screenshot of the Azure portal. It shows the results of a search for a Mobile Network resource.":::
+
+1. In the **Resource** menu, select **Sites**.
+1. Select the site containing the packet core instance you're interested in.
+1. Under the **Network function** heading, select the name of the **Packet Core Control Plane** resource shown next to **Packet Core**.
+
+    :::image type="content" source="media/packet-core-field.png" alt-text="Screenshot of the Azure portal showing the Packet Core field.":::
+
+1. Select **Resource Health** under the **Help** section on the left side.
+1. Check that the resource is healthy and there are no unexpected alerts.
+1. If there are any unexpected alerts, follow the recommended steps listed to recover the system.
+1. To learn more about health and the status types that may appear, see [Resource Health overview](../service-health/resource-health-overview.md).
+
+
 ## Upgrade the packet core instance
 
 ### Back up deployment information
@@ -116,9 +138,7 @@ Reconfigure your deployment using the information you gathered in [Back up deplo
 
 ### Verify upgrade
 
-Once the upgrade completes, check if your deployment is operating normally.
-
-1. Use [Azure Monitor platform metrics](monitor-private-5g-core-with-platform-metrics.md) or the [packet core dashboards](packet-core-dashboards.md) to confirm your packet core instance is operating normally.
+1. Follow the steps in [Verify the packet core is running](#verify-the-packet-core-is-running) to confirm that the upgrade has succeeded and packet core is running correctly.
 1. Execute the testing plan you prepared in [Plan for your upgrade](#plan-for-your-upgrade).
 
 ## Rollback

articles/private-5g-core/upgrade-packet-core-azure-portal.md

@@ -18,7 +18,7 @@ If your deployment contains multiple sites, we recommend upgrading the packet co
 
 ## Prerequisites
 
-- You must have a running packet core. Use Azure monitor platform metrics or the packet core dashboards to confirm your packet core instance is operating normally.
+- You must have a running packet core. Refer to [Verify the packet core is running](#verify-the-packet-core-is-running) for details on how to check this.
 - Ensure you can sign in to the Azure portal using an account with access to the active subscription you used to create your private mobile network. This account must have the built-in Contributor or Owner role at the subscription scope.
 - If you use Microsoft Entra ID to authenticate access to your local monitoring tools, ensure your local machine has core kubectl access to the Azure Arc-enabled Kubernetes cluster. This requires a core kubeconfig file, which you can obtain by following [Core namespace access](set-up-kubectl-access.md#core-namespace-access).
 
@@ -56,6 +56,17 @@ In addition, consider the following points for pre- and post-upgrade steps you m
 - Prepare a testing plan with any steps you'll need to follow to validate your deployment post-upgrade. This plan should include testing some registered devices and sessions, and you'll execute it as part of [Verify upgrade](#verify-upgrade).
 - Review [Restore backed up deployment information](#restore-backed-up-deployment-information) and [Verify upgrade](#verify-upgrade) for the post-upgrade steps you'll need to follow to ensure your deployment is fully operational. Make sure your upgrade plan allows sufficient time for these steps.
 
+## Verify the packet core is running
+
+1. Use Azure Resource Health to confirm the packet core instance is healthy.
+
+    - Navigate to the **Packet Core Control Plane** resource as described in [View the current packet core version](#view-the-current-packet-core-version).
+    - Select **Resource Health** under the **Help** section on the left side.
+    - Check that the resource is healthy and there are no unexpected alerts.
+    - If there are any unexpected alerts, follow the recommended steps listed to recover the system.
+    - To learn more about health and the status types that may appear, see [Resource Health overview](../service-health/resource-health-overview.md).
+1. Use [Azure Monitor platform metrics](monitor-private-5g-core-with-platform-metrics.md) or the [packet core dashboards](packet-core-dashboards.md) to confirm your packet core instance is operating normally.
+
 ## Upgrade the packet core instance
 
 ### Back up deployment information
@@ -109,7 +120,7 @@ Reconfigure your deployment using the information you gathered in [Back up deplo
 Once the upgrade completes, check if your deployment is operating normally.
 
 1. Navigate to the **Packet Core Control Plane** resource as described in [View the current packet core version](#view-the-current-packet-core-version). Check the **Version** field under the **Configuration** heading to confirm that it displays the new software version.
-1. Use [Azure Monitor platform metrics](monitor-private-5g-core-with-platform-metrics.md) or the [packet core dashboards](packet-core-dashboards.md) to confirm your packet core instance is operating normally.
+1. Follow the steps in [Verify the packet core is running](#verify-the-packet-core-is-running) to confirm that the upgrade has succeeded and packet core is running correctly.
 1. Execute the testing plan you prepared in [Plan for your upgrade](#plan-for-your-upgrade).
 
 ## Rollback