- Clear co-management workload ownership
- Autopilot path that reduces imaging dependency
- Packaging and patch continuity during the transition
Challenges we solve
- Pressure to “move to Intune” without a co-management design
- OSD still required while cloud enrollment is incomplete
- Duplicate policies between MECM and Intune
- Win32 packaging debt blocking cloud deployment
- Conditional Access readiness lagging device enrollment
What we deliver
- Estate assessment: clients, content, boundaries, ADR/SUG health
- Co-management and tenant attach readiness plan
- Workload slide sequence (compliance, resource access, updates, apps, endpoint protection)
- Autopilot and provisioning design for hardware refresh
- Application packaging and ring strategy for Intune Win32
- Reporting and rollback criteria for each wave
Engagement approach
- Assess — ConfigMgr health, Intune gaps, identity dependencies.
- Architect — target co-management state and Autopilot model.
- Modernize — pilot rings, then production slides.
- Operate — runbooks, metrics, and hypercare.
Who it is for
Enterprises with significant Configuration Manager investment that need a controlled path to Intune — not a weekend cutover.
FAQs
Do we have to retire ConfigMgr immediately?
Usually no. Many estates keep MECM for OSD or complex apps while sliding other workloads to Intune.
When should Autopilot start?
As soon as enrollment and ESP patterns are proven — ideally before large hardware refresh waves.
How do you handle packaging?
We prioritize critical Win32 apps, define a packaging standard, and align assignment rings with Intune.
What about Conditional Access?
Device compliance must be designed with Entra ID so access decisions remain predictable during migration.