Deploy Microsoft Store apps to devices — not just users
StorePackager Cloud resolves any Microsoft Store app straight from the official catalog, pulls in every framework dependency for your target architecture, and hands you a signed, hash-verified package with install, uninstall and detection scripts already written — ready for ConfigMgr device collections or an Intune Win32 app import, in minutes instead of an afternoon of manual MSIX wrangling.
- Official Microsoft endpoints only
- Package files never touch our servers
- Every download SHA-256 verified
- Works in air-gapped networks
Your packages never leave your own network
StorePackager Cloud fetches metadata only — nothing more — from the official Microsoft endpoints, and signs the result into a manifest. A lightweight agent inside your network downloads the actual package files directly from Microsoft's delivery infrastructure and checks each one against its hash. No intermediate copy on our side, no redistribution, and no bandwidth ceiling on packages that can run to hundreds of megabytes.
Paste a Store link
A product ID or an apps.microsoft.com URL is all it takes. StorePackager queries DisplayCatalog and Windows Update and works out the correct main package, its current version, and every framework it depends on.
The agent builds the package
It downloads straight from Microsoft's CDN, verifies every hash, and lays down a complete source folder — install, uninstall and detection scripts included. Proxies and isolated networks are supported out of the box.
Deploy to ConfigMgr or Intune
A ready-made ConfigMgr application via the script included in every package, or a .intunewin file for a Win32 app import into Intune. Build both from the same source folder if you need to support either platform.
Stay on the current version
Watch any app and get notified by email or webhook the moment Microsoft ships an update — or let StorePackager queue the rebuild automatically so your catalog never drifts out of date.
Built for how Windows device management actually works
Device deployment, not user deployment
ConfigMgr's built-in "Windows app package" deployment type can only target signed-in users — a dead end for kiosks, shared devices, and unattended machines. StorePackager creates a script deployment type instead, provisioning the app with Add-AppxProvisionedPackage in the SYSTEM context.
Every architecture your fleet needs
A bundle can resolve to an x86 package for a particular user. Miss that framework and registration fails at logon with 0x80073CF3. StorePackager includes the frameworks for every architecture that can run on your target, not only the one you asked for.
Hash-verified, every file, every time
Each download is checked against the hash published in the Windows Update metadata. A corrupted or incomplete transfer surfaces immediately while building — never as a silent failure on a client.
Built for air-gapped and restricted networks
Download a signed manifest and carry it into an isolated network on removable media; the agent verifies the signature offline and builds without ever calling your StorePackager Cloud URL. See the offline deployment guide for both variants.
Who it's for
ConfigMgr / MECM admins
Get Store apps onto device collections without hand-rolling provisioning scripts or fighting the built-in deployment type's user-only restriction.
Intune administrators
Skip the manual .intunewin packaging and detection-script guesswork — both are generated correctly from the same manifest as your ConfigMgr package.
MSPs and regulated environments
Multiple agents, multiple organisations, an audit log, and an offline path for clients whose networks can't call outside SaaS directly.
Pricing
See every differenceFree
For trying it out and the occasional package.
- 5 packages per month
- 3 watched apps
- 1 agent
- ConfigMgr scripts and ZIP
Team
For the client management of a single organisation.
- 100 packages per month
- 50 watched apps
- 5 agents
- Intune packaging (.intunewin)
- REST API
Business
For managed service providers and multiple sites.
- Unlimited packages
- Unlimited monitoring
- 25 agents
- Webhooks and automation
- Audit log
Frequently asked questions
Can I deploy Microsoft Store apps to device collections in ConfigMgr, not just users?
Yes. ConfigMgr's built-in 'Windows app package' deployment type can only target users, which is a dead end for kiosk, shared, and unattended devices. StorePackager builds a script deployment type instead, provisioning the app in the SYSTEM context with Add-AppxProvisionedPackage — the supported way to put a Store app on a device collection.
Does this work for Intune Win32 app deployment too?
Yes. Every package can include a ready-to-import .intunewin file, with the install command, uninstall command, PowerShell detection script and return-code mapping already filled in from the same source folder used for ConfigMgr.
Are the Microsoft Store package files stored on your servers?
No. StorePackager Cloud only resolves metadata — title, version, file hashes — through the official Microsoft catalog and Windows Update endpoints, and signs that into a manifest. The actual package bytes are downloaded by an agent inside your own network, straight from Microsoft's delivery network, and never pass through our infrastructure.
Can I package and deploy Microsoft Store apps in an air-gapped or offline network?
Yes, two ways depending on how isolated the network is. If it can still reach Microsoft but not third-party SaaS, an agent there builds directly from a signed manifest carried in from elsewhere. If it has no internet access at all, the package is built on a connected machine and the finished, hash-verified folder is carried across on removable media. Both are covered in the agent user guide.
What happens when Microsoft ships a new version of a watched app?
StorePackager checks watched apps on a schedule and notifies you by email or webhook the moment a new version appears — with the option to queue a rebuild automatically so your package library doesn't quietly go stale.
Ready to stop packaging Store apps by hand?
The Free plan covers five packages a month — enough to see the whole workflow on a real app before you commit to anything.
Start for free