How to Fix Enable-OrganizationCustomization Error During Microsoft 365 Upgrade
Question details
Users are unable to run the Enable-OrganizationCustomization command because the Microsoft 365 tenant is still being upgraded or provisioned.
- Product
- Microsoft 365
- Device & OS
- not provided
- Scenario
- Setting up a new Microsoft 365 tenant or attempting to modify organization configurations and anti-spam policies via Exchange Online PowerShell.
- Observed behavior
- The Enable-OrganizationCustomization cmdlet fails to execute, returning an error message stating that the backend organization setup has not finished.
Ensure you have global administrator or Exchange administrator privileges in your Microsoft 365 tenant and can access the Microsoft 365 Defender portal.
Wait for Provisioning and Use the Defender Portal
Bypass the PowerShell error by managing your policies directly through the web portal while the backend upgrade finishes.
The Enable-OrganizationCustomization cmdlet typically only needs to be run once in an Exchange Online organization to enable the creation of custom configurations. When a new tenant is created, the backend setup takes some time. Waiting for this automated process to finish usually resolves the error.
Allow sufficient time (usually a few hours, up to 24 hours) for the new Microsoft 365 tenant provisioning to fully complete on Microsoft's backend servers.
Open a web browser and navigate to https://security.microsoft.com/antispam to access the Microsoft 365 Defender portal.
Configure your anti-spam and security policies directly through the graphical interface instead of using PowerShell.
Once the tenant is fully provisioned and if customization is still required for other scripts, run the Enable-OrganizationCustomization cmdlet again in Exchange Online PowerShell.
Escalate to Microsoft Backend Support
If the tenant provisioning process takes unusually long or appears stuck, contact Microsoft Support for backend investigation.
Looking for a Hassle-Free Office Suite? Try WPS Office
While Microsoft 365 tenant configurations require backend provisioning and complex PowerShell commands, standard document creation shouldn't be complicated. WPS Office provides a free, lightweight, and user-friendly alternative to Microsoft Office desktop apps, ensuring seamless format compatibility without the need for complex administration.
- 1. Visit the WPS Office Website: Navigate to the official WPS website to access the free download page.
- 2. Download the Installer: Click the download button corresponding to your current operating system.
- 3. Install and Launch: Run the setup file and follow the on-screen instructions to start using your hassle-free office suite.
Frequently Asked Questions
What is the purpose of the Enable-OrganizationCustomization command?
Enable-OrganizationCustomization is an Exchange Online PowerShell cmdlet used to enable the creation of custom configurations and policies (such as role groups and management role assignments) in a new Microsoft 365 tenant. It shifts the tenant from a dehydrated state to a hydrated state.
How long does Microsoft 365 tenant provisioning usually take?
Backend tenant provisioning and upgrades typically complete within a few hours. However, in some scenarios, it may take up to 24 hours for all background processes to finish completely.
Can I manage anti-spam policies without running this command?
Yes, while the backend upgrade is still processing, you can bypass the PowerShell requirement by managing your anti-spam and security policies directly through the Microsoft 365 Defender web portal.
