[SOLVED] Powershell - ExchangeOnlineManagement - Enable-OrganizationCustomization not possible due to upgrade of organization

Markus Wagner 0 Reputation points
2026-06-03T10:12:36.1866667+00:00

Hi!

Enabling organization customization in PowerShell module "ExchangeOnlineManagement" via

Enable-OrganizationCustomization

fails with this error message:

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

This happens since about 24 hours after we started test phase of "Teams Essential" yesterday. Is there anything we can do?

Thanks in advance!
Markus

[EDIT] I opened a support ticket with Microsoft, and after a brief phone call with support, the issue was resolved and `Enable-OrganizationCustomization ran without any errors.

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

Answer recommended by moderator

Markus Wagner 0 Reputation points
2026-06-05T05:25:32.2+00:00

I opened a support ticket with Microsoft, and after a brief phone call with support, the issue was resolved and Enable-OrganizationCustomization ran without any errors.

Was this answer helpful?

0 comments

3 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Michelle-N 19,705 Reputation points Microsoft External Staff Moderator
    2026-06-03T11:17:35.3833333+00:00

    Hi @Markus Wagner

    Based on your description, running Enable-OrganizationCustomization is throwing an error indicating that your organization is currently undergoing an upgrade. This background provisioning sequence was almost certainly triggered by adding the Teams Essentials service plan to your tenant yesterday.

    To help you resolve this and push the process through, please follow these steps:

    Before running any tenant-wide overrides, please double-check that the account you are using to connect to Exchange Online PowerShell has the necessary administrative permissions.

    Without these baseline administrative scopes, organization-level modification cmdlets can fail or return unexpected status blocks. If this background upgrade gets stuck or takes longer than the standard window, it locks out manual organization customizations.

    You can try running an internal lifecycle cmdlet designed to kick off or force-complete this pending backend upgrade process. After researching a similar case, you may refer to the following cmdlet.

    Complete-OrganizationUpgrade

    Once the upgrade utility completes its run, allow a few minutes for the fresh configuration data to propagate across the directory servers. Afterward, try running your original cmdlet again:

    Enable-OrganizationCustomization

    Please give this sequence a try and let me know if it unblocks your tenant or if you encounter any secondary errors while running the upgrade command!

    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click ""Comment"".

    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.

    Was this answer helpful?

  2. Markus Wagner 0 Reputation points
    2026-06-03T10:16:07.08+00:00

    The result of the following command is "True":

    Get-OrganizationConfig | fl IsDehydrated

    So I'm going to wait for "several days" to try it again. :-(

    Was this answer helpful?

  3. AI answer

    2026-06-03T10:12:51.4+00:00

    The error indicates that Exchange Online is running an internal upgrade process on the tenant. During this period, Enable-OrganizationCustomization is blocked and cannot be forced or bypassed.

    Key points based on the cmdlet behavior:

    • Enable-OrganizationCustomization is only needed once per Exchange Online organization.
    • If the organization is in a special backend state (such as being upgraded or dehydrated/hydrated), the service can temporarily block this cmdlet.
    • The state can be checked with Get-OrganizationConfig by looking at the IsDehydrated property:
      • True = Enable-OrganizationCustomization has never been run.
      • False = it has already been run.

    Actionable steps:

    1. Wait for the backend upgrade to complete. These service-side upgrades can take more than 24 hours; the cmdlet will only succeed once the upgrade finishes.
    2. After some time, run: 
         Get-OrganizationConfig | fl IsDehydrated
      • If IsDehydrated is True, try again: 
             Enable-OrganizationCustomization
      • If IsDehydrated is False, the organization is already customized and no further action with this cmdlet is required.
    3. If the upgrade state persists for an unusually long time (several days) and the error continues, open a support case with Microsoft 365/Exchange Online support so the service state of the tenant can be checked and, if needed, corrected.

    There is no supported workaround to force Enable-OrganizationCustomization while the organization is in an upgrade state.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

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.