'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
Fix Enable-OrganizationCustomization Organization Is Being Upgraded Error in Exchange Online
Question details
Exchange Online administrators are unable to run the Enable-OrganizationCustomization cmdlet to modify settings, receiving a continuous tenant upgrade error.
- Product
- Exchange Online
- Device & OS
- not provided
- Scenario
- Attempting to enable organization customizations via PowerShell to modify settings like external forwarding in outbound anti-spam policies.
- Observed behavior
- The command fails repeatedly with an error stating the organization is currently being upgraded, and this blocked state persists for more than 48 hours.
Ensure you have Exchange Administrator credentials and access to the Microsoft 365 admin center before checking the service health dashboard or submitting a support ticket.
Verify Microsoft Service Health for Incident EX673801
Microsoft identified a service regression that caused this tenant upgrade failure. Check if your tenant has received the progressive fix.
This specific failure was tracked by Microsoft under incident ID EX673801. A backend service update introduced a regression that prevented the tenant hydration process from completing successfully.
Microsoft has already deployed a progressive fix across affected environments. Administrators should first verify the deployment status for their specific tenant.
Sign in to the Microsoft 365 admin center using your global or Exchange administrator credentials.
Go to Health > Service health in the left-hand navigation menu.
Review the 'Issue history' or active issues for Exchange Online incident EX673801 to confirm if the fix has been fully applied to your environment.
Once the service health dashboard indicates the issue is resolved for your tenant, connect to Exchange Online PowerShell and run the Enable-OrganizationCustomization cmdlet again.
Contact Microsoft Support for Stuck Tenants
If your tenant has been in the upgrading state for over 48 hours after the incident resolution, manual backend intervention by Microsoft is required.
Looking for a Hassle-Free Office Suite? Try WPS Office
While Microsoft 365 handles complex enterprise server configurations like Exchange Online, you might just need a reliable, fast, and free suite for your daily document tasks. WPS Office offers a lightweight, highly compatible alternative for Word, Excel, and PowerPoint files without the complex administrative overhead.
- 1. Download the Installer: Visit the official WPS Office website and download the free installer for your operating system.
- 2. Install WPS Office: Run the setup file and follow the on-screen instructions to complete the fast installation.
- 3. Open Your Documents: Launch WPS Office to instantly open, edit, and save your existing Microsoft Office files with perfect formatting.
Frequently Asked Questions
What does Enable-OrganizationCustomization do?
By default, Exchange Online tenants are created in a dehydrated state to save space. The Enable-OrganizationCustomization cmdlet hydrates the tenant, allowing administrators to modify customized settings, transport rules, and security policies.
How long does the organization upgrade process normally take?
Under normal circumstances, the process triggered by Enable-OrganizationCustomization takes a few minutes to an hour. If it exceeds 48 hours, it indicates an error or a backend server issue that requires troubleshooting.
Why do I need to run this command to allow external email forwarding?
Modifying default outbound anti-spam policies to allow external forwarding requires your tenant to be fully hydrated. Running this command unlocks the ability to customize these specific Exchange Online security policies.
