This backend upgrade/provisioning state is blocking our PST migration

Brian Stutesman 0 Reputation points
2026-09-17T23:29:54.2033333+00:00

We are migrating our organization's email to Exchange Online and need to import PST files through Microsoft Purview.

I need to assign the Exchange Online Mailbox Import Export role, but the tenant requires Organization Customization first.

Get-OrganizationConfig | Format-List IsDehydrated

returns:

IsDehydrated : True

When I run:

Enable-OrganizationCustomization

Exchange Online returns:

Enabling customization is not allowed because the Organization is currently being upgraded. Please try again after the Upgrade is complete.

This backend upgrade/provisioning state is blocking our PST migration and production email cutover. Please check the tenant's Exchange Online upgrade/provisioning state and remediate it so Enable-OrganizationCustomization can complete.

Exchange Online
Exchange Online

A cloud-based service included in Microsoft 365, delivering scalable messaging and collaboration features with simplified management and automatic updates.

0 comments

1 answer

Sort by: Oldest
Most helpful Newest Oldest
  1. Teddie Dang 1,270 Reputation points Independent Advisor
    2026-09-17T23:52:52.6666667+00:00

    Hi @Brian Stutesman

    The error returned by Enable-OrganizationCustomization “Enabling customization is not allowed because the Organization is currently being upgraded” indicates that Exchange Online currently considers the organization to be in an upgrade or provisioning state. This can prevent Enable-OrganizationCustomization from completing.

    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 normal tenant-side configuration. I recommend raising a support ticket with Microsoft Support so they can investigate the Exchange Online provisioning status and escalate the issue to the appropriate engineering team if necessary. Similar cases reported by other customers have required escalation, with service-side intervention used to resolve the organization upgrade state.

    You can submit a support request through the Microsoft 365 admin center if you have Global Admin access via the Microsoft 365 admin center.

    You can read more at: Get support - Microsoft 365 admin | Microsoft Learn     

    Reference: Exchange Online tenant is stuck in 'Organization is currently being upgraded' state for more than 5…

    Was this answer helpful?

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.