Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
The current Microsoft Intune report is called App Install Status. Open it in the Microsoft Intune admin center at Apps → Monitor → App Install Status.
It provides a tenant-level view of application deployment activity, including application name, publisher, platform, version information where available, installation totals, and failure totals. For a particular app, user, or device, use the more detailed installation-status views described below.
What is the Intune App Install Status report?
App Install Status is an operational report for checking application deployment health across an Intune tenant. It helps administrators identify apps with unusually high failure counts, pending deployments, platform-specific problems, or inconsistent versions.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
The tenant-wide report can include:
- Application name
- Publisher
- Platform
- Version, where reported
- Device installation totals
- User installation totals
- Failure totals and, where exposed, failure percentages
You can search and sort the available results and export the report when the control is available in your tenant.
#1 Best Overall
This is not a guaranteed real-time inventory. The portal displays the latest information that Intune has received after assignment evaluation, device check-in, and application processing. A newly assigned app may not appear immediately, and a device may have changed state before its latest result reaches the service.
How to open App Install Status in Intune
- Sign in to the Microsoft Intune admin center.
- Select Apps.
- Select Monitor.
- Select App Install Status.
Older articles may call this the Endpoint Manager Intune portal and use the older endpoint.microsoft.com terminology. The current navigation is the Intune admin center path above. Microsoft can also change report labels gradually, so minor differences in filters or columns may appear between tenants.
How to interpret the statuses
Common application states include:
| Status | What it generally means |
|---|---|
| Installed | Intune received a successful installation result. |
| Failed | The installation operation reported an error. |
| Not installed | The application is not currently reported as installed. This is not automatically an installation failure. |
| Install pending | Installation is awaiting processing or is still in progress. |
| Not applicable | The app does not apply to the user or device under the deployment conditions. |
| Unknown | Intune does not have a definitive current state. |
| Uninstall failed | An attempted removal did not complete successfully. |
These concepts correspond to the application-state values documented in Microsoft Graph’s resultant app state resource. The exact columns exposed by a portal report can vary.
Not installed is not the same as failed
Failed indicates that an installation attempt returned an error. Not installed can have several explanations: the assignment may not have been processed, the device may not have checked in, installation may not yet be required, or the app may have been assigned with an intent that does not require installation.
Similarly, a successful status confirms an installation result; it does not prove that the application is licensed, configured correctly, usable after sign-in, or functioning at runtime.
Export the report to CSV
For a snapshot that you can share or analyze:
- Open Apps → Monitor → App Install Status.
- Search, sort, or apply the available filters.
- Select Export.
- Wait for the export job to complete.
- Open the downloaded CSV file.
Export behavior, completion time, available columns, and the filename can vary as Microsoft updates its reporting framework. Save the export date, tenant context, and any filters used. Installation results change over time, so an undated CSV can be misleading during an incident review.
Check one application in detail
The tenant-wide report is useful for finding broad problems, but a selected application provides more actionable detail.
- Go to Apps → All apps.
- Select the application.
- Review its overview page and status summaries.
- Select Device install status for device-level results.
- Select User install status for user-level results.
Microsoft documents the main application status groups as Installed, Not Installed, Failed, Install Pending, and Not Applicable in its app assignment monitoring guidance.
Device install status
The device view can show information such as:
- Device name
- User name or UPN
- Platform
- Application version
- Status
- Status details
- Last check-in
Use this view when one application is failing on particular endpoints or when you need to determine whether a deployment reached a device.
A device may appear with a user even when the application was assigned to a device or device group. In system context, the report may show No user. The displayed user therefore does not necessarily prove that the app was assigned directly to that person.
Rank #3
There is also a platform edge case: if the device platform does not match the application platform, Intune may omit the device instead of displaying a normal Not Applicable row. For example, an Android application targeted to an iOS device may not produce the kind of record an administrator expects.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsUser install status
The user view is useful when the problem appears related to a user-targeted assignment. It can show the user, UPN, installation results, failures, pending states, Not Installed results, and Not Applicable results.
Comparing the user and device views can help distinguish a user-scoped deployment problem from a device-scoped one, but neither view should be treated as an instantaneous endpoint inventory.
Check one device with Managed Apps
When troubleshooting a single endpoint, the device’s Managed Apps view often supplies more context than the tenant-wide report:
- Go to Devices → All devices.
- Select the device.
- Select Managed Apps.
This view can show the application, version, resolved intent, and installation status. Resolved intent helps distinguish actions such as:
- Required install
- Required uninstall
- Available
The installation details pane may also include assignment, Microsoft Intune Management Extension, check-in, creation, and installation information. This makes Managed Apps particularly useful when the question is not merely “What is the status?” but “Why did Intune decide to take—or not take—this action?”
Troubleshoot a failed installation
Use the following sequence rather than treating every Failed result as an application packaging defect.
- Confirm the intended action. Check whether the app is Required, Available, or assigned for uninstall.
- Confirm scope. Verify that the affected user or device belongs to the intended group and is not excluded by another assignment.
- Check platform compatibility. Confirm that the application supports the device operating system and architecture.
- Review requirements and dependencies. Check detection rules, minimum operating-system requirements, dependencies, supersedence, licensing, and required privileges.
- Check the device’s last check-in. A stale check-in means the portal may still show an older result.
- Open the application’s Device install status or User install status view. Review Status details and any error information.
- Use Troubleshoot + support. Select the affected user, select the device, open Managed Apps, and select the failed application.
- Sync and retry when appropriate. For a required deployment, a device sync can prompt the endpoint to process current policy. A retry is appropriate only after checking the underlying assignment and device conditions.
Microsoft’s documented troubleshooting route is Troubleshoot + support → select user → select device → Managed Apps → select the failed app. See Microsoft’s app-installation troubleshooting guidance for the diagnostic workflow.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Important reporting limitations
Available apps may not report like required apps
Users must choose an Available application, so it should not be interpreted like a Required deployment. Microsoft specifically notes reporting limitations for Microsoft Store and Android Store applications deployed with Available intent. An absent installation result does not necessarily indicate a failure.
Recommended Free Tools
Version information may be incomplete
Full version information is available for some line-of-business applications. Standard Store and VPP applications may not expose a version in the device installation report.
Assignment does not equal installation
Adding a user or device to an assignment does not instantly create an installation result. Intune must evaluate the assignment, the device must contact the service, and the application agent must process the deployment.
Conflicting intents can change the result
The same application can be assigned to multiple groups with different intents. Exclusions, required installs, required uninstalls, and Available assignments can produce an unexpected resolved intent. Inspect the assignment configuration and the device’s Managed Apps record when the portal result does not match expectations.
Portal status can be stale
The report is the latest state known to Intune, not necessarily the endpoint’s instantaneous state. A device may have installed or removed an app but not yet reported the change. Conversely, a successful report may not prove that the app is still present if detection is outdated or the device has not checked in recently.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallChoosing the right Intune view
| Administrative question | Best view |
|---|---|
| Which applications have widespread failures? | Apps → Monitor → App Install Status |
| How is one application performing on individual devices? | Apps → All apps → app → Device install status |
| Is a problem associated with a user assignment? | Apps → All apps → app → User install status |
| What happened on one endpoint? | Devices → All devices → device → Managed Apps |
| What should the help desk investigate next? | Troubleshoot + support → user → device → Managed Apps |
Using Graph for recurring reporting
The Intune portal is usually the simplest choice for interactive investigation and occasional CSV exports. For scheduled exports, dashboards, or service-management integration, administrators can consider Microsoft Graph and PowerShell.
Graph application-state resources can expose concepts such as application ID, device ID, device name, installation state, installation-state details, error code, last-modified time, platform, and user information. However, a Graph response and a portal export should not be assumed to contain identical data at the same moment.
For automation:
- Record the extraction timestamp.
- Store the normalized status separately from the error code and detailed message.
- Distinguish a missing record from an explicit Not Installed state.
- Use documented endpoints and permissions.
- Prefer Microsoft Graph v1.0 where the required resource is available.
- Treat beta APIs as changeable and avoid building production workflows around undocumented endpoints.
Microsoft states that Intune Graph APIs require an active Intune license for the tenant and warns that beta APIs can change more frequently. Review the applicable resultant app state documentation before designing an integration.
Do you need a separate product?
No separate reporting product is required for the native App Install Status report. Before purchasing standalone Intune or an add-on, check whether the organization already has an entitlement that includes Intune, such as Microsoft 365 E3, Microsoft 365 E5, Enterprise Mobility + Security, or another qualifying plan.
Native portal exports are suitable for occasional reports. Graph and PowerShell are better for scheduled reporting but require development, permissions, maintenance, and attention to API changes. Azure Monitor, Log Analytics, and workbooks can support broader dashboards, but they add design complexity and may introduce Azure consumption costs. Add-ons such as endpoint analytics or Remote Help can provide adjacent capabilities; they do not replace the basic app-installation status report.
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.
