Fix Microsoft 365 Apps Stuck on Install Pending in Intune
Question details
User needs to resolve an issue where Microsoft 365 app deployments through Intune are failing or taking too long to complete.
- Product
- Microsoft 365 Apps, Microsoft Intune
- Device & OS
- Windows 10
- Scenario
- Deploying Microsoft 365 applications to enterprise endpoints using Microsoft Intune.
- Observed behavior
- The installation process takes an unusually long time, remains perpetually stuck at an 'Install pending' state, or reports an unreliable status even after the apps are successfully installed.
Ensure you have administrative access to the Microsoft Intune admin center and that the target Windows 10 devices are properly enrolled and actively syncing with Intune.
Review Intune Management Extension Logs and Device Sync Status
Checking the local system logs on the affected Windows 10 device can help pinpoint exactly why the Microsoft 365 installation is hanging.
The Intune Management Extension is responsible for processing app deployments. If an app is stuck on 'Install pending', analyzing its local logs is the most direct way to identify network timeouts, configuration conflicts, or download failures.
On the affected Windows 10 device, go to Start > Settings > Accounts > Access work or school. Click on your connected Azure AD/Intune account, select 'Info', and click the 'Sync' button to force a check-in with Intune.
Open File Explorer and navigate to C:\ProgramData\Microsoft\IntuneManagementExtension\Logs\. You may need to enable 'Hidden items' in the View tab to see the ProgramData folder.
Open the 'IntuneManagementExtension.log' file using a text editor like Notepad. Search for 'Office' or the specific App ID to look for error codes, download blocks, or timeout messages that explain why the installation is pending.
Verify Office Deployment Settings and Detection Rules
Incorrect detection rules or flawed deployment XML configurations can cause Intune to misunderstand the installation status.
Consult Microsoft Intune Community and Official Documentation
For complex or widespread deployment failures, leveraging Microsoft's official channels and community forums can provide highly specific workarounds.
Deploy WPS Office as a Lightweight Alternative
If Microsoft 365 deployments continue to fail due to heavy package sizes or network restrictions, consider deploying WPS Office. It is a highly compatible, lightweight, and free alternative to Microsoft Office that is much easier and faster to deploy across enterprise environments via MDM or Intune.
- 1. Download the WPS Installer: Obtain the official WPS Office installation package from the WPS website.
- 2. Package for Intune: Wrap the installer using the Microsoft Win32 Content Prep Tool to create an .intunewin file for deployment.
- 3. Deploy via Intune: Upload the package to the Intune admin center, assign it to your target groups, and enjoy a faster installation process.
Frequently Asked Questions
Where can I find the Intune Management Extension logs on Windows 10?
You can find the logs at C:\ProgramData\Microsoft\IntuneManagementExtension\Logs\. The primary file to review for app deployment errors is IntuneManagementExtension.log.
Why does Intune show Microsoft 365 as 'Install pending' when it is actually already installed on the PC?
This usually happens due to incorrect detection rules in the Intune app configuration. If Intune cannot verify the installation path or specific registry key specified in the detection rule, it will fail to report the status as successfully installed.
Can firewall or network restrictions cause the 'Install pending' status?
Yes. If the target device is on a corporate network that blocks access to Microsoft's Office Content Delivery Network (CDN) URLs, the Intune agent will not be able to download the installation files, causing the process to remain stuck pending the download.
How long should a Microsoft 365 installation take via Intune?
Depending on network speed and device performance, a standard Microsoft 365 Apps deployment via Intune typically takes between 15 to 45 minutes. If it exceeds a few hours and remains pending, there is likely a deployment error.
