Access - Streamlined clientless browser isolation for private applications

A new Allow clientless access setting makes it easier to connect users without a device client to internal applications, without using public DNS. Previously, to provide clientless access to a private hostname or IP without a published application , you had to create a separate bookmark application pointing to a prefixed Clientless Web Isolation URL (for example, ). This bookmark was visible to all users in the App Launcher, regardless of whether they had access to the underlying application. Now, you can manage clientless access directly within your private self-hosted application . When Allow clientless access is turned on, users who pass your Access application policies will see a tile in their App Launcher pointing to the prefixed URL. Users must have remote browser permissions to open the link.