← Back to All Articles
Microsoft Azure

Microsoft Entra Global Secure Access: Cloud SSE, Private Access (ZTNA), and Internet Access

Replacing legacy corporate VPNs and fragmented web proxies with Microsoft Entra Global Secure Access (SSE) for identity-centric ZTNA (Private Access) and M365/Internet protection.

·10 min read·
#Global Secure Access#SSE#Zero Trust Network#Entra Private Access#Entra Internet Access#M365 E3
Microsoft Entra Global Secure Access: Cloud SSE, Private Access (ZTNA), and Internet Access

Executive Summary and Network Access Context

Even with mature Conditional Access and App Proxy controls, users still relied on full-tunnel legacy VPNs to access internal SMB/RDP servers and disconnected proxy appliances for Microsoft 365 egress. Introduced in July 2023, Microsoft Entra Global Secure Access merged identity evaluation directly with packet steering via Entra Private Access (ZTNA) and Entra Internet Access (SWG).

From an architectural evolution standpoint, this foundational design connects directly to modern platform controls. Unveiled alongside the Azure AD to Microsoft Entra ID rebranding in July 2023, Global Secure Access (Microsoft SSE) powers modern identity-aware network perimeters and M365 Compliant Network checks.

Trust Boundaries, Traffic Flows, and Design Principles

  • Microsoft Entra Private Access evolves Azure AD Application Proxy beyond HTTP/HTTPS to guard arbitrary TCP/UDP private ports (RDP, SSH, SMB, internal ERPs) behind per-app Conditional Access.
  • Microsoft Entra Internet Access applies Source IP Restoration and Universal Tenant Restrictions to neutralize stolen-token replay and unsanctioned tenant data egress.
  • A lightweight Global Secure Access Client routes authorized flows securely to Microsoft global PoPs without saturating central datacenter VPN concentrators.
  • Management and application ingress must avoid raw public ports (RDP 3389, SSH 22) by routing through Private Endpoints, Azure Bastion, or SSE tunnels backed by symmetric UDR egress inspection.

Prerequisites, Network Dependencies, and RBAC Requirements

  • Licensing: Global Secure Access for Microsoft 365 traffic is covered with Entra ID P1 (M365 E3/E5); full Entra Private Access and Internet Access require Microsoft Entra Suite or standalone add-on licensing.
  • RBAC & Connectors: Requires Global Secure Access Administrator role and outbound-only Private Network Connectors installed on internal Windows servers.
  • Routing Caution: Cleanly partition private CIDR/FQDN targets away from legacy VPN client drivers to avoid local traffic loops.

Technical Verification, Access Controls, and Telemetry

PowerShell Network Posture and Configuration Check

Validating GSA Windows client services, connector health, and Graph forwardingProfiles configuration:

  • Execution Environment and Prerequisites: Requires Microsoft.Graph.
  • Least Privilege and Operation Separation: Run with scoped Least-privilege Graph `.Read.All` scopes (delegated admin role only for writes) privileges. All statements above are **read-only (Get-*/Test-*/Search-*)** verification checks making no direct configuration edits; still validate module/network prerequisites in a test cohort first.
  • Security Control Mapped and Boundary Note: Verifies active policy state and guards against silent drift or mis-scoped rollouts without blind production changes.
powershell
# 1. Inspect Global Secure Access Windows client services on managed endpoint
Get-Service -Name "GlobalSecureAccess*" -ErrorAction SilentlyContinue | Select-Object Name, DisplayName, Status, StartType

# 2. Check Private Network Connector service state on internal connector host
Get-Service -Name "WAPCSvc", "MicrosoftEntraPrivateNetwork*" -ErrorAction SilentlyContinue | Select-Object Name, Status

# 3. Query Global Secure Access traffic forwarding profiles via Microsoft Graph
Connect-MgGraph -Scopes "NetworkAccess.Read.All"
Invoke-MgGraphRequest -Method GET -Uri "https://graph.microsoft.com/v1.0/networkAccess/forwardingProfiles" |
  Select-Object -ExpandProperty value | Select-Object id, name, state, trafficForwardingType

Network Traffic Telemetry and KQL Verification Query

KQL query auditing Entra SigninLogs evaluated through Global Secure Access compliant network signals:

kql
// Execution Scope: Read-only hunting/audit query (Log Analytics Reader / Security Reader)
// Data Source: Microsoft Entra ID Diagnostic Settings -> Log Analytics / Microsoft Sentinel (SigninLogs / AuditLogs)
SigninLogs
| where TimeGenerated > ago(14d)
| extend NetworkLocation = tostring(NetworkLocationDetails)
| where NetworkLocation has "compliantNetwork" or ConditionalAccessPolicies has "Compliant network"
| project TimeGenerated, UserPrincipalName, AppDisplayName, IPAddress, ResultType, NetworkLocation
| summarize GsaSignIns = count() by AppDisplayName, ResultType
| order by GsaSignIns desc

Critical Architectural Assessment, Outage Risks, and Rollback Strategy

  • Enabling Every Forwarding Profile Tenant-Wide on Day One: Always sequence deployment starting with Microsoft 365 + targeted Private Access Quick Access lists before touching full Internet egress.
  • Leaving Universal Tenant Restrictions Unconfigured: Without tenant restrictions enabled inside the Microsoft 365 profile, users on managed laptops can still exfiltrate files into personal M365 tenants.
  • Risks Mitigated vs. Residual Limitations: Private Endpoints, Azure Bastion, Azure Firewall, and Entra Global Secure Access eliminate direct public RDP/SSH exposure, lateral L3 VPN traversal, and unrestricted internet egress; they do not mitigate application-layer exploits (SQLi, SSRF) traversing authorized tunnels, compromised local endpoint binaries, or overly permissive spoke-to-spoke NSG rules.
  • New Dependencies and Production Failure Modes: Connectivity relies on consistent Private DNS Zone linking, symmetric UDR paths, and healthy endpoint SSE clients/connectors. Misconfigured 0.0.0.0/0 routing loops or missing private DNS zones instantly sever VM and hybrid application traffic in production.
  • Rollback and Pilot Validation Procedure: Validate firewall rules, NSG priorities, and SSE forwarding profiles against a canary VNet or pilot cohort first; maintain scripted Az.Network UDR/NSG snapshots and SSE bypass toggles to restore routing swiftly.

Verified Primary Sources & Open-Source Repositories

This architectural guide was cross-corroborated against the official advisories, Microsoft Learn docs, and open-source PowerShell / KQL repositories below.

Multi-Channel Distribution Summary (X & LinkedIn Draft)

Toggle X (Twitter) & LinkedIn sharing drafts
X (Twitter) Draft

Retiring traditional VPNs with Microsoft Entra Global Secure Access (SSE), Private Access ZTNA, and Internet Access. #EntraID #SSE #ZeroTrust

LinkedIn Draft

Identity-Centric Network Security: Implementing Entra Private Access for per-app ZTNA and shutting down token-replay egress gaps with Global Secure Access.