We are in the process of setting up CPA, but I've run into an issue with desktop pool tags. We currently utilize tags to help control external accessibility. For example, on our internal load balanced connection servers we have a tag configured (let's say "internal-only") then at the desktop pool side we have a connection server restriction configured to use only those connection servers tagged with "internal-only". This worked great until we attempted to utilize Cloud Pod Architecture. CPA has been configured, we removed the individual entitlement on the pool and added a global entitlement (so that the user wouldn't see the pool listed twice) and it's as if the tag is being ignored. The pool can be seen when attempting to access externally. Remove the global and re-add the local entitlement and it cannot be seen externally. Has anyone run into this scenario and figured out a fix or an alternative option? We don't run F5 load balancers so that feature set cannot be used.
Thanks,
Travis