Fix Microsoft 365 Servicing Profile Devices Stuck on Not Started
Question details
Devices enrolled in a Microsoft 365 servicing profile are failing to begin updates.
- Product
- Microsoft 365 Apps for enterprise
- Device & OS
- not provided
- Scenario
- Administrators are attempting to manage Microsoft 365 updates via servicing profiles, but a new build rollout is stalled.
- Observed behavior
- Devices remain in a Not Started status after a new build becomes available, even though they are powered on, online, and recently synchronized.
Ensure your affected devices are currently powered on, connected to the internet, and verify that no local firewall policies are blocking communication with the Microsoft Office CDN or the Microsoft 365 Apps admin center.
Create a Service Request in the Microsoft 365 Admin Center
Because servicing profiles rely heavily on backend synchronization and tenant data, contacting Microsoft support directly is the only way to resolve data processing delays.
Public forum moderators and community members do not have the authorization or tools to inspect your specific device synchronization status or backend servicing data. A formal support ticket allows Microsoft engineers to investigate your tenant's backend sync health.
Navigate to admin.microsoft.com and sign in with your Microsoft 365 Global Administrator or Office Apps Administrator credentials.
Click on the 'Support' icon or navigate to 'Help & support' located in the bottom right corner or left navigation menu of the admin center.
Type 'Servicing Profile Devices Not Started' in the search bar, review the automated diagnostic suggestions, and click 'Contact Support' to open a new service request. Provide details such as the affected device names and the date they last successfully synchronized.
Seek Guidance in the Microsoft Tech Community
If you want to check if this is a widespread global issue or seek advice from other enterprise administrators, post in the official Microsoft 365 Apps for enterprise community.
Try WPS Office for Simplified Deployment and Updates
Dealing with complex Microsoft 365 servicing profiles, backend synchronization errors, and stalled enterprise updates can disrupt productivity. WPS Office offers a powerful, lightweight, and free Microsoft Office alternative with standalone deployment—eliminating the headache of tenant-level synchronization issues.
- 1. Download the Installer: Visit the official WPS Office website and download the free installer for Windows, Mac, or Linux.
- 2. Deploy to Your Devices: Run the installer locally or deploy the package across your network using standard management tools like SCCM or Intune without relying on cloud servicing profiles.
- 3. Start Working Immediately: Open WPS Writer, Spreadsheet, or Presentation to easily open and edit your existing Microsoft Office files.
Frequently Asked Questions
Why do devices remain in Not Started status despite being online?
This typically occurs due to a disruption in backend tenant synchronization or a delay in Microsoft's servicing profile data processing. Even if the device is online and connected, it relies on a signal from the Microsoft 365 Apps admin center to begin the update.
Can public forums fix my servicing profile sync issue?
No. Public forum moderators and community members cannot inspect specific device synchronization statuses or backend servicing data. You must create an official service request via the admin center for tenant-specific fixes.
Is it possible to bypass the servicing profile and update manually?
Yes, administrators can temporarily exclude specific devices from the servicing profile inventory. Once excluded, you can trigger updates manually via the Office Deployment Tool (ODT) or by adjusting local Group Policy settings.
How often do servicing profiles check for updates?
Devices typically check in with the Microsoft 365 Apps admin center frequently to report their status. However, a new build rollout is strictly governed by the rollout waves and deployment rings configured in your tenant's servicing profile settings.
