How to investigate the Global Secure Access remote network connectivity
In brief
The article now distinguishes tunnel and BGP connectivity scenarios and adds investigation steps, licensing requirements, least-privilege roles, and Microsoft Graph permissions for viewing and managing signals and alerts.
What Entra admins need to know
Administrators have clearer guidance for troubleshooting remote network health issues and determining the access required to view or manage related alerts.
This editorial summary was generated by AI from the documentation changes. Verify important details in the full Microsoft Learn article.
Documentation change
The comparison below shows only the changed extract. Use the full-page view for complete context.
How to use Microsoft Entra health monitoring signals and alertsHow to investigate Microsoft Entra health monitoring signals and alerts
This article describes the health metrics related to remote network connectivity and provides steps to troubleshoot potential problems. Tunnel connectivity and BGP connectivity are separate health scenarios, but this article covers them together because BGP depends on an established IPsec tunnel.
This article covers two scenarios:
- Global Secure Access requiring remote network tunnel connectivity
Prerequisites
There are different roles, permissions, and license requirements to view health monitoring signals and to configure and receive alerts. We recommend using a role with least privilege access to align with the Zero Trust guidance.
A tenant with a Microsoft Entra P1 or P2 license is required to view the Microsoft Entra health scenario monitoring
signalssignals.A tenant with both a non-trial Microsoft Entra P1 or P2 license and at least 100 monthly active users is required to view alerts and receive alert notifications.
A tenant with a Microsoft Entra Global Secure Access license is required. For details, see the licensing section of What is Global Secure Access?.
The Reports Reader role is the least privileged role required to view scenario monitoring
signals.signals, alerts, and alert configurations.The Helpdesk Administrator is the least privileged role required to update alerts and update alert notification configurations.
The
HealthMonitoringAlert.Read.Allpermission is required to view the alerts using the Microsoft Graph API.The
HealthMonitoringAlert.ReadWrite.Allpermission is required to view and modify the alerts using the Microsoft Graph API.For a full list of roles, see
Least privileged role by taskLeast privileged role by task.You must be assigned the Global Secure Access Administrator
,or Security Administrator role to access remote network logs.
Investigate the signals and alerts
To investigate a signal, gatherStart your investigation by identifying whether the following data:alert is for tunnel connectivity or BGP connectivity. Then compare the alert timeframe and affected remote networks with the remote network health and audit logs.
View the details of the alert.
- In the Microsoft Entra admin center, review the
metricssignal graph, alert timeframe, anddetails of theaffectedentities.remote networks. For more information, seeInvestigate the alert and signalsInvestigate the signals and alerts.
- For Microsoft Graph guidance, see Microsoft Graph health monitoring overview.
- In the Microsoft Entra admin center, review the
Sign
intoin to the Microsoft Entra admin center as at least aReports ReaderReports Reader.Browse to Entra ID > Monitoring & health > Health. The page opens to the Service Level Agreement (SLA) Attainment page.
Select the Health Monitoring tab.
Select the Global Secure Access requiring remote network tunnel connectivity
scenario.or Global Secure Access requiring remote network BGP connectivity scenario, and then select an active alert.:::image type="content" source="media/howto-investigate-remote-networks-scenario-signals/remote-network-border-gateway-protocol-alert.png" alt-text="Screenshot of the Global Secure Access remote network BGP connectivity scenario with one active alert." lightbox="media/howto-investigate-remote-networks-scenario-signals/remote-network-border-gateway-protocol-alert.png":::
Review the remote network health logs.
- For a tunnel alert, look for Tunnel disconnected events for the affected remote network, source IP address, and destination IP address.
- For a BGP alert, look for BGP disconnected events. Review the BGP Routes Advertised Count in the corresponding Remote network alive events.
- Use Remote network alive events to compare sent and received bytes before and during the alert.
Review
your Remotethe Global Secure Access audit logs for recent changes to the affected remote network, device link, IPsec configuration, or traffic profile assignment.:::image type="content" source="media/howto-investigate-remote-networks-scenario-signals/global-secure-access-audit-logs.png" alt-text="Screenshot of audit logs filtered to the Global Secure Access service." lightbox="media/howto-investigate-remote-networks-scenario-signals/global-secure-access-audit-logs.png":::
If you need longer retention or correlation, export the remote network health logs to Log Analytics and analyze them with a workbook.
Understand the signals
Tunnel and BGP alerts represent different layers of remote network health logs.connectivity:
How to use the remote network health logs - Global Secure Access | Microsoft LearnThe tunnel connectivity signal tracks whether IPsec tunnels are connected or disconnected. If the tunnel is disconnected, BGP can't exchange routes over that tunnel.- The BGP connectivity signal tracks whether the BGP session is connected and exchanging route information over an established tunnel. An IPsec tunnel can remain connected while BGP is disconnected.
A spike in disconnected tunnels or BGP sessions can indicate a CPE, internet service provider, configuration, or Global Secure Access edge connectivity problem. Compare the alert start time with remote network health events, audit logs, and planned network maintenance.
Mitigate common issues
The following common issues can cause a tunnel or BGP connectivity alert. This list isn't exhaustive, but it provides a starting point for your investigation.
One or more IPsec tunnels are disconnected
A tunnel can disconnect because of a CPE outage, internet connectivity problem, or mismatch between the CPE and Global Secure Access IPsec configuration.
To investigate and mitigate the issue:
- In the alert, identify the affected remote network and alert start time.
In the remote network health logs, filter by the remote network ID. Identify Tunnel disconnected events and note the source and destination IP address pair.Configure diagnostic settings to export logs.
for the matching tunnel. Confirm that the public IP addresses, IPsec parameters, shared secret or certificate, and tunnel endpoints match the Global Secure Access device link configuration.AnalyzeCheck the CPE status and logswith a workbook.Review the audit
logs.logs for changes to the remote network or device link near the alert start time.- Restore CPE or internet connectivity, or correct the mismatched configuration.
- Confirm that a Tunnel connected event appears and that sent and received bytes resume in subsequent Remote network alive events.
The IPsec tunnel is connected, but BGP is disconnected
The underlying tunnel can remain connected while the BGP neighbor relationship is down. In this state, the remote network might not exchange the routes that are required to forward traffic.
How to access Global Secure Access audit logs (preview) - Global Secure Access | Microsoft LearnConfirm that the remote network health logs show Tunnel connected for the affected source and destination IP address pair.
To investigate and mitigate the issue:
Connectivity is intermittent or depends on a single tunnel
A remote network with one tunnel has no alternate path during CPE, ISP, or Global Secure Access edge maintenance or failure.
To investigate and mitigate the issue:
- Review the health logs for repeated tunnel or BGP disconnect and reconnect events.
- Confirm whether the remote network has redundant tunnels.
- Configure at least two IPsec tunnels per location. Use zone redundancy or a secondary geographic remote network based on your availability requirements.
- Configure tunnel weighting for active-active or active-standby routing.
- Use BGP for dynamic route learning. If your CPE doesn't support BGP, configure static routes with appropriate metrics.
- Export remote network health logs to Log Analytics and create alert rules for tunnel and BGP failures.
For redundancy and failover guidance, see Enhance remote network resilience.
Related content
@@ -2,8 +2,9 @@ title: How to investigate the Global Secure Access remote network connectivity description: Learn how to monitor and troubleshoot remote network connectivity using Microsoft Entra Health monitoring. ms.topic: how-to-ms.date: 11/18/2025+ms.date: 09/14/2026 ms.reviewer: gauthamca+ai-usage: ai-assisted # Customer intent: As an IT admin, I want to learn how to monitor and troubleshoot remote network connectivity using Microsoft Entra Health monitoring. ---@@ -16,10 +17,10 @@ To learn more about how Microsoft Entra Health works, see: - [What is Microsoft Entra Health?](/entra/identity/monitoring-health/concept-microsoft-entra-health) -- [How to use Microsoft Entra health monitoring signals and alerts](/entra/identity/monitoring-health/howto-use-health-scenario-alerts)+- [How to investigate Microsoft Entra health monitoring signals and alerts](/entra/identity/monitoring-health/howto-investigate-health-scenario-alerts)++This article describes the health metrics related to remote network connectivity and provides steps to troubleshoot potential problems. Tunnel connectivity and BGP connectivity are separate health scenarios, but this article covers them together because BGP depends on an established IPsec tunnel. -This article describes the health metrics related to remote network connectivity and provides steps to troubleshoot potential problems.- This article covers two scenarios: - Global Secure Access requiring remote network tunnel connectivity@@ -31,58 +32,111 @@ This article covers two scenarios: ## Prerequisites -There are different roles, permissions, and license requirements to view health monitoring signals and to configure and receive alerts. We recommend using a role with least privilege access to align with the [Zero Trust guidance](/security/zero-trust/zero-trust-overview).+There are different roles, permissions, and license requirements to view health monitoring signals and to configure and receive alerts. We recommend using a role with least privilege access to align with the [Zero Trust guidance](/security/zero-trust/zero-trust-overview).++- A tenant with a [Microsoft Entra P1 or P2 license](/entra/fundamentals/get-started-premium) is required to *view* the Microsoft Entra health scenario monitoring signals.+- A tenant with both a non-trial [Microsoft Entra P1 or P2 license](/entra/fundamentals/get-started-premium) *and* at least 100 monthly active users is required to *view alerts* and *receive alert notifications*.++- A tenant with a Microsoft Entra Global Secure Access license is required. For details, see the licensing section of [What is Global Secure Access?](/entra/global-secure-access/overview-what-is-global-secure-access).++- The [Reports Reader](/entra/identity/role-based-access-control/permissions-reference#reports-reader) role is the least privileged role required to *view scenario monitoring signals, alerts, and alert configurations*.++- The [Helpdesk Administrator](/entra/identity/role-based-access-control/permissions-reference#helpdesk-administrator) is the least privileged role required to *update alerts* and *update alert notification configurations*.++- The `HealthMonitoringAlert.Read.All` permission is required to *view the alerts using the Microsoft Graph API*.+- The `HealthMonitoringAlert.ReadWrite.All` permission is required to *view and modify the alerts using the Microsoft Graph API*.++- For a full list of roles, see [Least privileged role by task](/entra/identity/role-based-access-control/delegate-by-task#microsoft-entra-health-least-privileged-roles).++- You must be assigned the [Global Secure Access Administrator](/entra/identity/role-based-access-control/permissions-reference#global-secure-access-administrator) or [Security Administrator](/entra/identity/role-based-access-control/permissions-reference#security-administrator) role to access remote network logs.++## Investigate the signals and alerts++Start your investigation by identifying whether the alert is for tunnel connectivity or BGP connectivity. Then compare the alert timeframe and affected remote networks with the remote network health and audit logs.++1. View the details of the alert.++ - In the [Microsoft Entra admin center](https://entra.microsoft.com/), review the signal graph, alert timeframe, and affected remote networks. For more information, see [Investigate the signals and alerts](howto-investigate-health-scenario-alerts.md#investigate-the-signals-and-alerts).+ - For Microsoft Graph guidance, see [Microsoft Graph health monitoring overview](/graph/api/resources/healthmonitoring-overview?view=graph-rest-beta&preserve-view=true).++1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com/) as at least a [Reports Reader](/entra/identity/role-based-access-control/permissions-reference#reports-reader).++1. Browse to **Entra ID** > **Monitoring & health** > **Health**. The page opens to the Service Level Agreement (SLA) Attainment page.++1. Select the **Health Monitoring** tab.++1. Select the **Global Secure Access requiring remote network tunnel connectivity** or **Global Secure Access requiring remote network BGP connectivity** scenario, and then select an active alert.++ :::image type="content" source="media/howto-investigate-remote-networks-scenario-signals/remote-network-border-gateway-protocol-alert.png" alt-text="Screenshot of the Global Secure Access remote network BGP connectivity scenario with one active alert." lightbox="media/howto-investigate-remote-networks-scenario-signals/remote-network-border-gateway-protocol-alert.png"::: -- A tenant with a [Microsoft Entra P1 or P2 license](/entra/fundamentals/get-started-premium) is required to *view* the Microsoft Entra health scenario monitoring signals+1. Review the [remote network health logs](/entra/global-secure-access/how-to-remote-network-health-logs?tabs=microsoft-entra-admin-center). -- A tenant with Microsoft Entra Global Secure Access license is required. For details, see the licensing section of [What is Global Secure Access?](/entra/global-secure-access/overview-what-is-global-secure-access)- -- The [Reports Reader](/entra/identity/role-based-access-control/permissions-reference#reports-reader) role is the least privileged role required to *view scenario monitoring signals.*+ - For a tunnel alert, look for **Tunnel disconnected** events for the affected remote network, source IP address, and destination IP address.+ - For a BGP alert, look for **BGP disconnected** events. Review the **BGP Routes Advertised Count** in the corresponding **Remote network alive** events.+ - Use **Remote network alive** events to compare sent and received bytes before and during the alert. -- The HealthMonitoringAlert.Read.All permission is required to *view the alerts using the Microsoft Graph API*.+1. Review the [Global Secure Access audit logs](/entra/global-secure-access/how-to-access-audit-logs) for recent changes to the affected remote network, device link, IPsec configuration, or traffic profile assignment. -- For a full list of roles, see [Least privileged role by task](/entra/identity/role-based-access-control/delegate-by-task#monitoring-and-health---audit-and-sign-in-logs).+ :::image type="content" source="media/howto-investigate-remote-networks-scenario-signals/global-secure-access-audit-logs.png" alt-text="Screenshot of audit logs filtered to the Global Secure Access service." lightbox="media/howto-investigate-remote-networks-scenario-signals/global-secure-access-audit-logs.png"::: -- You must be assigned the [Global Secure Access Administrator](/entra/identity/role-based-access-control/permissions-reference#global-secure-access-administrator), or [Security Administrator](/entra/identity/role-based-access-control/permissions-reference#security-administrator) role to access remote network logs.+1. If you need longer retention or correlation, [export the remote network health logs](/entra/global-secure-access/how-to-remote-network-health-logs#configure-diagnostic-settings-to-export-logs) to Log Analytics and [analyze them with a workbook](/entra/global-secure-access/how-to-remote-network-health-logs#analyze-logs-with-a-workbook). -## Investigate the signals+## Understand the signals -To investigate a signal, gather the following data:+Tunnel and BGP alerts represent different layers of remote network connectivity: -1. View the details of the alert.+- The tunnel connectivity signal tracks whether IPsec tunnels are connected or disconnected. If the tunnel is disconnected, BGP can't exchange routes over that tunnel.+- The BGP connectivity signal tracks whether the BGP session is connected and exchanging route information over an established tunnel. An IPsec tunnel can remain connected while BGP is disconnected. - - In the [Microsoft Entra admin center](https://entra.microsoft.com/), review the metrics and details of the affected entities. For more information, see [Investigate the alert and signals](/entra/identity/monitoring-health/howto-use-health-scenario-alerts#investigate-the-alert-and-signals).+A spike in disconnected tunnels or BGP sessions can indicate a CPE, internet service provider, configuration, or Global Secure Access edge connectivity problem. Compare the alert start time with remote network health events, audit logs, and planned network maintenance. - <!-- -->+## Mitigate common issues - - For Microsoft Graph guidance, see [Microsoft Graph health monitoring overview](/graph/api/resources/healthmonitoring-overview?view=graph-rest-beta&preserve-view=true).+The following common issues can cause a tunnel or BGP connectivity alert. This list isn't exhaustive, but it provides a starting point for your investigation. -<!-- -->+### One or more IPsec tunnels are disconnected -2. Sign into the [Microsoft Entra admin center](https://entra.microsoft.com/) as at least a [Reports Reader](https://github.com/MicrosoftDocs/entra-docs/blob/c5d27bbda734933549480ccf46deffbeeed01bc7/docs/identity/role-based-access-control/permissions-reference.md#reports-reader).+A tunnel can disconnect because of a CPE outage, internet connectivity problem, or mismatch between the CPE and Global Secure Access IPsec configuration. - - Browse to **Entra ID** \> **Monitoring & health** \> **Health**. The page opens to the Service Level Agreement (SLA) Attainment page.+To investigate and mitigate the issue: - - Select the **Health Monitoring** tab.+1. In the alert, identify the affected remote network and alert start time.+1. In the remote network health logs, filter by the remote network ID. Identify **Tunnel disconnected** events and note the source and destination IP address pair.+1. Check the CPE status and logs for the matching tunnel. Confirm that the public IP addresses, IPsec parameters, shared secret or certificate, and tunnel endpoints match the Global Secure Access device link configuration.+1. Review the audit logs for changes to the remote network or device link near the alert start time.+1. Restore CPE or internet connectivity, or correct the mismatched configuration.+1. Confirm that a **Tunnel connected** event appears and that sent and received bytes resume in subsequent **Remote network alive** events. - - Select the **Global Secure Access remote network connectivity** scenario.+### The IPsec tunnel is connected, but BGP is disconnected -3. Review your Remote network health logs.+The underlying tunnel can remain connected while the BGP neighbor relationship is down. In this state, the remote network might not exchange the routes that are required to forward traffic. - - [How to use the remote network health logs - Global Secure Access \| Microsoft Learn](/entra/global-secure-access/how-to-remote-network-health-logs?tabs=microsoft-entra-admin-center)+To investigate and mitigate the issue: -4. Configure diagnostic settings to export logs.+1. Confirm that the remote network health logs show **Tunnel connected** for the affected source and destination IP address pair.+1. Look for **BGP disconnected** events. Check the **BGP Routes Advertised Count** in **Remote network alive** events for the affected remote network.+1. On the CPE, verify the BGP neighbor IP addresses, autonomous system numbers, and route advertisement configuration.+1. Review recent CPE and Global Secure Access configuration changes.+1. Correct the BGP configuration or restart the affected BGP session according to your CPE vendor's guidance.+1. Confirm that a **BGP connected** event appears. Then confirm that the advertised route count returns to its expected value in subsequent **Remote network alive** events. - - [What are remote network health logs](/entra/global-secure-access/how-to-remote-network-health-logs?#configure-diagnostic-settings-to-export-logs)+### Connectivity is intermittent or depends on a single tunnel -5. Analyze logs with a workbook.+A remote network with one tunnel has no alternate path during CPE, ISP, or Global Secure Access edge maintenance or failure. - - [What are remote network health logs?](/entra/global-secure-access/how-to-remote-network-health-logs#analyze-logs-with-a-workbook)+To investigate and mitigate the issue: -6. Review audit logs.+1. Review the health logs for repeated tunnel or BGP disconnect and reconnect events.+1. Confirm whether the remote network has redundant tunnels.+1. Configure at least two IPsec tunnels per location. Use zone redundancy or a secondary geographic remote network based on your availability requirements.+1. Configure tunnel weighting for active-active or active-standby routing.+1. Use BGP for dynamic route learning. If your CPE doesn't support BGP, configure static routes with appropriate metrics.+1. Export remote network health logs to Log Analytics and create alert rules for tunnel and BGP failures. - - [How to access Global Secure Access audit logs (preview) - Global Secure Access \| Microsoft Learn](/entra/global-secure-access/how-to-access-audit-logs)+For redundancy and failover guidance, see [Enhance remote network resilience](/entra/global-secure-access/remote-network-resilience). -Related content+## Related content - [Understand remote network connectivity](/entra/global-secure-access/concept-remote-network-connectivity)+- [Use remote network health logs](/entra/global-secure-access/how-to-remote-network-health-logs)+- [Enhance remote network resilience](/entra/global-secure-access/remote-network-resilience) 