@kenco8801 Geofencing policies work off the same tagging system as settings, so a "Corporate Office" tag can be used to allocate both device restrictions and a geofencing policy to a device or devices. From what I've done, a single geofencing policy can only encompass one location and radius, but multiple geofencing policies can be applied to one or multiple devices. One thing to keep in mind is that while a device's location on its details page may update via IP-based locations, the value used in determining geofencing compliance will not. @DCBOE-Admin Without a cellular connection, you can only get updates to a device's location while it's connected to a wifi network. If it connects to a network and gets back to Meraki's server, public network or not, geofencing location data will be updated and any compliance policy based on location will go into effect. The problem is the compliance policy can only go into effect after the geofence is technically violated (i.e., outside the location for longer than the grace period) and after the device is able to get its location data back to the Meraki servers. It won't assume anything or give a kind of "time bomb" effect. You'll have to keep the same thing in mind as above as well: location data from IP-based locations is not taken into account when determining geofence compliance status. ... View more