disconnected mode rework

Author: robswain

articles/private-5g-core/azure-stack-edge-disconnects.md

@@ -10,58 +10,54 @@ ms.date: 11/30/2022
 ms.custom: template-concept 
 ---
 
-# Azure Stack Edge disconnects
+# Temporary AP5GC disconnects
 
-There are several reasons why your *Azure Private 5G Core (AP5GC)* may have *Azure Stack Edge (ASE)* disconnects. Disconnects can either be unplanned short-term [Temporary disconnects](#temporary-disconnects) or periods of [Disconnected mode for up to five days](#disconnected-mode-for-azure-private-5g-core).
-
-## Temporary disconnects
-
-ASE can tolerate small periods of unplanned connectivity issues. The following sections detail the behavior expected during these times and behavior after ASE connectivity resumes.
+Azure Stack Edge (ASE) can tolerate up to 5 days of unplanned connectivity issues. The following sections detail the behavior expected during these times and behavior after ASE connectivity resumes.
 
 Throughout temporary disconnects, the **Azure Stack Edge overview** displays a banner stating `The device heartbeat is missing. Some operations will not be available in this state. Critical alert(s) present. Click here to view details.`
 
 > [!CAUTION]
-> Limited Azure AP5GC support is available if you encounter issues while disconnected. If you encounter issues during a disconnect, we recommend you reconnect to enable full support. If it is not possible to reconnect, support is provided on a best-effort basis.
+> Limited Azure Private 5G Core (AP5GC) support is available if you encounter issues while disconnected. If you encounter issues during a disconnect, we recommend you reconnect to enable full support. If it is not possible to reconnect, support is provided on a best-effort basis.
 
-### Configuration and provisioning actions during temporary disconnects
+While disconnected, AP5GC core functionality persists through ASE disconnects due to network issues, network equipment resets and temporary network equipment separation. During disconnects, the ASE management GUI displays several banners stating that it's currently disconnected and describing the impact on functions.
 
-It's common to see temporary failures such as timeouts of configuration and provisioning while ASE is online, but there is a connectivity issue. AP5GC can handle such events by automatically retrying configuration and provisioning actions once the ASE connectivity is restored. If ASE connectivity is not restored within 10 minutes or ASE is detected as being offline, ongoing operations will fail and you will need to repeat the action manually once ASE reconnects.
+## Unsupported functions during disconnects
 
-The **Sim overview** and **Sim Policy overview** blades display provisioning status of the resource in the site. This allows you to monitor the progress of provisioning actions. Additionally, the **Packet core control plane overview** displays the **Installation state** which can be used to monitor changes due to configuration actions.
+The following functions are not supported while disconnected:
 
-### ASE behavior after connectivity resumes
+- Deployment of the packet core
+- Updating the packet core version
+- Updating SIM configuration
+- Updating NAT configuration
+- Updating service policy
+- Provisioning SIMs
 
-Once ASE connectivity resumes, several features resume:
+### Monitoring and troubleshooting during disconnects
 
-- ASE management resume immediately.
-- **Resource Health** is viewable immediately.
-- **Workbooks** is viewable immediately and populates for the disconnected duration.
-- **Kubernetes Cluster Overview** shows as **Online** after 10 minutes.
-- **Monitoring** tabs show metrics for sites after 10 minutes, but doesn't populate stats for the disconnected duration.
-- **Kubernetes Arc Insights** shows new stats after 10 minutes, but doesn't populate stats for the disconnected duration.
-- **Resource Health** views are viewable immediately.
-- [Workbooks](../update-center/workbooks.md) for the ASE are viewable immediately and populates for the disconnected duration.
+While disconnected, you cannot enable local monitoring authentication or sign in to the [distributed tracing](distributed-tracing.md) and [packet core dashboards](packet-core-dashboards.md) using Azure Active Directory. However, you can access both distributed tracing and packet core dashboards via local access if enabled.
 
-## Disconnected mode for Azure Private 5G Core
+If you expect to need access to your local monitoring tools while the ASE device is disconnected, you can change your authentication method to local usernames and passwords by following [Modify the local access configuration in a site](modify-local-access-configuration.md).
 
-*Disconnected mode* allows for ASE disconnects of up to five days. During disconnected mode, AP5GC core functionality persists through ASE disconnects due to: network issues, network equipment resets and temporary network equipment separation. During disconnects, the ASE management GUI displays several banners alerting that it's currently disconnected and the impact on functions.
+Once the disconnect ends, log analytics on Azure updates with the stored data, excluding rate and gauge type metrics.
 
-### Functions not supported while in disconnected mode
+### Configuration and provisioning actions during temporary disconnects
 
-The following functions aren't supported while in disconnected mode:
+It's common to see temporary failures such as timeouts of configuration and provisioning while ASE is online but with a connectivity issue. AP5GC can handle such events by automatically retrying configuration and provisioning actions once ASE connectivity is restored. If ASE connectivity is not restored within 10 minutes, or ASE is detected as being offline, ongoing operations will fail and you will need to repeat the action manually once the ASE reconnects.
 
-- Deployment of the 5G core
-- Updating the 5G core version
-- Updating SIM configuration
-- Updating NAT configuration
-- Updating service policy
-- Provisioning SIMs
+The **Sim overview** and **Sim Policy overview** blades display provisioning status of the resource in the site. This allows you to monitor the progress of provisioning actions. Additionally, the **Packet core control plane overview** displays the **Installation state** which can be used to monitor changes due to configuration actions.
 
-### Monitoring and troubleshooting during disconnects
+### ASE behavior after connectivity resumes
 
-While in disconnected mode, you cannot enable local monitoring authentication or sign in to the [distributed tracing](distributed-tracing.md) and [packet core dashboards](packet-core-dashboards.md) using Azure Active Directory. However, you can access both distributed tracing and packet core dashboards via local access if enabled. If you expect to need access to your local monitoring tools while the ASE is disconnected, you can change your authentication method to local usernames and passwords by following [Modify the local access configuration in a site](modify-local-access-configuration.md).
+Once ASE connectivity resumes, several features resume:
 
-Once the disconnect ends, log analytics on Azure updates with the stored data, excluding rate and gauge type metrics.
+- ASE management resumes immediately.
+- **Resource Health** is viewable immediately.
+- **Workbooks** is viewable immediately and populates for the disconnected duration.
+- **Kubernetes Cluster Overview** shows as **Online** after 10 minutes.
+- **Monitoring** tabs show metrics for sites after 10 minutes but don't populate stats for the disconnected duration.
+- **Kubernetes Arc Insights** shows new stats after 10 minutes but doesn't populate stats for the disconnected duration.
+- **Resource Health** views are viewable immediately.
+- [Workbooks](../update-center/workbooks.md) for the ASE are viewable immediately and populate for the disconnected duration.
 
 ## Next steps