Moving a geolocation to IP-based routing

If you are using either geolocation or geoproximity routing policies, and you’re consistently seeing specific clients routed to an endpoint that isn’t optimal based on their physical location or network topology, you can better target these clients’ public IP ranges by using IP-based routing.

The following table contains an example geolocation configuration for an existing geolocation routing that we will fine-tune for California IP ranges.

To override IP ranges from California to go to a new application endpoint, first recreate the geolocation routing under a new record set name.

Then, create IP-based routing records and a default record that points to your recently recreated geolocation routing recordset.