Every application in the Microsoft Intune Enterprise App Management (EAM) catalog, in one searchable list — publisher, version, architecture, locales and auto-update support for every package, refreshed with each catalog export. For the feature itself, see Microsoft's Enterprise App Management documentation.
| # | Publisher | App Name | Branch | Version | Architecture | Auto-Update | Locales |
|---|
No packages match your filters.
About the Intune EAM App Catalog
Enterprise App Management (EAM) is the Microsoft Intune feature that publishes ready-made Win32 applications — packaged, with detection rules and update logic already in place — so an administrator can deploy them without wrapping an installer. Microsoft does not publish the contents of that catalog as a browsable list; the only official view is the app picker inside the Intune admin center. Microsoft documents the feature itself on Microsoft Learn.
This site is that list. Every package returned by the
win32MobileAppCatalogPackage Graph resource is exported on a
schedule and rendered here: a searchable table of all packages, a
page for each application with its full branch and
version history and the deployment details Intune sets up for it, statistics,
a changelog of what Microsoft added, removed or updated between exports, and
a quirks page of what those deployment details
reveal across the whole catalog.
Use it to check whether an application is available in EAM before planning a deployment, to see which version Intune currently offers, to confirm whether a package can update itself, or to subscribe to the RSS feed and be told when the catalog changes.
Filtering with the Stat Cards
The cards above each table are also filters. Clicking one scopes the view; clicking it again clears it. Cards that only summarise values spread across rows — Publishers, Locales — are read-only.
| Card | Click |
|---|---|
| Total Packages | Clears every filter, including the search box. |
| Unique Products | Shows one row per product — the first version listed, regardless of how the table is sorted. |
| Auto-Update | Cycles through auto-update capable, not capable, and off. The dropdown follows along. |
| Added / Removed / Updated | On the Changes tab: shows only that section. The choice carries over when you switch period, unless that period has no such entries. |
Card filters stack with the search box and the dropdowns rather than replacing them, and the Clear button resets all of them at once.
Data Fields
Each entry represents one installable package from the Intune EAM catalog,
as returned by the win32MobileAppCatalogPackage resource in
the Microsoft Graph API.
| Field | Description |
|---|---|
productDisplayName |
Application name as shown in Intune EAM. |
publisherDisplayName |
Publisher or vendor name. |
versionDisplayName |
Version string for this specific package. |
branchDisplayName |
Branch name — typically includes the architecture, e.g. WireGuard (x64). |
applicableArchitectures |
Supported CPU architectures such as x64, x86, or arm64. |
packageAutoUpdateCapable |
When Yes, Intune can automatically update this package when a newer version appears in the catalog. |
locales |
List of supported locale codes, e.g. en-US. |
productId |
Stable GUID identifying the product. One product can have multiple branches (e.g. separate x64 and x86 packages). |
branchId |
Stable GUID identifying this specific branch. Used as the primary key for change detection between exports. |
id |
Package instance ID. A branch gets a new one whenever Microsoft publishes a new package for it — with every version update, and also for rebuilds that change nothing in the fields above. Not used to match packages between exports. |
Deployment Details
For every package, the exporter also asks Microsoft Graph for the Win32 app
Intune would create from it
(convertFromMobileAppCatalogPackage). Each app page shows the
result under Deployment details; packages whose templates differ only
in installer size, such as Firefox's locales, are shown once.
| Shown | Source in the template |
|---|---|
| Installer, file, size | msiInformation present means MSI, otherwise EXE; fileName, size. |
| Install / uninstall command | installCommandLine, uninstallCommandLine, with a copy button. |
| MSI product and upgrade code | msiInformation.productCode, msiInformation.upgradeCode. |
| Detection and requirement rules | rules, split by ruleType and written out as sentences. Several detection rules must all match. |
| Install context, restart, max run time | installExperience. |
| Return codes, minimum OS | returnCodes, minimumSupportedWindowsRelease. |
| Description | description — the catalog record's own productDescription is always empty. |
How Change Detection Works
When two exports are compared, packages are matched by branchId —
a stable identifier that survives catalog re-indexing. The id field
identifies the package, not the branch, and is not used to match them.
| Change type | Meaning |
|---|---|
| Added | branchId exists in the newer export but not in the older one. |
| Removed | branchId exists in the older export but not in the newer one. |
| Updated | Same branchId in both exports, but at least one tracked field
changed. The Changed column lists which ones — hover a tag to see
the old and new value. |
| Repackaged | Same branchId and an unchanged catalog entry, but the deployment
details differ — Microsoft rebuilt the package without a new version.
Listed in changes.md on GitHub and in each app's change
history. |
Deployment details are compared in two ways. With a version change, only how the app is deployed counts: a new switch, another detection method, a different upgrade code. The installer name, its size, the MSI product code and the version in the detection rule move with every release, so they are not reported. Without a version change every value counts. The first export with deployment details is a baseline and reports none.
Tracked fields are versionDisplayName, productDisplayName,
branchDisplayName, publisherDisplayName,
applicableArchitectures, packageAutoUpdateCapable and
locales. A version bump is the common case, but renames and
capability changes are reported too.
Exports produced before the catalog exposed branchId fall back to a
composite key of productId plus branch name. A handful of packages
share that key — they are kept apart by a stable ordinal so none are silently
dropped from the comparison. On this fallback path a branch rename cannot be told
apart from a removal plus an addition.
Changelog Windows
The period-based changelogs use the timestamp embedded in each filename
(YYYYMMDD_HHMMSS_AppCatalog) to find the right comparison point
automatically.
| Changelog | Comparison point |
|---|---|
| Latest | Most recent export vs the one directly before it. |
| Daily | Most recent export vs the closest export at least 24 hours older. |
| Weekly | Most recent export vs the closest export at least 7 days older. |
| Monthly | Most recent export vs the closest export at least 30 days older. |
These are minimums, not fixed windows. If no export exists close to the cut-off — for example after a long gap in exports — the comparison reaches back to the newest one that qualifies, which may be considerably older. Each changelog states the actual span between the two exports it compared.
RSS Feed
Subscribe to catalog changes in any RSS reader. Every export that adds, removes or updates something publishes a new entry automatically; exports that change nothing stay out of your inbox.
Feed URL
feed.xml
Each item names the apps that changed and lists the added, removed, and updated packages — publisher, name, and version, with a link to every app's own page. The feed keeps the last 50 entries and is compatible with any RSS 2.0 client: Feedly, Outlook, Thunderbird, Apple Mail, and others.
| Client | How to subscribe |
|---|---|
| Feedly | Paste the feed URL into the search bar |
| Outlook | Account Settings → RSS Feeds → New |
| Thunderbird | File → Subscribe → paste URL |
| Apple Mail | File → Add Account → Other Mail Account → RSS |
| Any reader | Copy the feed URL and add it as a new subscription |
Disclaimer
This project is not affiliated with, endorsed by, or in any way officially connected to Microsoft Corporation. All product names, trademarks, and registered trademarks are property of their respective owners.
The data displayed here is sourced from the Microsoft Graph API and is provided for informational purposes only. Accuracy and completeness depend on the timing of catalog exports and may not reflect the current state of the Intune EAM catalog at any given moment. No warranty, express or implied, is given regarding the accuracy, reliability, or fitness of this data for any particular purpose. Use at your own discretion.