Jamf ALME: removing an app from a Blueprint does not uninstall it
Removing an application from a configuration does not necessarily remove it from the device. Jamf’s November 2 explanation provides a practical starting point for designing a Mac application exit procedure, with an explicit decision on data and access.
1. The behaviour documented by Jamf
Jamf describes ALME as an engine for distributing non-App Store Mac apps through Blueprints, based on Apple declarative device management. Catalog apps install and stay current automatically. Removing an app from a Blueprint stops its updates but leaves it installed. The source also describes maintenance windows for controlling download timing.
This distinction between management and local presence is the focus of this guide. Initial catalog qualification is covered in our Mac application acceptance guide.
2. Define the intended outcome before removal
Our recommendation is to open an exit record for each application. Record the business owner, target population, reason and expected outcome. Keep three decisions separate: stopping automatic maintenance, uninstalling the software and removing access to the associated service. Assign an owner to each.
A temporary exception needs a deadline
If a team wants to retain a version to complete a project, ask security to assess the risk and the business owner to set a review date. Record the observed version, affected devices and proposed compensating measure. Do not treat Blueprint removal as a documented version-locking mechanism: also check other update channels present in your environment.
3. Prepare an exit that protects data
We advise asking the business owner to identify documents to retain, their destination and who will confirm they remain readable after the exit. Test the chosen uninstall procedure on a pilot device and document its actual outcome. If a backup is needed, verify restoration using test data before the change.
For an application connected to a service, have the identity team or service owner examine permissions, sessions and licences separately. Local removal and access revocation require different evidence. Keep secrets and user documents out of the tracking record.
4. Underside analysis: verify the final state
Our operational reading is that a configuration change should end with an observation on the device. We propose four acceptance steps: record the initial version; remove the app from the Blueprint within the pilot scope; observe its local presence; then, if approved, run the separate uninstall procedure. Retain the time, device and result for each step.
Before expanding, identify policies, tools and application mechanisms that could reinstall or update the software. Assign one owner to the exit scenario and define a stop criterion: an unexpected result, unrecoverable data or business access interrupted without approval. Permission handling remains covered in our Self Service+ Full Disk Access analysis.
5. What changes for a Belgian or French business?
For an SME, we propose a short record approved by the IT contact and application owner. For a mid-sized organisation, large enterprise or public body, plan a decision for each business population and track exceptions. An organisation operating in Belgium, France or several European markets should share exit criteria while validating dependencies specific to each site.
The priority is to answer three questions: is the software still present, does it still receive updates and does it still enable access to the service? These are checks proposed by Underside, not a catalog guarantee of removal or compliance.
Underside, an Apple Business Partner, supports Apple deployment, security and lifecycle management in Belgium and France. Prepare your Mac application management procedure.
Source : Jamf — From packaging to declaring: the next generation of Mac app deployment (2026-11-02).