
The predominant solution for secure remote access in the Microsoft ecosystem today is Always On VPN, which is based on traditional virtual private network (VPN) technology originally developed in the mid-1990s. Microsoft Entra Private Access, generally available since 2024, is part of Microsoft’s Global Secure Access (GSA) Security Service Edge (SSE) solution. Entra Private Access is an identity-centric Zero Trust Network Access (ZTNA) solution designed to replace traditional VPNs. It offers significantly improved security with granular resource access and minimal dependency on on-premises infrastructure. This article outlines where each solution fits best and how organizations can transition safely between them.
Last updated: November 9, 2026
Always On VPN
First introduced in Windows 10, Microsoft Always On VPN provides seamless, transparent, secure remote access using client-based VPN protocols such as Internet Key Exchange version 2 (IKEv2) and Secure Socket Tunneling Protocol (SSTP). When a VPN connection is established, a virtual network adapter is created, and an IP address is assigned to the interface to facilitate tunneled network communication with the internal network.
Architecture
Always On VPN requires substantial on-premises supporting infrastructure. In addition to the VPN servers themselves, administrators must deploy authentication servers (RADIUS or NPS) and certificate services (AD CS), and they must manage public TLS certificates for SSTP connections. Larger deployments may also require on-premises load balancers or cloud-based Global Server Load Balancing (GSLB) solutions, and additional configuration is needed to integrate Entra ID Conditional Access. Because this infrastructure must be publicly accessible by design, it is an attractive target for attackers. In addition, the complex infrastructure has many interdependencies, resulting in significant administrative overhead for network and security administrators.
Access Model
Most commonly, Always On VPN provides full access to the internal network. This is accomplished by configuring IP routing on the client so that internal network subnets are routed over the VPN tunnel. In this model, clients are often implicitly trusted once connected. After authentication and authorization, users receive full, unfettered access to the internal network across all protocols and ports. This level of access introduces significant security risk and does not adhere to modern Zero Trust principles. To address this, administrators must implement additional security controls internally (perimeter or DMZ firewalls) to restrict network access for Always On VPN clients.
Zero Trust Always On VPN?
Always On VPN supports traffic filters that can restrict network access and provide Zero Trust-like access. However, these controls exist only on the client side, so an attacker with administrative access to the endpoint can bypass them. They should not be considered a reliable way to enforce Zero Trust for Always On VPN connections.
Entra Private Access
Entra Private Access is a robust, cloud-based ZTNA service that provides granular access to on-premises resources. It requires installing the Global Secure Access client on endpoints and one or more Private Network connectors on-premises. Entra Private Access integrates deeply with Entra ID, so you can easily configure Conditional Access policies for any published resource, including multifactor authentication for legacy protocols such as SSH.
Limited Network Access
Unlike legacy VPNs, the Global Secure Access client does not create a virtual network interface. Instead, it operates as a filter driver in the Windows networking stack, intercepting and forwarding traffic bound for private resources. This eliminates the complexities of client IP address management, network routing, and firewalling. In addition, authentication and authorization are handled natively by Entra ID and Conditional Access.
Minimal Infrastructure
Entra Private Access is a cloud-based service with minimal on-premises infrastructure requirements. Administrators deploy only the Entra Private Network connector on one or more on-premises servers. The connector is a lightweight software agent that requires little post-deployment support, so the administrative burden is much lighter than with Always On VPN.
Key Differences at a Glance
The table below highlights the most important architectural, security, and operational differences to help determine which solution best fits your environment.
| Aspect | Always On VPN | Entra Private Access |
|---|---|---|
| Architecture | On-premises VPN gateways | Cloud-based service |
| Access model | Full network access via a routable IP address assigned to the endpoint | Per-resource Zero Trust Network Access (ZTNA); no full network access |
| Authentication | On-premises AD or Entra ID (AD-synced accounts only) | Entra ID (AD-synced or cloud-native) |
| Client software | Built-in or third-party | Global Secure Access client |
| Tunneling protocols | IKEv2, SSTP | gRPC |
| Network exposure | VPN servers must be exposed to the public internet | None; Private Network connectors require outbound access only |
| Granularity | All protocols and ports (default) | Application-level (FQDN, IP and port, IP range, CIDR blocks) |
| Conditional Access | Requires additional configuration | Native per-app enforcement |
| Device-based connectivity | Yes; device tunnel provides pre-logon connectivity | None |
| Infrastructure requirements | VPN servers, RADIUS servers, internal PKI, AD, load balancers, GSLB | Entra Private Network connector (minimum one server, two recommended for redundancy) |
| Device support | Windows only | Cross-platform (Windows, macOS, iOS, Android) |
| Licensing | Included in the Windows license | Additional per-user cost with Entra Suite or a standalone Entra Private Access license |
Advantages of Always On VPN for Domain-Joined Endpoints
Always On VPN integrates more naturally with classic Active Directory domain-joined Windows devices and includes features that Entra Private Access does not currently provide, including the following.
Device Tunnel Support
The Always On VPN device tunnel provides machine-based, pre-logon connectivity. It ensures access to on-premises authentication services (domain controllers) before the user signs in, which allows users to sign in without cached credentials (for example, new users) and streamlines password changes. It also ensures network access for complete Group Policy processing for remote users. Entra Private Access is user-based only and does not include device-based connectivity. The device tunnel is one of the most significant functional gaps between Always On VPN and Entra Private Access.
Note: Device-based connections are not available in Entra Private Access at the time of this writing, but Microsoft may add the feature in the future.
Windows Native Integration
Always On VPN uses the built-in Windows VPN client, which integrates deeply with the operating system. The Windows VPN client is mature and robust, supporting secure authentication with certificates or smart cards, and requires no additional client software. For Entra Private Access, administrators must deploy and manage a separate software component, the Global Secure Access client.
Full Network Access
The domain is a trust boundary, and domain-joined endpoints require broad network access to function. They must reach domain controllers using several protocols and many different ports. They must also connect to a variety of other internal resources, such as DNS servers, certification authorities (CAs), revocation servers (HTTP, OCSP, LDAP), systems management servers, file shares, printers, and more. Much of this access uses Remote Procedure Call (RPC) and Distributed COM (DCOM), which rely on ephemeral (dynamic) port ranges (49152-65535). Because these endpoints require access to so many resources, enforcing firewall policy to restrict access for remote domain-joined clients is challenging.
If your managed endpoints are primarily domain-joined and depend on pre-logon network connectivity, Always On VPN remains the more mature and feature-complete choice today.
Why Entra Private Access Is Ideal for Entra-Joined Devices
Entra Private Access is designed around a cloud-first, identity-centric Zero Trust model, and its client and device requirements align best with Entra-joined devices, including the following.
Client Requirements
The Global Secure Access client requires Windows devices to be Microsoft Entra joined or Microsoft Entra hybrid joined for full functionality. Microsoft Entra registered devices, such as personal devices, are also supported, but only for Private Access traffic, and this support is currently in preview. Domain-joined only (non-hybrid) devices are not supported. Unlike the native VPN client built into Windows, the Global Secure Access client is a separate piece of software that administrators must install and maintain.
Per-App Zero Trust
Entra Private Access controls access using FQDNs or IP addresses (individual addresses, ranges, or networks) and specific protocol and port combinations instead of full network routing. Per-app access aligns with the modern cloud-native device model by avoiding broad network exposure and evaluating every access request through Conditional Access, including device compliance, MFA for legacy protocols, and more. Unlike Always On VPN, the principle of least privilege is enforced at all times.
Simplified Management
Entra Private Access requires minimal on-premises supporting infrastructure. There’s no need for VPN servers, RADIUS servers, or certificate services for VPN authentication, because Entra Private Access natively uses Entra ID and Conditional Access.
Cross-Platform Support
Entra Private Access supports Windows clients (Pro and Enterprise editions) as well as macOS, iOS, and Android. Broad client support makes Entra Private Access a comprehensive secure remote access solution for all your managed endpoints.
Overall, Entra Private Access provides a cleaner, more secure, and lower-maintenance experience for organizations moving toward Entra-joined device fleets, especially when combined with Microsoft Intune for management and Conditional Access policies for enhanced security.
Licensing
Always On VPN and Entra Private Access use different licensing models.
Always On VPN
Always On VPN requires no per-user or per-device licensing. It’s included with the Windows license you already own.
Entra Private Access
Entra Private Access requires a separate license at an additional per-user cost. It’s included with the Microsoft Entra Suite license (about $12.00 per user per month) or available as a standalone Entra Private Access license (about $5.00 per user per month). Learn more about Microsoft Entra licensing.
Migration Path
Migrating from Always On VPN to Entra Private Access is low-risk with a phased approach. Plan the Entra Private Access deployment (client deployment, connector placement, Conditional Access policies, and so on), deploy it alongside Always On VPN, move users and applications over gradually, and then decommission the legacy VPN. Key steps include the following.
- Assess your resources, devices, and Entra ID licensing.
- Enable Entra Private Access, deploy at least two Private Network connectors on-premises, and install the Global Secure Access client on devices.
- Configure access rules. Begin with Quick Access to replicate VPN-like behavior.
- Run both solutions side by side. Pilot with a small group, migrate applications and users incrementally, and enforce Conditional Access, including MFA for sensitive applications.
- Phase out and decommission Always On VPN once stable.
This approach reduces infrastructure overhead, delivers granular Zero Trust security, and aligns with a cloud-first identity strategy.
Summary
Microsoft Always On VPN provides reliable remote access for Windows devices using protocols such as IKEv2 and SSTP. It remains the best choice for environments with traditional Active Directory domain-joined devices that require pre-logon connectivity and broad network access. However, Always On VPN requires substantial infrastructure and typically grants risky full network access.
Entra Private Access is the preferred solution for organizations adopting a cloud-first Zero Trust strategy with Entra-joined endpoints. Its per-application access model, native Conditional Access enforcement, reduced infrastructure footprint, and cross-platform support make it ideal for modern managed endpoints where least-privilege access and simplified operations are priorities.
In practice, many organizations benefit from running both solutions in parallel during a transition, using Always On VPN for domain-joined endpoints and Entra Private Access for Entra-joined devices. As device fleets and applications modernize, Entra Private Access can progressively replace legacy VPN infrastructure while improving security posture and reducing operational complexity.
Additional Information
Global Secure Access Client for Windows (Microsoft Learn)
Microsoft Entra Private Network Connectors (Microsoft Learn)
Microsoft Entra Private Access Intelligent Local Access (ILA)
Preventing Port Exhaustion on Entra Private Network Connector Servers
Microsoft Security Service Edge (SSE) Now Generally Available
Microsoft Entra Security Service Edge (SSE) on RunAs Radio
Ready to Modernize Your Remote Access Strategy?
Schedule a free one-hour consultation to review your current Always On VPN deployment, assess readiness for Entra Private Access, and identify a secure, practical migration path tailored to your environment. I’ll cover architecture considerations, device requirements, licensing implications, and common pitfalls. There’s no obligation. Fill out the form below, and I’ll personally follow up to schedule your free consultation.








