Egress Internet Traffic from Single Gateway host in Azure blocked via AWS WAF -HostingProviderIPList

[jfelix]

Hi There,
We are an MSP that has a number of clients configured with Azure Hosted Citrix deployments.  Egress/Ingress internet traffic is filtered by R82.0 Azure hosted Security Gateway and managed by Smart-1 Cloud Saas Platform.  

We are finding random egress traffic is blocked by AWS hosted sites WAF, and i believe this is due to provider utilizing the HostingProviderIPList reputation rules.  Additionally we found services like Youtube are now forcing users to sign in when connections are detected from Azure.  

We understand we can utilize Azure BYOD PIP service, but from the R&D i have completed it seems the clients need to use /24 PIP as a minimum.  Most of the clients aren't large enough to consider this.  

While the issue has nothing to do with Checkpoint NVA, i was hopefully of finding any real-life experience on how others have handled this situation without having to change the entire client egress internet flow.  On the surface, configuring the NVA to forward egress traffic to a forward proxy sounds like a viable option, but have been unable to find too much technical info around if such an option exists.  

thanks in advance