How to Fix Microsoft Purview Audit Search and Logging Errors
Question details
Administrators are unable to enable Microsoft Purview auditing due to backend organization customization failures and role assignment conflicts.
- Product
- Microsoft 365
- Device & OS
- not provided
- Scenario
- Attempting to start user and administrator activity recording in a Microsoft 365 Business Basic tenant.
- Observed behavior
- The portal returns an error, Exchange Online displays IsDehydrated as True and UnifiedAuditLogIngestionEnabled as False, and running Enable-OrganizationCustomization fails because an RBAC role assignment object already exists.
Ensure you are using an account with Global Administrator privileges in the Microsoft 365 admin center before attempting to manage tenant organization settings or contact support.
Contact Microsoft Support for Backend Tenant Reconfiguration
Because this issue involves an inaccessible backend RBAC role assignment conflict during organization hydration, opening a service request with Microsoft Support is required.
The error occurs because the Microsoft 365 tenant is in a dehydrated state, but the automated process to hydrate it (Enable-OrganizationCustomization) is blocked by a pre-existing or conflicting RBAC role assignment in the backend. As this configuration is not exposed in the standard admin interface or PowerShell, Microsoft backend engineers must resolve it.
Log in to the Microsoft 365 admin center using an account with administrator privileges.
Navigate to the left-hand menu and select the 'Support' option.
Click on 'New service request' to open a help ticket with the technical support team.
In the request description, explicitly state that your tenant shows IsDehydrated as True and UnifiedAuditLogIngestionEnabled as False, and note that the Enable-OrganizationCustomization cmdlet fails due to an existing RBAC role assignment object.
Simplify Your Document Workflow with WPS Office
Complex backend configurations and tenant errors in Microsoft 365 can occasionally halt your administrative workflow. If you are looking for a straightforward, reliable, and user-friendly office suite for creating and editing documents without relying on cloud tenant administration, consider WPS Office.
Frequently Asked Questions
Why does Enable-OrganizationCustomization fail with an RBAC role assignment error?
This error typically occurs when there is a backend data conflict in the tenant's Exchange Online directory. An improperly orphaned or conflicting role assignment prevents the system from automatically applying the required organization settings.
What does 'IsDehydrated' mean in a Microsoft 365 tenant?
The 'IsDehydrated' status indicates that the tenant is operating in a default, compressed state to save system resources. To utilize advanced features like unified audit logging, the tenant must be 'hydrated', which is usually done by running the Enable-OrganizationCustomization command.
Can I manually force UnifiedAuditLogIngestionEnabled to True?
No. If your tenant is dehydrated and the customization process is blocked by backend RBAC errors, you cannot successfully set UnifiedAuditLogIngestionEnabled to True until Microsoft Support resolves the underlying role conflict.
