| # | Publisher | App Name | Branch | Version | Architecture | Auto-Update | Locales |
|---|
No packages match your filters.
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 assigned by the Graph API. This changes on every export and is not used for comparisons. |
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
changes on every export and is intentionally ignored.
| 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. |
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 time a new export is processed, a new entry is published automatically.
Feed URL
feed.xml
Each item contains a summary of added, removed, and updated packages — including publisher, name, and version details. 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.