Multiple Connectivity Profiles for just one Virtual Server Edge Client

Based on the Always On changes that are stored on the work station and within the registry, along with how settings such as Component Update take place early on in the connection process, I would guess that by the time the access policy could check for the landing uri that it might be too late. You could perhaps do a sessiondump on a connection to see if there is a variable associated with the Always On configuration and if so try to change it.

That being said, even if you could do this I would proceed with caution because you would really be coming up with a one-off solution that could very likely be difficult to support or understand if you are not around. I know it is not always easy for some environments to obtain addional public IPs but I would really weigh that against a simple and supportable configuration. Maybe that IP is an investment instead of a waste? 🤔