GSA known limitations
Microsoft's edit ·
Microsoft's commit message in MicrosoftDocs/entra-docs · commit 1a2c065 · +3 −4 lines · also on GitHub
⋯ 4 unchanged lines
55
author: HULKsmashGithub
66
ms.topic: reference
77
ms.author: jayrusso
8
−ms.date: 11/07/2025
8
+ms.date: 02/24/2026
99
ms.custom: agent-id-ignite
1010
1111
⋯ 140 unchanged lines
152152
return "PROXY 10.1.0.10:8080"; // forward the connection to the proxy
153153
}
154154
```
155
−If a direct internet connection isn't possible, configure the client to connect to the Global Secure Access service through a proxy. For example, set the `grpc_proxy` system variable to match the value of the proxy, such as `http://proxy:8080`.
156
−
157
−To apply the configuration changes, restart the Global Secure Access client Windows services.
155
+> [!IMPORTANT]
156
+> The Global Secure Access client doesn't support connecting through an outbound proxy. If the client is behind an outbound proxy, configure the PAC file exclusions as described previously to bypass the proxy for Global Secure Access traffic.
158157
159158
#### Packet injection
160159
The client only tunnels traffic sent using sockets. It doesn't tunnel traffic injected to the network stack using a driver (for example, some of the traffic generated by Network Mapper (Nmap)). Injected packets go directly to the network.
⋯ 120 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 9 Oct 22:20 UTC. The commit date is when the source changed, which can be hours or days before Learn published it.