“Tenant Organization is dehydrated error” while running Hybrid Configuration
if you don’t have the exchange online module installed. Install it using the below PowerShell command to check the dehydrate status of the Office 365 tenant.
Install-Module -Name ExchangeOnlineManagement -Force
Connect-ExchangeOnline
We can check the dehydrate status using the below command
Get-OrganizationConfig | fl Identity,IsDehydrated
Microsoft consolidates certain objects to save space.
When you use Exchange Online PowerShell or the Exchange admin center or run hybrid for the first time to modify these consolidated objects you may encounter an error message that the tenant is dehydrated.
It is completely safe to run Enable-OrganizationCustomization on a Production Tenant.
if the office 365 tenant is dehydrated. we can hydrate the tenant using the below command.
Enable-OrganizationCustomization
Get-OrganizationConfig | fl Identity,IsDehydrated
Now your Office 365 Tenant looks healthy you can safely re-run the Exchange Hybrid configuration.
Hey I also had an error, but when executing the command Enable-OrganizationCustomization I get the result WARNING: An unexpected error has occurred and a Watson dump is being generated: Value cannot be null. Parameter name: rootOrgId Value cannot be null. Parameter name: rootOrgId + CategoryInfo : NotSpecified: (:) [Enable-OrganizationCustomization], ArgumentNullException + FullyQualifiedErrorId : System.ArgumentNullException,Microsoft.Exchange.Management.Deployment.EnableOrganization CustomizationTask + PSComputerName : outlook.office365.com