APM + GTM issue with OWA 2013

@Stanislas - I'm curious, was this breaking hard for you with the static persist lb method, or were you only having issues with a handful of users? With static persist you should've ran into issues with particular users whose LDNSs were being load balanced - ie coming from multiple sources. At which point you could have tried adjusting the Static Persist CIDR (32bit by default). Often the LDNSs being load balanced have the same first two or three octets - but not always. Same deal with the WIP persistence, you can specify the CIDR to be used for the persisting the LDNSs making the queries on your behalf. Topology could have been another option, though I'm not a huge fan of the geoip DB ever since F5 moved away from quova to digital envoy. DE has definitely advanced it's data over the past few years, but I still find issues here and there.

Seth is correct, using the redirect method you ensure a user can't hit the wrong APM. As you pointed out, users are bound to re-use it. At which point you'll need to build another WIP and for that redirect URL and use Global Availability as your lb method, otherwise you're right back where you started.

What did you end up going with?