Organizations can switch from System Center Configuration Manager (SCCM) to leverage the Microsoft Store for Business or Microsoft Store in Intune as part of a modern software distribution and management strategy. However, the feasibility and effectiveness of this switch depend on the organization’s needs and the features available in these platforms.
Key Considerations for Switching
1. Benefits of Using the Microsoft Store for Business
• Centralized Management:
• Organizations can use the Microsoft Store for Business to acquire, manage, and distribute apps to users.
• Integration with tools like Microsoft Intune enables seamless app deployment and updates.
• Seamless Updates:
• Apps from the Microsoft Store update automatically, reducing the need for manual patching or deployments.
• Simplified Deployment:
• Pre-packaged apps in the Microsoft Store are ready for deployment without additional packaging efforts required in SCCM.
• Cost Efficiency:
• Reduces reliance on SCCM infrastructure, which can save on server costs and administrative overhead.
• User Self-Service:
• Users can access approved apps directly through a company-managed store, improving productivity.
2. Limitations of the Microsoft Store
• Limited Software Availability:
• Not all enterprise applications are available in the Microsoft Store. Many enterprise apps require custom installers, which SCCM handles effectively.
• Custom Installations:
• SCCM supports customized installations (e.g., silent installs, pre-configuration settings), which are harder to achieve through the Microsoft Store.
• Compliance and Security:
• SCCM offers granular control over deployments, configurations, and compliance policies that may be more robust than what the Microsoft Store provides.
• Legacy and Non-UWP Apps:
• The Microsoft Store primarily supports Universal Windows Platform (UWP) apps. Legacy apps and apps requiring deep system integration may not be available.
3. Use of Microsoft Intune as a Bridge
Organizations moving away from SCCM can combine Microsoft Intune with the Microsoft Store for Business:
• App Deployment:
• Intune can deploy apps from both the Microsoft Store and external sources, providing flexibility for software not available in the Store.
• Device Management:
• Intune provides mobile device and PC management capabilities, replacing SCCM’s device management features.
• Policy Enforcement:
• Intune allows enforcement of security and compliance policies.
4. Hybrid Approach
For organizations with diverse requirements, a hybrid approach can be effective:
• Use SCCM for managing legacy, custom, or complex applications.
• Use the Microsoft Store (via Intune) for modern UWP apps and straightforward installations.
• Gradually transition workloads to Intune as more apps adopt modern packaging.
5. Key Scenarios for Switching
• Small to Medium Businesses (SMBs):
• The Microsoft Store for Business with Intune is a cost-effective solution for SMBs with simpler IT needs.
• Cloud-First Organizations:
• Organizations moving to a fully cloud-based infrastructure may benefit from Intune and the Store for app management.
• Modern Device Deployment (Windows Autopilot):
• The Microsoft Store integrates well with Windows Autopilot for zero-touch device provisioning.
6. Considerations for Transition
• Training:
• IT teams need training on Intune and Microsoft Store management.
• Software Compatibility:
• Evaluate if all required software is available or can be transitioned to modern app packages.
• Cost Analysis:
• Assess costs associated with migrating to Intune and decommissioning SCCM infrastructure.
Conclusion
Switching from SCCM to the Microsoft Store and Intune is feasible for many organizations, especially those prioritizing cloud-based infrastructure and modern app delivery. However, for enterprises with complex app requirements or reliance on legacy systems, SCCM may still be necessary in a hybrid setup.
Would you like guidance on implementing a specific transition strategy or exploring Intune in more detail?