'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
How to Fix Microsoft 365 Activation on Autopilot-Managed Devices
Question details
Users need to resolve an issue where Microsoft 365 Apps fail to activate and get stuck in viewer mode on devices managed by Windows Autopilot.
- Product
- Microsoft 365 Apps
- Device & OS
- Windows
- Scenario
- Provisioning a new machine or signing into Microsoft 365 applications on a device managed by Windows Autopilot.
- Observed behavior
- Microsoft 365 Apps display 'Getting Office ready for you' but ultimately fail to activate, causing the applications to open in viewer-only mode.
Ensure that the user account is assigned a valid Microsoft 365 license that includes desktop apps, and verify that the device is connected to a network that does not block Microsoft activation URLs.
Reset Activation State and Verify Configuration
Clear existing activation credentials and systematically check licensing, enrollment, and network access to isolate the Autopilot deployment issue.
When Microsoft 365 Apps fail to activate specifically on Autopilot devices, it usually stems from conflicting sign-in tokens, conditional access blocks, or missing licensing assignments during the provisioning phase. Resetting the activation state allows the device to attempt a fresh authentication.
Run the Microsoft Support and Recovery Assistant (SaRA) tool or use the official OLicenseCleanup script to completely clear the previous Microsoft 365 Apps activation state and cached credentials from the device.
Log into the Microsoft 365 Admin Center, navigate to Active Users, and confirm that the affected user has an active license assigned for Microsoft 365 Apps for enterprise or business.
Sign in with the same user credentials on a standard, non-managed device on the same network. If the apps activate successfully, the issue is isolated to your Autopilot profile or conditional access policies.
If the issue persists only on Autopilot-managed devices, collect the diagnostic logs using the SaRA tool and open a support ticket with Microsoft Support via the Microsoft 365 Admin Center.
Try WPS Office for Seamless Productivity Without Activation Hassles
If your organization is facing persistent enterprise deployment and activation issues with Microsoft 365, WPS Office provides a lightweight, highly compatible, and easy-to-manage alternative that works perfectly on Windows devices without complex enrollment prerequisites.
- 1. Download the installer: Visit the official WPS website and download the free WPS Office installation package.
- 2. Install on your device: Run the installer and follow the simple on-screen prompts to complete the setup in minutes.
- 3. Open your files: Launch WPS Office and instantly open your existing Microsoft Office documents without worrying about enterprise activation states.
Frequently Asked Questions
Why do Microsoft 365 Apps open in viewer mode on Autopilot devices?
This happens when the application cannot successfully verify the user's license. On Autopilot devices, this is often caused by single sign-on (SSO) failures, conditional access policies blocking the authentication, or network restrictions preventing access to activation servers.
How can I tell if the activation error is caused by Autopilot?
Test the activation process on a standard, non-Autopilot managed device using the exact same user account and network. If it activates successfully on the standard device but fails on the Autopilot device, the issue is tied to your Intune/Autopilot deployment configuration.
What should I do if clearing the activation state doesn't fix the issue?
If resetting the activation state fails, you should gather diagnostic logs using the Microsoft Support and Recovery Assistant (SaRA) and escalate the issue to Microsoft Support through your Microsoft 365 Admin Center for advanced troubleshooting.
