The challenge
Packages that still lived in SCCM
The client is a Canadian public-sector organization. Its application packages still lived in Configuration Manager (SCCM). The target state was an Intune application catalog, assigned by persona and ready for Windows Autopilot enrollment, so those applications had to be rebuilt in Intune-compatible formats.
The inventory was not a single shape of work. Some titles were straightforward; others needed custom install logic. The packaging method had to scale across that range, leave a registry the client's technical operations team could keep, and prove Autopilot enrollment for the personas those apps served.
Our approach
BITSUMMIT classified the SCCM inventory, packaged and validated applications into Intune across a four-tier complexity model, configured persona-based assignments, validated Autopilot enrollment for those personas, and closed with documentation and knowledge transfer.
Classify before packaging
The team reviewed the application inventory against SCCM deployment data and classified every title into a four-tier complexity model. An Application Packaging Strategy document captured the approach, and a Phase 1 review presented the findings for approval before packaging ran at scale.
Package in waves, by tier
Applications were packaged and validated in tiers from straightforward through very complex, including Microsoft Store titles configured in Intune. Packaging ran in waves: install scripts were rewritten and corrected as the client's technical team returned titles that needed fixes, so the catalog improved against real feedback rather than a one-pass conversion.
Assign by persona and prove Autopilot
Persona-based application assignments were configured in Intune so the right titles reached the right roles through the intended self-service path. Autopilot enrollment was validated as an MVP for each persona.
Registry, runbooks, and handover
An Application Packaging Registry recorded what was packaged and how. Deployment runbooks covered the complex and very complex tiers. A validation review meeting was held with the client, knowledge was transferred to the client's technical operations team, and the engagement closed with a Project Closure Report and closure meeting.
The outcome
- A four-tier packaging model. The SCCM inventory was classified into four tiers, from straightforward to very complex, and applications were packaged and validated in Intune tier by tier, including Microsoft Store titles.
- Persona-based assignments in Intune. Applications were assigned by persona so roles received the titles they needed.
- Autopilot enrollment validated per persona. Autopilot enrollment was validated as an MVP for each persona.
- A registry, runbooks, and knowledge transfer. The packaging registry, Tier 3–4 runbooks, knowledge transfer, and closure report left the client's technical operations team with the record and the method.
Moving packages into Intune is easy to treat as a conversion job. The work was classifying the inventory, packaging it so personas and Autopilot enrollment held up, and handing the client's team the registry, runbooks, and knowledge transfer to run it.
Other teams have brought devices under Intune in different ways. See how one organization brought staff Apple devices under Intune, and how another unified Windows and Mac under managed Intune and Jamf services. More on our modern workspace practice.
Still carrying application packages in SCCM while devices move to Intune? Book an Intune packaging review. We'll look at your inventory, your personas, and how Autopilot enrollment should receive those apps.
