Cloud Security
Why Global Secure Access should replace your VPN
Many companies still pay to maintain an access model built for a time when work happened in the office. If you already run Microsoft 365 and Entra ID, most of the foundation for the next step is already in place.
Take a look at what a typical mid-sized company still runs, just so people can reach internal applications.
VPN gateways or appliances, with support contracts and renewal cycles. Client licences. Firewall rules that have grown for years and that nobody really wants to touch. Tunnels between offices, the datacenter and Azure. Routing that only a few people fully understand. And a steady flow of tickets whenever the VPN client refuses to connect from a hotel or a customer site.
None of this was a bad decision. For a long time, this is simply how secure access worked. Applications lived in the network, so you connected people to the network.
But look at how your people work today. From home, from the train, from a customer’s office, from another country. What they actually need is access to a handful of specific applications. Not access to the network those applications happen to sit in.
So it’s worth asking the uncomfortable question: do we really still need to maintain all of this?
In many cases, the honest answer is no.
The access model is older than the way you work
A VPN does one thing well. It authenticates the user once and puts the device on the corporate network. From that moment on, the network is trusted. What the user can actually reach is decided by firewall rules and internal segmentation.
Think of it as handing someone the key to the building and relying on the lock of every office door inside. In customer environments, those inner locks are where things usually go wrong. The rules were written for different applications, different people and a different network. Over time, they only grow. Somebody needed access once, a rule was added, and nobody ever removed it.
The result is a pattern we see again and again. A contractor who needs one internal application gets access to the whole subnet it sits in. A user who needs a file share can also reach servers they have no business seeing. And every session is routed through a central gateway, often only for the traffic to head straight back out to Microsoft 365.
You are paying to recreate the office network wherever your people happen to be. That made sense when the network was the only place the applications could be reached. It makes much less sense now.
You already own most of the foundation
This is the part I think many IT leaders underestimate.
If you run Microsoft 365, every user already has an identity in Microsoft Entra ID. Often MFA is already enforced, and Conditional Access and Intune already decide whether a device is compliant before it may open Outlook, Teams or SharePoint. Every one of those sign-ins is already an access decision based on who the person is, which device they use and in what context.
And next to all of that, the VPN still runs as a second, parallel access system. With its own users, its own rules, its own logs and its own renewal date.
So the real question is not which VPN to buy next. It’s why you would keep a parallel remote-access stack at all, when you could extend the foundation you already have to your private applications.
That is what Microsoft Entra Private Access does.
Stop connecting users to networks
Private Access is part of Global Secure Access, Microsoft’s Security Service Edge offering, together with Microsoft Entra Internet Access. The idea behind it is simple:
Stop connecting users to networks. Give identities controlled access to exactly the applications they need.
In practice, it works like this. The user signs in with the same Entra identity they use for Microsoft 365. The Global Secure Access client on the device sends traffic for private applications to Microsoft’s service. A lightweight private network connector inside your network, in the datacenter or in Azure, picks up the request and connects to the application. The connector only makes outbound connections, so you do not need to open inbound ports to the internet for remote access.
The user does not land on a subnet. They reach a specific application, defined by its FQDN, IP address and ports. And that access is evaluated against Conditional Access on every request, not only once when someone signs in.
What changes for the business
- Less legacy infrastructure. No VPN concentrator to patch, size, fail over and renew. Once the last users have moved, the appliance and its support contract can go.
- Fewer VPN and firewall dependencies. Remote access no longer depends on tunnels and long firewall rule sets. Who may reach which application becomes an assignment in Entra ID that you can actually read and review.
- Less operational complexity. One access model for cloud and private applications. The same identities, the same Conditional Access policies, the same sign-in logs.
- Access based on identity, device and context. MFA, a compliant device, location and risk signals apply to the private connection itself. With Universal Continuous Access Evaluation, a revoked session or a change in risk takes effect within minutes, instead of when the VPN session expires.
- Application-level access instead of network access. A contractor gets the one application they need. When someone changes role or leaves, you remove an assignment, not a firewall rule nobody remembers.
- Secure work from anywhere. There is no separate “connect the VPN first” step. The same identity and device checks apply wherever people work.
- A gradual migration. You do not need a big-bang replacement. Users and applications move in stages, while the VPN is still there as a fallback.
The last point is usually what makes this realistic.
Quick Access is the bridge, not the destination
Microsoft’s documented path starts with Quick Access. You publish the same broad ranges your VPN reaches today, FQDNs, IP ranges and ports, assign them to a pilot group and attach a Conditional Access policy. From the user’s point of view, the applications simply keep working. From your point of view, access now goes through identity and device checks instead of a tunnel.
That is a good first step. It is not the goal.
If you stop at Quick Access, you have replaced the VPN product, but not the VPN model. Users still reach broad ranges, just through a different client. The real value comes when you use the traffic logs to split those ranges into individual applications, each with its own users and its own Conditional Access requirements. That is where access actually shrinks compared to what the VPN allowed.
In customer environments, we usually run it like this:
- Find out what is really accessed over the VPN today, by whom and over which protocols.
- Install private network connectors where the applications live, in the datacenter or in Azure.
- Move a pilot group to Quick Access, in parallel with the existing VPN, with Conditional Access applied from day one.
- After a few weeks of traffic logs without missing access, split the broad ranges into per-application access, starting with the applications that are best understood.
- Decommission the VPN gateway once the remaining edge cases are covered.
The trade-offs, honestly
This is not free, and it does not replace everything.
- Licensing. Full Private Access, including Quick Access and per-application access, requires the dedicated Global Secure Access licences or the Microsoft Entra Suite. The Microsoft traffic profile, which secures and accelerates access to Microsoft 365, is already included in Entra ID P1 or P2, and many customers have it without using it. Compare the licence against the full cost of the current model: appliances, support contracts, client licences, renewal cycles and the hours spent on firewall changes and VPN tickets.
- Clients and edge cases. The Global Secure Access client has to run on the devices. Unsupported operating systems and unusual protocols are the typical edge cases, and they usually decide when the VPN can finally be switched off. Decide early what happens to them.
- Not every tunnel is user access. Private Access replaces how people reach applications. Site-to-site connections that carry server-to-server traffic, such as replication or backups, remain a network decision. Some tunnels, though, only exist so users in one location can reach applications in another. Those are the candidates.
- A different dependency. Access now runs through Microsoft’s service instead of your own gateway. If your identities, email and collaboration already run on Microsoft, that dependency already exists. Still, plan how administrators reach critical systems if that path is ever unavailable.
What I would do
Don’t renew or expand the VPN by default. The next renewal date is a natural deadline for this decision.
Start with an honest look at your current access landscape:
- Which applications are reached over VPN or other private access paths today, and by whom?
- Which tunnels and firewall rules exist, and which of them are still needed?
- Which Microsoft licences and Conditional Access policies do you already have?
- Which applications can move first, and which edge cases have to stay for now?
The answers usually show that a large part of the access model can move to identity-based application access, step by step, on a foundation you already pay for.
If you want to do this with real data instead of assumptions, that is where our Secure Access Pilot starts. We select a first user group and its applications, configure Microsoft Entra Private Access with a Conditional Access model, and give you a rollout recommendation based on what actually happened.

