This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(51.2, 69%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPK%3C/text%3E%3C/svg%3E)
Unable to run: Enable-OrganizationCustomization
Error: 'Enabling customization is not allowed because the Organization is currently being upgraded.'
Tenant remains dehydrated and blocking Hybrid Configuration Wizard (HCW8077).
Manual mailbox creation also attempted but did not trigger hydration.
A cloud-based service included in Microsoft 365, delivering scalable messaging and collaboration features with simplified management and automatic updates.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(204.8, 44%, 29%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAB%3C/text%3E%3C/svg%3E)
Experiencing the same issue. Unable to enable organization customization and getting the error below:
Error: 'Enabling customization is not allowed because the Organization is currently being upgraded.'
Were you able to get someone from Microsoft confirm if this is a known issue these days?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Hi @Admin Bry Ambaco
At this time, there is no official Microsoft documentation that explicitly confirms this as a known issue. However, based on community discussions and observed cases, multiple users have reported the same behavior where the tenant remains stuck in the “Organization is currently being upgraded” state and Enable-OrganizationCustomization cannot complete.
Because of this, it appears to be a backend provisioning condition rather than something that can be resolved through tenant-side actions.
To ensure your issue is reviewed by the appropriate engineering team and to get the fastest possible resolution, I recommend raising a support ticket with Microsoft. Many cases with similar symptoms have been resolved after escalation, as backend intervention is often required to complete or reset the organization upgrade process.
You can submit a support request through the Microsoft 365 admin center if you have Global Admin access via the Microsoft 365 admin center.
Hi @Admin Bry Ambaco ,
Yes! I was experiencing the exact same issue and it has now been resolved today after escalating through Microsoft Support.
As Support Team mentioned, this is indeed a backend provisioning condition and cannot be resolved from the tenant side. The fix required backend intervention from Microsoft's engineering team to complete/reset the organization upgrade process.
My recommendation:
It took several days and multiple escalations but it was eventually resolved. Hang in there and keep following up persistently.
Good luck!
Hi @Samir Shrestha
Thank you for your update. I’m glad to hear the issue has been resolved. Your sharing will be valuable to others who may face the same challenge.
Hi @Samir Shrestha
From what you’ve described, this behavior typically indicates that the Exchange Online organization provisioning process is still pending or stuck in the backend.
The error returned by Enable-OrganizationCustomization “Enabling customization is not allowed because the Organization is currently being upgraded” means that Exchange Online still considers the tenant to be in an upgrade/provisioning state. Under normal circumstances, this process completes automatically. However, if it has remained in this state for more than 5 days and actions like mailbox creation did not trigger hydration, it is unlikely that there is anything further you can do from within the tenant to resolve it.
Additionally, the Enable-OrganizationCustomization cmdlet normally only needs to be run once. If customization is already enabled, running it again would typically return a different message indicating no further action is required. In your case, the error instead shows that the organization is still in an upgrade state, which points to a backend provisioning issue rather than repeated execution of the command.
Please note that we’re not Microsoft support, this is a user-to-user support forum. Moderators here don’t have backend access to Microsoft systems, so we can only provide guidance based on public documentation and cannot escalate this to backend.
If you have an active Microsoft 365 subscription and hold the Global Admin role, you can submit a support request directly through the Microsoft 365 admin center. Otherwise, please contact your IT administrator to raise a support ticket on your behalf.
You can read more at: Get support - Microsoft 365 admin | Microsoft Learn
If you receive any updates from Microsoft on this issue, please feel free to share them, as they may benefit other users facing the same challenge.
Thank you for your contribution and understanding.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Hi @Samir Shrestha
May I know if you have got any chance to check my answer? If you need further assistance, please feel free to let me know. Thank you!