GSA remote network connectivity
Microsoft's edit ·
Microsoft's commit message in MicrosoftDocs/entra-docs · commit 98e12b9 · +4 −4 lines · also on GitHub
⋯ 37 unchanged lines
3838
3939
## Supported traffic forwarding profiles
4040
41
−Remote networks don't support all the same traffic forwarding profiles as the Global Secure Access client. The following table summarizes which connectivity methods support each profile:
41
+Remote networks support different traffic forwarding profiles for acquiring traffic. Traffic forwarding profiles control which traffic is routed through Global Secure Access. Security profiles (such as the baseline profile) control what policies are applied to that acquired traffic.
4242
4343
| Traffic forwarding profile | Global Secure Access client | Remote network |
4444
|---|---|---|
4545
| **Microsoft traffic** | ✅ Supported | ✅ Supported |
46
−| **Internet Access** | ✅ Supported | ❌ Not supported as a traffic forwarding profile |
46
+| **Internet Access** | ✅ Supported | ✅ Supported |
4747
| **Private Access** | ✅ Supported | ❌ Not supported |
4848
4949
> [!IMPORTANT]
50
−> Only the **Microsoft traffic** forwarding profile can be assigned to remote networks. **Private Access** and **Internet Access** traffic forwarding profiles require the Global Secure Access client installed on end-user devices. For more information, see [Understand traffic forwarding profiles](concept-traffic-forwarding.md).
50
+> The **Microsoft traffic** and **Internet Access** traffic forwarding profiles can be assigned to remote networks. The **Private Access** traffic forwarding profile requires the Global Secure Access client installed on end-user devices. For more information, see [Assign a traffic profile to a remote network](how-to-assign-traffic-profile-to-remote-network.md) and [Understand traffic forwarding profiles](concept-traffic-forwarding.md).
5151
52
−Although the Internet Access traffic forwarding profile is client-only, you can still apply Internet Access security policies (such as web content filtering) to remote network traffic. Use the [baseline security profile](how-to-apply-security-policies-remote-network.md) to enforce these policies at the tenant level for all traffic routed through Global Secure Access, including remote network traffic. User-aware Conditional Access policies for Internet Access require the Global Secure Access client.
52
+Once traffic is acquired through a forwarding profile, you apply security policies to it using security profiles. The [baseline security profile](how-to-apply-security-policies-remote-network.md) enforces policies at the tenant level for all traffic routed through Global Secure Access, including remote network traffic. User-aware security profiles linked to Conditional Access policies require the Global Secure Access client.
5353
5454
## Why remote network connectivity is important for you?
5555
Maintaining security of a corporate network is increasingly difficult in a world of remote work and distributed teams. Security Service Edge (SSE) promises a world of security where customers can access their corporate resources from anywhere in the world without needing to back haul their traffic to headquarters.
⋯ 118 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 06:20 UTC. The commit date is when the source changed, which can be hours or days before Learn published it.