How to Resolve Microsoft 365 Sensitivity-Label Policy Simulation Failures
Question details
The user needs to fix a sensitivity-label policy simulation that identifies financial files but reports failed site scans, preventing the policy from being activated.

- Product
- Microsoft 365
- Device & OS
- not provided
- Scenario
- Running a sensitivity-label policy simulation to test and identify matching financial files before activating the policy across selected Microsoft 365 sites.
- Observed behavior
- The simulation successfully identifies matching files but reports that several sites failed to scan. Subsequently, attempting to activate the policy fails despite the files being located on the correct site.
Ensure you have Microsoft 365 Global Administrator privileges, as you will need elevated administrative access to view compliance reports and open official service requests.
Open a Service Request with Microsoft 365 Support
Because simulation scan failures often stem from back-end server indexing or synchronization issues, opening a direct support ticket is the necessary resolution path.
Community moderators and front-line support cannot resolve backend compliance indexing failures. A specialized remote session is required to collect the necessary diagnostic logs directly from your tenant.
Navigate to admin.microsoft.com and log in using an account with Global Administrator credentials.
Click on the 'Support' tab in the left-hand navigation menu, then select 'Help & support' to open the support assistant pane.
Enter details about the sensitivity-label policy simulation failure, specifically noting that sites failed to scan and activation is blocked despite matching financial files being present.
Bypass the automated suggestions by clicking 'Contact Support'. Fill out the required contact details and submit the ticket.
The back-end support team will contact you to initiate a remote session. Be prepared to authorize this access so they can safely collect diagnostic logs.
If your Microsoft 365 subscription was purchased through a partner or reseller (CSP) and you lack permissions to create a direct support ticket, contact your provider and ask them to escalate the simulation issue on your behalf.

Looking for a Lightweight Office Alternative? Try WPS Office
While Microsoft 365 handles complex enterprise compliance and infrastructure, everyday users and small teams often need a faster, free, and highly compatible office suite for daily tasks. WPS Office provides comprehensive tools for documents, spreadsheets, and presentations without backend configuration hurdles.
- 1. Download WPS Office: Visit the official WPS Office website and click the free download button for your operating system.
- 2. Install the Suite: Run the installer package and follow the quick on-screen instructions to set up the software.
- 3. Open Your Files Seamlessly: Launch WPS Office and open your existing Microsoft Office files. Your formatting, layouts, and data will remain perfectly intact.

Frequently Asked Questions
Why do sensitivity-label policy simulations fail on certain sites?
Simulations typically fail due to back-end indexing delays, temporary server synchronization issues, or permission mismatches on the specific SharePoint or OneDrive sites that the compliance center is attempting to scan.
Can I force a sensitivity-label policy to activate despite simulation errors?
No. Microsoft 365 intentionally blocks policy activation if the preliminary simulation encounters severe scanning failures. This safeguard prevents accidental broad impacts, false positives, or unintended data access restrictions across your organization.
What diagnostic logs does Microsoft need to fix label simulation failures?
Support teams usually require compliance center trace logs, the specific correlation IDs generated during the failed simulation runs, and backend SharePoint indexing logs. These are securely collected during an authorized remote diagnostic session.
Does restarting the policy simulation help resolve scan failures?
In cases of temporary server glitches, deleting the failed simulation and running a new one after 24 hours can occasionally resolve the issue. However, persistent failures always require Microsoft back-end support intervention.




