Allow Gateway as Access rule


I have setup Access to allow connections via Gateway, so my users don’t need to login extra, but this rule doesn’t seem to work…

I’ve setup Teams Gateway, but on, I see this:

While on I get this:

On the Teams Dashboard, I see my DNS requests in the Gateway logs…

Any idea what’s going on here?


To add, sometimes my connection seems to be secured by Gateway, but not every time as in the screenshot above…

Gateway (or Warp) as a standalone criteria for an Access policy is not currently supported. When it is, it will likely be a ‘service auth’ type rule which is non-identity based vs. an Allow rule action if that is the only criteria. It will also require that the user is using the Client in a Warp mode.

Sounds great! Exactly what I need. Thanks @cscharff!

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.