This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
At my workplace, we are using Private Access with the Global Secure Access Client and we are able to access private resources remotely. However, we are facing issues with transitioning to on-location routing. We have created a conditional access policy to block the quick access app when at our location, but it blocks the resource altogether. We are looking for a seamless way to transition to on-location routing without having to pause the GSAC. Is there a way to configure our setup so this is possible? Maybe through a conditional access policy?
Hi @ahunt , I think a conditional access policy is your best option for this. It's more customizable and allows for more control. Anything else would be over-complicated and might not work reliably. Let me know if you need any help setting it up or have any questions about it!
If this answer helps you please mark "Accept Answer" so other users can reference it.
Thank you,
James
I have tried to set one up. After enabling this policy it blocks application segment when on the local network. The flow would look like this to reproduce the issue.
10.0.0.2:443 is configured with quick access, but is reachable at our location without quick access.
I'm not great at describing it, I hope this is enough information to understand. Essentially we want to use Quick Access when users are remotely connecting, and the local network when at our location.
This is the CAP, Target is the Quick Access App.
I am unsure what you mean here. Where is the whitelist located? Did I create the Conditional Access Policy incorrectly?
Edit: After looking at your link, yes it is setup in this way. Our Public IP range is set as a trusted location, this is the same location in the picture I posted earlier. I set this location as a condition, targeted quick access and then blocked access. This produces the result where it is unreachable because quick access cannot connect, even though the ip is reachable without quick access.
In a different way to explain, quick access is blocking the connection, even though I want to skip it when at our trusted location to use our LAN.