'%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)
Fix Microsoft Purview Auto-Labeling Policy: Audit Log Search is Disabled
Question details
The user is unable to save a Microsoft Purview auto-labeling policy because the portal incorrectly reports that the audit log search is disabled.
- Product
- Microsoft Purview
- Device & OS
- not provided
- Scenario
- Attempting to create and save a new auto-labeling policy in a Microsoft 365 E5 developer tenant.
- Observed behavior
- The portal blocks saving the policy with an error stating audit log search is disabled, even though Content Search and SharePoint Online audit searches are returning results successfully.
Ensure you have the necessary Compliance Administrator permissions in your Microsoft 365 tenant and that your E5 developer subscription is fully active before making policy changes.
Create the Policy in the New Microsoft Purview Portal
The classic portal may experience synchronization issues with audit log statuses. Switching to the new Microsoft Purview portal often resolves this false error.
Microsoft is transitioning compliance features to an updated administrative interface. The older portal sometimes fails to recognize backend auditing states, especially in developer tenants, resulting in saving failures.
Navigate to the new Microsoft Purview compliance portal using your global admin or compliance admin credentials.
On the left-hand navigation menu, select 'Information Protection' and go to the 'Auto-labeling' tab.
Create your auto-labeling policy from scratch in this new interface. Proceed through the wizard and click 'Save' to apply the policy without the audit log error.
Verify Audit Logging is Enabled via PowerShell
Confirm that audit logging is genuinely turned on for your tenant using Exchange Online PowerShell to rule out actual configuration issues.
Contact Microsoft Support for Backend Verification
If the error persists in the new portal and auditing is confirmed to be enabled, there may be a backend configuration issue requiring Microsoft's intervention.
Manage Your Daily Documents Effectively with WPS Office
While Microsoft Purview handles enterprise compliance and labeling in the cloud, you still need a reliable suite to create, edit, and manage your daily documents. WPS Office provides a lightweight, highly compatible alternative to Microsoft Office for your desktop and mobile needs.
- 1. Download the installer: Visit the official WPS Office website and download the free installer for your operating system.
- 2. Install the suite: Run the setup file and follow the on-screen instructions to install WPS Office on your device.
- 3. Open your documents: Launch WPS Office to instantly open, edit, and save your existing Microsoft Office files with perfect formatting retention.
Frequently Asked Questions
Why does Purview say my audit log search is disabled when it is not?
This is often a display or synchronization glitch in the classic Microsoft Purview compliance portal. Using the new Purview portal usually bypasses this false error, as it correctly reads the backend audit status.
How long does it take for audit logging to activate after enabling it?
After turning on audit logging via the Microsoft 365 admin center or Exchange Online PowerShell, it can take up to 60 minutes for the change to propagate and for the audit data to become fully searchable.
Can I apply auto-labeling policies to an E5 developer tenant?
Yes, Microsoft 365 E5 developer tenants support full compliance features, including auto-labeling policies, provided that auditing is correctly enabled and active in the backend services.
