Enable-OrganizationCustomization: When and How to Run It

2 min read James Futhey Updated November 13, 2026
Microsoft Learn documentation for the Enable-OrganizationCustomization cmdlet showing its PowerShell syntax

Quick answer: connect with Connect-ExchangeOnline, then run Enable-OrganizationCustomization once. It takes no parameters and shows no output. You only need it when Exchange Online or the Microsoft Defender portal asks for it, usually the first time you create or change a built-in policy or role. Check whether it's already done with Get-OrganizationConfig | Format-List IsDehydrated: False means it has already run.

What does Enable-OrganizationCustomization do?

To save space, Microsoft consolidates certain configuration objects in its datacenters. A tenant in that state is "dehydrated." Enable-OrganizationCustomization creates the tenant's own copies so you can change them. It works only in Exchange Online.

You might get an error that tells you to run it the first time you:

Change Example cmdlet
Create a role group or management role assignment New-RoleGroup, New-ManagementRoleAssignment
Create or modify a role assignment policy New-RoleAssignmentPolicy, Set-RoleAssignmentPolicy
Create or modify an Outlook on the web mailbox policy New-OwaMailboxPolicy, Set-OwaMailboxPolicy
Create or modify a sharing policy New-SharingPolicy, Set-SharingPolicy
Create or modify a retention policy New-RetentionPolicy, Set-RetentionPolicy
Turn on preset security policies Microsoft Defender portal

How do I run it?

Connect-ExchangeOnline -UserPrincipalName admin@contoso.com
Enable-OrganizationCustomization

No output means it worked. Afterwards, rerun the command that asked for it. If Connect-ExchangeOnline isn't recognized, install the Exchange Online module first.

The only parameters are -WhatIf, which previews the change without making it, -Confirm, which adds a prompt, and the common parameters.

Has it already been run?

Get-OrganizationConfig | Format-List IsDehydrated
IsDehydrated Meaning Action
True Never run Run Enable-OrganizationCustomization
False Already run Nothing to do. Running it again returns an error

More on that cmdlet: Get-OrganizationConfig.

Which permissions do I need?

You need an Exchange role that includes the cmdlet. To list the roles that include it and who holds them:

$Perms = Get-ManagementRole -Cmdlet Enable-OrganizationCustomization
$Perms | foreach {Get-ManagementRoleAssignment -Role $_.Name -Delegating $false | Format-Table -Auto Role,RoleAssigneeType,RoleAssigneeName}

If your account isn't listed, ask an Exchange or Global Administrator to run the command or to assign you the role.

Is it safe?

It is a one-time change. It doesn't change any setting on its own: it only lets you customize objects that were shared before. Run Enable-OrganizationCustomization -WhatIf first if you want to preview it.

Troubleshooting

Symptom Cause Fix
"Enable-OrganizationCustomization is not recognized" Not connected to Exchange Online Run Connect-ExchangeOnline
Error when you run it Already run (IsDehydrated is False) Nothing to do. Continue with your change
Access denied Missing the role Check roles with the script above
Defender preset policies still won't turn on Tenant still dehydrated Check IsDehydrated, run it, then retry in the portal

Summary

  • Run it once, only when Exchange Online or Defender asks for it.
  • It takes no parameters and shows no output.
  • Get-OrganizationConfig | Format-List IsDehydrated: False means it's done.
  • Running it a second time gives an error. That error is harmless.
  • You need an Exchange role that includes the cmdlet.

Related: Get-OrganizationConfig, installing the Exchange Online PowerShell module.

Meeting Room 365 turns any iPad or Android tablet into a room display for Exchange and Microsoft 365 calendars. See the features or pricing: $9 a display a month.

Add a display to your office

Every room, on the door.

Live availability on every meeting room. Works with Microsoft 365, Exchange and Google Workspace.