Solution design
VPN replacement with Cloudflare Access and Tunnel
Replace broad network access with per-application identity, device posture, and outbound-only private connectivity. The practical goal is not just to remove a VPN client; it is to reduce implicit trust and make access easier to operate.
When This Pattern Fits
Use this pattern when users need access to private web apps, SSH/RDP, developer tools, dashboards, admin portals, or internal services without placing them on a broad private network. It is especially useful when VPN access has become too coarse, hard to audit, painful for contractors, or risky for privileged systems.
Good fitPrivate web apps, SSH, RDP, admin portals, developer tools, internal dashboards, partner access, and contractor access.
Needs design careThick client apps, legacy protocols, shared jump hosts, hardcoded IP allowlists, and apps that assume layer-3 network adjacency.
Keep VPN temporarilyUse coexistence while you discover dependencies, migrate high-value apps, and test failure modes.
Target Architecture
The cleanest architecture is per-application access through Cloudflare Access, with Cloudflare Tunnel providing outbound-only connectivity from the private environment to Cloudflare. Users authenticate through the corporate IdP, policies evaluate identity and device posture, and the origin remains private.
IdentityConnect Entra ID, Okta, Google Workspace, or another SAML/OIDC provider. Verify group claims before writing policy.
Application connectorRun Cloudflare Tunnel close to the private app. Prefer multiple connectors for availability and avoid inbound firewall exposure.
Access policyUse default-deny, reusable Access Groups, short session duration for sensitive apps, and explicit admin policies.
Device postureAdd WARP enrollment, OS version, disk encryption, serial number, certificate, or endpoint security checks where managed devices are required.
LoggingSend Access logs to the SIEM and review identity, decision, app, device posture, source location, and failure reason.
Recommended Rollout Sequence
I would avoid a big-bang VPN cutover. Start with a narrow workflow, prove the user experience, then migrate app by app.
1. InventoryList VPN users, private routes, apps, ports, owners, authentication method, business criticality, and current access groups.
2. Pick a pilot appChoose an app with a clear owner, web access if possible, low blast radius, and a small user group willing to test.
3. Publish with TunnelCreate the tunnel, map the private hostname, confirm DNS behavior, and ensure the origin is not exposed directly.
4. Add Access policyRequire the right IdP group, add posture for managed-device access, and set a session duration that matches app sensitivity.
5. Pilot and measureTrack login success, blocked attempts, latency, app errors, helpdesk tickets, and user feedback against the VPN baseline.
6. Expand by app groupMigrate apps in waves: admin portals, developer tools, internal dashboards, partner apps, then more sensitive systems.
Practical Policy Examples
Keep policies readable. The best design is usually a small set of reusable groups and a few app-specific exceptions.
Employee app
Group + managed device
Allow employees in the app owner group when device posture is healthy. Block everyone else by default.
Admin portal
Privileged group + short session
Require admin group membership, managed device posture, MFA at the IdP, and a shorter Access session.
Contractor access
Separate login path
Use a contractor IdP, partner IdP, or OTP with tight app scope, expiration date, and stricter review.
SSH/RDP
Protocol-specific access
Use Access for Infrastructure or browser-rendered access where appropriate, and avoid shared local credentials.
Migration Checklist
App ownerNamed owner, support contact, acceptable maintenance window, and rollback decision-maker.
User groupConfirmed IdP group, test users, blocked users, contractors, admins, and break-glass access.
ConnectivityTunnel health, connector redundancy, DNS record, private hostname, origin firewall, and service port.
PolicyDefault deny, allow rules, posture checks, session duration, service tokens if needed, and audit logging.
ValidationAllowed user succeeds, blocked user fails, disabled user fails, unmanaged device fails, and direct origin access fails.
OperationsHelpdesk runbook, SIEM visibility, dashboard view, rollback path, owner sign-off, and next wave plan.
Validation Tests
Do not call the migration complete after one successful login. Test positive and negative paths before removing the app from VPN access.
Allowed employeeCan authenticate, pass posture, reach the app, and complete the real workflow.
Wrong groupCan authenticate but receives a policy block with the expected log reason.
Unmanaged deviceFails posture if the app requires managed-device access.
Disabled userLoses access through IdP lifecycle and cannot reuse an old session beyond intended limits.
Origin bypassCannot reach the private origin directly from the Internet or an unauthorized network.
Common Pitfalls
Copying VPN groups blindlyVPN groups are often too broad. Rebuild access around app ownership and least privilege.
Skipping postureIdentity-only access may be fine for low-risk apps, but sensitive apps usually need device context.
No app ownerIf nobody owns the app, nobody can approve policy, test the workflow, or accept migration risk.
Forgetting non-web accessSSH, RDP, database tools, and thick clients may need separate patterns and user guidance.
Turning off VPN too earlyKeep coexistence until logs, helpdesk, rollback, and critical workflows are proven.
Rollback Plan
Rollback should be boring. Keep the previous VPN path available for the pilot group, document the DNS or policy change needed to revert, and define who can approve rollback. If a tunnel connector fails, users should either fail closed safely or use a known temporary path while the connector is restored.
Success Criteria
A good VPN replacement wave should show fewer broad network grants, clearer access logs, app-level policy ownership, lower reliance on shared VPN routes, and a user experience that is at least as easy as the old VPN. Only then would I move to the next application group.