
Endpoint Management
Application Packaging: Win32 vs MSIX vs Store
Win32 vs MSIX vs Microsoft Store for Intune: a decision framework covering COM interoperability, kernel drivers, deployment rings, and MSIX App Attach.
By Paul Bentley12 min read
Windows Endpoint Management · Part 3 of 4
On this page
- The three formats
- Why Win32 is costing you more than you think
- MSIX: the default you should use
- When MSIX won't work: COM, drivers and edge cases
- Microsoft Store: simplicity with guardrails
- Making the decision: a framework
- Deployment rings: don't ship to everyone at once
- The application catalogue: knowing what you have
- Bringing it together: the application lifecycle
- Getting started
In Part 2, we talked about managing your endpoint configuration as code, treating Intune policies like source code, with version control, pull requests and pipelines. But configuration is only half the story. The other half is what you deploy to those endpoints: applications.
And this is where things get messy.
Most organisations I encounter still package everything as Win32, not because they've evaluated the alternatives and made a deliberate choice, but because it's what they've always done. The tooling is familiar, the processes are established, and nobody's made a compelling case for change.
This post is that case.