---
sourceDocument: Australia Workflow Data Fabric
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/integrate-applications

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Workflow Data Fabric

ft:clusterId :

    - crint

bundleId :

    - crint

workflow :

    - Creator


---

# SCCM software revocation flow

# SCCM software revocation flow {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
The Revoke SCCM Application flow moves a user or device from an install collection to
an uninstall collection to revoke software installed from Microsoft System Center Configuration
Manager (SCCM).
For the revocation subflow to run, the software package must have a status of [Client software distribution validation process](https://www.servicenow.com/docs/access?context=c_ClientSWDistValidProcess&version=australia&pubname=australia-servicenow-platform&ft:locale=en-US) and must be pre-configured for an appropriate uninstall collection. See
[Revoke software deployed through the
service catalog](https://www.servicenow.com/docs/1etBezPnK_4qNPyBDDb_ig "Software deployed by SCCM can be revoked, but only when the status of software is Installed and the application associated with the software configuration has an uninstall collection configured.") for configuration instructions. When an administrator initiates the
revocation process, the system launches the Revoke SCCM Application subflow to move the user
or device collection associated with installation to the appropriate SCCM uninstall
collection. When the SCCM server performs a policy check, it finds the additions to the user
or device uninstall collection and revokes the software package associated with that
collection.  
The subflow employs two custom actions in the [Microsoft SCCM Spoke](https://www.servicenow.com/docs/r1y0oo966lkDp59e1gEnLg "Automate management of user collections, device collections, and application deployments on a Microsoft System Center Configuration Management (SCCM) server."), Remove from User Collection and Remove from Device Collection, to remove either the user or the device from its original collection. The subflow then adds the user or device to the appropriate uninstall collection on the SCCM server with the Add to User Collection or Add to Device Collection activity.  
Note:  
This subflow is triggered by the Revoke Client Software subflow.