Microsoft 365 Error Codes

Fix Enable-OrganizationCustomization Errors During Exchange Upgrade

Steve KSteve K Oct 10, 2026 868 views

Question details

The administrator needs to bypass or resolve an error preventing the execution of the Enable-OrganizationCustomization command during an Exchange Online upgrade.

How to Fix Enable-OrganizationCustomization Errors During Exchange Upgrade
Product
Exchange Online
Device & OS
not provided
Scenario
Attempting to add roles such as ApplicationImpersonation for migration tools using PowerShell.
Observed behavior
The system rejects the command, displaying an error message stating that customization is not allowed while the organization is currently being upgraded.
Before you start

Ensure you have global administrator or Exchange administrator privileges in your Microsoft 365 tenant and access to the Exchange Online PowerShell module.

Solution 1Recommended

Wait for the Organization Upgrade and Retry the Command

Exchange Online locks customizations during automated tenant upgrades. Waiting for this background process to finish is the primary resolution.

Microsoft 365 routinely performs automated background upgrades on Exchange Online tenants. During this time, the organization is temporarily locked from structural changes to prevent data corruption.

1
Wait for background processes

Give the Exchange Online tenant up to 24 to 48 hours to complete its automated background upgrade.

2
Reconnect to Exchange Online

Open PowerShell as an administrator and reconnect to your tenant using the Connect-ExchangeOnline cmdlet.

3
Run the command again

Execute the Enable-OrganizationCustomization cmdlet. Note that this command only needs to be run successfully once per tenant.

4
Add the required roles

Once the customization is enabled, proceed to assign the necessary roles, such as ApplicationImpersonation, to your migration tools.

Wait for the Organization Upgrade and Retry the Command
Command Execution Frequency: If you have run this command in the past successfully, you do not need to run it again. The dehydration state is permanently lifted after the first successful execution.
Free Microsoft Office alternative

Try WPS Office as Your Lightweight Productivity Alternative

While managing Microsoft 365 backend infrastructure like Exchange Online requires specific admin tools, your daily document and planning workflows shouldn't be complicated. WPS Office provides a free, lightweight, and highly compatible suite for all your administrative planning and documentation needs.

  1. 1. Download the installer: Visit the official WPS Office website and download the free version for your operating system.
  2. 2. Install the software: Run the installer and follow the on-screen prompts to set up the office suite on your computer.
  3. 3. Open your files: Instantly open, edit, and save your existing Microsoft Office documents without any formatting loss.
Seamlessly draft your PowerShell scripts and migration plans using WPS Writer.Fully compatible with Microsoft Office document formats (.docx, .xlsx, .pptx).Lightweight installation with minimal system resource requirements.Familiar, easy-to-use tabbed user interface for seamless software migration.
QA img-9

Frequently Asked Questions

Why do I need to run Enable-OrganizationCustomization in Exchange Online?

By default, Exchange Online tenants are created in a dehydrated state to save system resources. Running this command hydrates the tenant, allowing administrators to make custom role assignments and organization-wide configuration changes necessary for advanced migrations.

How long does an Exchange Online organization upgrade typically take?

Automated background tenant upgrades usually complete within a few hours to a full day. If you are locked out of customizations for more than 48 hours, the process might be stuck, and you should contact Microsoft support.

Can I check the status of my organization's upgrade in PowerShell?

You can use the Get-OrganizationConfig cmdlet to review general organization settings, but specific backend upgrade statuses might not be entirely visible to administrators. If the customization command continually fails with the upgrade error, opening a support ticket is the most effective diagnostic step.