To export the configured apps shown in Intune under Apps > All Apps, use the Microsoft Graph FilteredAppsList report. Despite its name, that report has no supported report filters. If you need to filter installed or discovered software across managed devices, use the separate AppInvRawData report, which documents equality (eq) filters on specified fields. These reports answer different questions: one lists app records configured in Intune; the other reports apps discovered on devices.
Choose the report that matches what you want to track
| Need | Recommended path | Documented filter support | What it helps you track |
|---|---|---|---|
| Configured apps in Apps > All Apps | FilteredAppsList report export |
No report filters | App type, status, version, assignment state, owner, publisher, platform, dates and related details |
| Discovered software across managed devices | AppInvRawData report export |
eq on documented properties |
App name and versions, publisher, device, OS, platform and user fields |
| Discovered software for a known device | AppInvByDevice report export |
DeviceId is required |
Inventory associated with a particular device |
| Intune app objects retrieved through Graph | GET /deviceAppManagement/mobileApps |
Check the API query documentation for the exact query you need | App objects and their properties; assignments are retrieved separately |
The report names and portal locations are documented in Microsoft’s available Intune reports reference. The key distinction is whether you mean apps configured in the Intune catalog or software discovered on devices; an app record in the catalog does not, by itself, show that the app is installed on a particular device.
As an Amazon Associate I earn from qualifying purchases.
Export the Intune app catalog with Microsoft Graph
Use the export jobs API to create a FilteredAppsList report, select the fields you need, wait for the job to finish, and download its output. Microsoft documents the export endpoint as https://graph.microsoft.com/beta/deviceManagement/reports/exportJobs. Export is asynchronous: the initial request creates a job rather than returning the finished file immediately.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problems- Choose explicit columns. Supply a
selectlist of fields valid forFilteredAppsList. Do not build an automated process around assumed default columns: Microsoft advises selecting the required fields and accepting only columns valid for that report. - Choose an output format. Set
formattocsvorjson. CSV is the documented default, but setting the format explicitly makes the intended output clear. - Choose how localized values should appear. If the report contains localized values, use
LocalizedValuesAsAdditionalColumnto retain the raw or enum value and add a localized display column, orReplaceLocalizableValuesto put the localized string in the original column. - Create the export job. Send a POST request to the documented export jobs endpoint with
reportNameset toFilteredAppsListand the selected columns and export options. - Wait for completion and download the file. Use the job ID returned by Graph to check the export job’s status. When its status is
completed, download the compressed output from the URL returned by Graph. Treat that URL as temporary job output, not as a permanent report address.
Microsoft’s Intune report export guidance documents the export job workflow and options. For example, the request’s key values would be:
#1 Best Overall
{
"reportName": "FilteredAppsList",
"select": ["ApplicationId", "ApplicationName", "AppStatus", "AppVersion", "Publisher", "Platform"],
"format": "csv"
}This illustrates the report name and a subset of valid fields; add or remove columns to suit the tracking task. It does not add filtering: Microsoft’s report reference lists no filters for FilteredAppsList.
Fields available for the catalog report
The documented FilteredAppsList fields include:
ApplicationId,ApplicationName,AppStatus,AppTypeandAppVersionAssigned,AppLastModifiedTimeandCreationTimeDescription,Developer,Owner,Platform,PublisherandNotesStoreUrl,MoreInformationLinkandPrivacyLink
Include only fields that help answer a reporting question. For example, use the app name, version, platform and status for a compact catalog inventory; add assignment state and dates when you also need to review configuration and maintenance.
Filter discovered app inventory instead
If the task is to find applications reported on managed devices, export AppInvRawData, not FilteredAppsList. The documented filter comparison for this inventory report is eq. Its listed filterable properties are:
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →- Application:
ApplicationName,ApplicationPublisher,ApplicationShortVersionandApplicationVersion - Device and operating system:
DeviceId,DeviceName,OSDescription,OSVersionandPlatform - User:
UserId,EmailAddressandUserName
For example, a filter can target an exact application name or version using the documented eq operator. Do not assume that other operators, fields, or filter behavior are supported unless Microsoft documents them for the report you use. The available reports reference identifies AppInvRawData and its filterable properties.
Rank #3
When a device-specific inventory is more useful
Use AppInvByDevice when you already know which device to inspect. Its documented filter requires DeviceId; it is not the same as filtering the wider discovered-app inventory by application name.
Retrieve app objects instead of an export report
For applications as Graph resources, use GET /deviceAppManagement/mobileApps. The collection returns Intune mobileApp objects, with properties such as app ID, display name, description, publisher, creation and modification timestamps, owner, developer, notes and publishing state, alongside category and assignment relationships.
This route is suited to applications that need app objects through Graph rather than a report-shaped export. Microsoft documents an active Intune license and an appropriate delegated or application permission, such as DeviceManagementApps.Read.All, as requirements. Personal Microsoft accounts are unsupported for this API. The resource documentation also marks listing the collection with $expand=assignments as deprecated; list the apps first, then retrieve assignments for individual apps. Do not assume report-export filters translate directly to query filters on the app collection.
Free tools Windows power users keep installed
One-click scans. No signup required.
Keep an automated export reliable
- Use a job, not a one-shot download assumption. Create the export, retain its returned job ID, check status, and download only after completion.
- Make the schema intentional. Request the columns your process consumes so downstream tracking does not depend on unspecified defaults.
- Avoid aggressive polling. Microsoft documents an export API limit of 100 requests per tenant per minute, in addition to per-user and per-app limits. Those are operational API limits, not a recommendation to poll at that rate.
- Store the result appropriately. The download URL belongs to the completed job output and should not be treated as a durable report link.
- Choose the report before designing filters. Catalog reporting has no report filters; discovered-app inventory has documented equality filters. A different Graph resource route has a different query model.
Microsoft’s report export documentation covers the export workflow and limits. API versions, permissions and report documentation can change, so confirm the current Microsoft guidance when implementing or maintaining automation.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
