GSA coexistence with Netskope
Microsoft's edit ·
Microsoft's commit message in MicrosoftDocs/entra-docs · commit e0678bb · +7 −9 lines · also on GitHub
⋯ 9 unchanged lines
1010
ai-usage: ai-assisted
1111
---
1212
13
−# Security Service Edge (SSE) coexistence With Microsoft and Netskope
14
−
15
−Learn about Security Service Edge (SSE) coexistence with Microsoft and Netskope
13
+# Security Service Edge (SSE) coexistence with Microsoft and Netskope
1614
1715
In today's rapidly evolving digital landscape, organizations require robust, and unified solutions to ensure secure and seamless connectivity. Microsoft and Netskope offer complementary Secure Access Service Edge (SASE) capabilities that, when integrated, provide enhanced security and connectivity for diverse access scenarios.
1816
⋯ 101 unchanged lines
120118
1. Navigate to **Advanced Diagnostics** > **Health Check** and ensure no checks are failing.
121119
1. Right-click on **Netskope Client** > **Configuration**. Verify **Steering Configuration** matches the name of the configuration. If not, select the **Update** link.
122120
> [!NOTE]
123
− > If you experience `information troubleshooting` health check failures, see [Troubleshoot the Global Secure Access client](/entra/global-secure-access/troubleshoot-global-secure-access-client-diagnostics-health-check).
121
+ > To troubleshoot health check failures, see [Troubleshoot the Global Secure Access client](/entra/global-secure-access/troubleshoot-global-secure-access-client-diagnostics-health-check).
124122
125123
#### Test traffic flow
126124
⋯ 14 unchanged lines
141139
In this scenario, both clients handle traffic for separate private applications. The Global Secure Access client handles private applications in Microsoft Entra Private Access and the Netskope client handles private applications in Netskope Private Access. Netskope handles internet traffic.
142140
143141
> [!NOTE]
144
−> Known limitation – When the macOS Global Secure Access client is connected before the Netskope client Global Secure Access functionality is disrupted.
142
+> Known limitation – When the macOS Global Secure Access client is connected before the Netskope client, Global Secure Access functionality is disrupted.
145143
146144
### Microsoft Entra Private Access configuration
147145
⋯ 49 unchanged lines
197195
1. Navigate to **Advanced Diagnostics** > **Health Check** and ensure no checks are failing.
198196
1. Right-click on **Netskope Client** > **Configuration**. Verify **Steering Configuration** matches the name of the configuration created. If not, select the **Update** link.
199197
> [!NOTE]
200
− > For information troubleshooting health check failures: [Troubleshoot the Global Secure Access client: Health check - Global Secure Access | Microsoft Learn](/entra/global-secure-access/troubleshoot-global-secure-access-client-diagnostics-health-check).
198
+ > To troubleshoot health check failures, see [Troubleshoot the Global Secure Access client](/entra/global-secure-access/troubleshoot-global-secure-access-client-diagnostics-health-check).
201199
202200
#### Test traffic flow
203201
⋯ 16 unchanged lines
220218
In this scenario, Global Secure Access handles all Microsoft 365 traffic. Netskope Private Access handles Private application traffic and Netskope Internet Access handles Internet traffic.
221219
222220
> [!NOTE]
223
−> Known limitation – When the macOS Global Secure Access client is connected before the Netskope client Global Secure Access functionality is disrupted.
221
+> Known limitation – When the macOS Global Secure Access client is connected before the Netskope client, Global Secure Access functionality is disrupted.
224222
225223
### Microsoft Entra Microsoft Access configuration
226224
⋯ 46 unchanged lines
273271
1. Navigate to **Advanced Diagnostics** > **Health Check** and ensure no checks are failing.
274272
1. Right-click on **Netskope Client** > **Configuration**. Verify **Steering Configuration** matches the name of the configuration created. If not, select the **Update** link.
275273
> [!NOTE]
276
− > For information troubleshooting health check failures: [Troubleshoot the Global Secure Access client: Health check - Global Secure Access | Microsoft Learn](/entra/global-secure-access/troubleshoot-global-secure-access-client-diagnostics-health-check).
274
+ > To troubleshoot health check failures, see [Troubleshoot the Global Secure Access client](/entra/global-secure-access/troubleshoot-global-secure-access-client-diagnostics-health-check).
277275
278276
#### Test traffic flow
279277
⋯ 79 unchanged lines
359357
1. Navigate to **Advanced Diagnostics** > **Health Check** and ensure no checks are failing.
360358
1. Right-click on **Netskope Client** > **Configuration**. Verify **Steering Configuration** matches the name of the configuration created. If not, select the **Update** link.
361359
> [!NOTE]
362
− > For information troubleshooting health check failures: [Troubleshoot the Global Secure Access client: Health check - Global Secure Access | Microsoft Learn](/entra/global-secure-access/troubleshoot-global-secure-access-client-diagnostics-health-check).
360
+ > To troubleshoot health check failures, see [Troubleshoot the Global Secure Access client](/entra/global-secure-access/troubleshoot-global-secure-access-client-diagnostics-health-check).
363361
364362
#### Test traffic flow
365363
⋯ 7 unchanged lines
Microsoft's Markdown source from MicrosoftDocs/entra-docs, © Microsoft Corporation, under MIT. Changed lines with up to 3 unchanged lines around each; ChangeIntel kept this copy 10 Oct 05:03 UTC. The commit date is when the source changed, which can be hours or days before Learn published it.