Application Rollbacks
Perform a rollback for crucial applications if a critical bug occurs
Performing an Application Rollback in Pckgr Deployments
Overview: When and Why Rollbacks Are Needed
Most application bugs or deployment issues can be resolved directly by Pckgr Support through adjustments or updates to the package — without requiring a full rollback.
However, a rollback process becomes necessary when:
A critical bug or failure occurs that directly affects business operations or functionality.
A version of the app causes immediate disruption to business-critical workflows.
The issue cannot be quickly resolved through vendor updates or Pckgr support intervention.
In short: Rollbacks are only recommended for critical business-impacting issues. For general bugs, always contact Pckgr Support first.
The Role of "Keep Intune History" (When to Use It)
Pckgr includes a setting called Keep Intune History in deployment settings:
When enabled, all previous versions remain available inside Intune.
This allows administrators to easily select previous versions if rollback is required.
Without this enabled, the new version completely replaces the old version inside Intune, whilst maintaining all group assignments and application settings/configurations - neat!
When Should You Enable Keep Intune History?
Enable for business-critical applications where rollbacks may be required.
Avoid enabling for general or non-critical apps — leaving old versions for every app may clutter Intune unnecessarily and undermine its clean self-maintenance.
Only select this option when there's a genuine need for version control and rollback capability.
UI Location: Deployment → Deployment Settings → Toggle Keep Intune History ON
How to Perform a Rollback (Primary Method - Supersedence Edit)
Once Keep Intune History has been enabled and multiple versions exist in Intune, rollback is handled entirely via Intune’s supersedence feature.
Step 1 — Open Microsoft Intune Admin Center
Navigate to: Apps → Windows → All Apps
Step 2 — Locate the Previous Version
Find and open the older version you wish to rollback to.
Step 3 — Edit Supersedence
Navigate to Supersedence within the application.
Select Edit → Add Supersedence.
Choose the newer version (the one you're rolling back from).
Set Uninstall previous version to Yes.
Save your changes.
Step 4 — Ensure Assignments are Active
Verify that the rollback version is still assigned to the correct device groups.
Intune will automatically process the supersedence by uninstalling the newer version and reinstalling the older version.
Processing Time & Reboot Tips
Supersedence changes may take time due to Intune’s sync intervals and device check-ins.
In many cases, there may be a delay between uninstall and reinstall.
Device rebooting will trigger a sync and can dramatically speed up the rollback processing.
Fallback Option: What If Keep Intune History Was Not Enabled?
If Keep Intune History wasn’t enabled and the older version is no longer available in Intune:
Use Pckgr's Custom Apps Feature:
Package the previous version using the Custom Apps tool.
Deploy this new package to Intune.
Once deployed, you can then configure supersedence as outlined above to perform the rollback.
This allows you to manually restore rollback functionality even if Keep Intune History was not pre-configured.
Summary: When to Use Rollback
Minor bugs or packaging issues
Contact Pckgr Support — most issues can be fixed without rollback
Critical bugs affecting business operations
Use rollback via supersedence
Keep Intune History Enabled?
Only for business-critical apps that require rollback capability
Forgot to enable Keep Intune History?
Use Custom Apps to rebuild the previous version
Key Takeaways for Application Rollbacks
Rollback functionality is not something most apps will need day-to-day.
Enable Keep Intune History only for high-risk or high-priority apps.
Always work with Pckgr Support first — rollback is typically your last resort for major incidents.
Last updated