Anyone here actually using automate uninstall application action?Solved

We didn’t think much of it at first, but it’s been pretty useful for us. 

We deal with a lot of short-term app deployments, stuff that’s only relevant for a few days or weeks. Earlier, those apps would just sit there unless someone remembered to remove them. 

Now we just attach an automation to clean them up later. It keeps devices from getting cluttered over time.  

In our setup, it’s more tied to how devices transition. Whenever a device moves into a different group, we use automation to strip out apps that don’t belong in that context. It’s less about cleanup and more about keeping things aligned with how the device is supposed to be used. 

Before this, there was always a gap between moving the device and fixing the apps. 

One thing I’d say — don’t treat it like a “set and forget” action. 

We had a case where an automation removed an app that was still needed by a small set of users. Since it wasn’t a manual action, it took a while before anyone noticed. 

Now we’re a bit more careful about how we scope it. 

Yeah, that’s what I was wondering. Once it’s automated, you kind of lose that immediate visibility. 

Do you all mostly run it on schedules or based on some conditions? 

A mix of both. 

Scheduled works well for predictable cleanup, but conditions are where it gets interesting. If you can tie uninstall to a specific device state or scenario, it becomes much more meaningful than just periodic removal. 

Yeah, exactly @it_christo! 

We actually use it for a location non-compliance scenario. If a device moves outside the allowed location range, it gets flagged, and that triggers an automation. As part of that, we uninstall a set of apps that shouldn’t be accessible outside approved regions. 

So instead of just running it on a schedule, it depends on where the device is and whether it meets our conditions.