The simplest approach is to add a device sub-group to the current device group of device of interest  Add an geofence (exit) alert rule/signal policy for the current device group with device relocated to the child group as action, and a corresponding geofence (entry) alert-rule/signal policy for the newly added child device-group with devices relocated back to its parent device-group as action.  Then, just add apps to be blocked in an extra application-run-control policy targeted to the new child device-group.

. 

Hi Jean Granados,

Thank you for your post on SOTI Pulse. I would also like to extend my sincere gratitude to Raymond for your valuable assistance—your expertise and willingness to help are truly appreciated.

Raymond has provided an excellent workaround; please give this method a try and let us know if it works for you. However, if you are referring to third-party applications, geofencing alone cannot block them. Instead, you can try the workaround suggested by Raymond using the application-run-control policy.

Please feel free to reach out if you need further clarification or assistance.

In addition to what Raymond said, if you don't want to relocate (move the device path), you may prefer different approach as well, such as setting a Custom Data value by using a script (and then to use this custom data In the profile(s) assignment filter you can use a custom attribute called DeviceLocation = In, otherwise the profile would be deleted), or you may test un-installation script for specific apps.

If relocation of the devices is okay to you, I'd also prefer re-location for most of the use-cases. 

Zafer