What I like most about Zscaler Private Access is how it completely changes the way you connect to internal systems. With traditional VPNs, I always felt like I was opening the door to the entire network, even when I only needed one application. With ZPA, I’m only connected to what I actually need, and that makes a big difference in terms of both security and peace of mind.
From a test automation perspective, it has made my daily work much smoother. I used to deal with random VPN drops right in the middle of running tests or calling internal APIs, which was frustrating. With ZPA, the connection is much more stable. Once I’m logged in, I can access staging environments and APIs without interruptions, which saves time especially during debugging and long test runs.
On the UI/UX side, I like that it’s not something I constantly have to think about. The client is simple and runs quietly in the background. From an admin perspective, the interface can feel a bit complex at first, but once you get used to it, managing access policies becomes more structured and predictable.
Another thing I appreciate is how it integrates with identity providers. Access is based on roles and context, so I don’t have to chase permissions all the time. It’s clear, controlled, and feels more secure without adding extra friction.
In terms of performance, it was actually better than I expected. Compared to VPN, latency feels lower, especially when running API-heavy automated tests. That directly impacts our efficiency.
From a pricing/ROI perspective, it makes sense if you consider the bigger picture. It’s not just about replacing VPN, but reducing downtime, improving security, and saving engineering time. Fewer connection issues alone have already paid back a lot for us.
Support has also been reliable in my experience. When we had configuration questions early on, responses were helpful and fairly quick, which made the onboarding process easier.
I haven’t deeply used any AI-driven features, but the platform’s policy-based intelligence and access control logic already feel quite advanced. It’s clear that decisions are not just static rules but based on context like user identity and device state.
Overall, it’s been a more stable, secure, and less frustrating way to access internal resources compared to traditional approaches. Review collected by and hosted on G2.com.
One of the main challenges with Zscaler Private Access is the initial setup and configuration. The Zero Trust model is powerful, but it also comes with a learning curve. Defining policies, segmenting applications correctly, and making sure everything works as expected can take time, especially if you're coming from a traditional VPN setup.
From a day-to-day usage perspective, troubleshooting can sometimes be a bit difficult. When something doesn’t work, it’s not always immediately clear whether the issue is related to policies, identity provider integration, or network configuration. This can slow things down, especially when you're trying to quickly access an internal service during development or testing.
On the UI/UX side, while the end-user experience is simple, the admin interface can feel a bit overwhelming at first. There are many configuration layers, and it takes some time to fully understand how everything is connected.
Pricing could also be a consideration for smaller teams. While it delivers value in terms of security and stability, the cost might feel high if you're not fully utilizing all of its capabilities.
In terms of support, while generally helpful, response times can vary depending on the issue, and more complex cases may require some back-and-forth before getting fully resolved.
Lastly, while the platform has strong policy-based logic, I haven’t seen very visible or impactful AI-driven features in everyday use yet. Most of the intelligence still feels rule-based rather than adaptive.
Overall, none of these are deal-breakers, but they are things to consider, especially during the onboarding and early adoption phase. Review collected by and hosted on G2.com.
