Did you test this in a lab ?
As it could cause issues in terms dialing and other features depends on how you configure the locations and mobility groups
Based on the IP subnet that is used by the phone associated with a device pool, CUCM can choose the appropriate device pool and apply the location-dependent parameters. With the introduction of Device Mobility, CUCM is aware of the physical location of a device based on its IP address within its subnet and applies the appropriate location-specific configuration by selecting the corresponding device pool.
Roaming-sensitive settings are settings that do not have an impact on call routing. Device Mobility-related settings, on the other hand, have a direct impact on call routing, because they modify the device CSS, AAR group, and AAR CSS. Depending on the implementation of Device Mobility, roaming-sensitive settings only, or both roaming-sensitive settings and Device Mobility-related settings, can be applied to a roaming phone.
Also if this is multisite deployment and your using local route group in your dial plan the works as the phone wil use the rooming device pool for this one
But again this function is designed to work the other way around how you wanna use it where a phone configured with home Device pool with the right subnet
And once the phone subnet changes the rooming device pool with the relevant subnet will be used to overwrite some features as stated above
In brief test it to see which options/parameters that you need to apply to meet your requirements with this approach as the config of using on or more device mobility with one or different device pools and physical location can effect which parameter will be taken from the rooming device pool such as device CSS, srst reference and AAR CSS
Hope this help
If helpful rate
