App deployment: Win32 vs Enterprise App Catalog vs M365 Apps vs managed Google Play
Verdict: Package classic installers as Win32 with the Content Prep Tool. Use the Enterprise App Catalog for Microsoft-hosted Win32 apps. Build Microsoft 365 Apps config with the Office Customization Tool. Android Enterprise apps need a managed Google Play connection first.
| Criterion | Win32 app | Enterprise App Catalog | Microsoft 365 Apps | Store apps | Managed Google Play |
|---|---|---|---|---|---|
| What it is | Classic Windows installer | Microsoft-hosted prepared Win32 apps | Microsoft 365 desktop apps | Store app distribution | Android Enterprise apps |
| Prep or config tool | Win32 Content Prep Tool | None; discover in catalog | Office Customization Tool | None | Approve in managed Google Play |
| Installer or agent | Intune Management Extension | Intune Management Extension | M365 Apps app type | Store client | Managed Google Play |
Rules
- Convert a classic setup.exe installer into the required .intunewin format with the Microsoft Win32 Content Prep Tool before adding it as a Win32 app.
- The Enterprise App Catalog is a Microsoft-hosted collection of prepared Win32 apps for Windows, discoverable and deployable from Intune.
- The Intune Management Extension installs Enterprise App Catalog apps, the same agent used for other Win32 deployments; the catalog does not use winget.
- Build the Microsoft 365 Apps configuration.xml with the web-based Office Customization Tool rather than hand-editing XML.
- Connect the Intune tenant to a managed Google Play account before Android Enterprise work profile apps can be added and assigned.
Traps
- The Win32 Content Prep Tool packages installers; it does not build the Office Deployment Tool configuration.xml.
- Enterprise App Catalog apps are not installed through winget; Microsoft states the catalog does not use Windows Package Manager.