Hi Everyone, this is Prem, I have worked as Microsoft 365 support ambassador. We see a lot of ticket for “Enable Organization Customization in Office 365”.
In this blog, I am going to share a common step which we used to suggest to Office 365 Admins to enable it.
When we try to do some changes in Office 365 specifically in Security admin center and compliance admin center, it gives the error to Enable Organization Customization.
It mostly happen when you have a new tenant and/or you have not used all the service of office 365.
When we get a new tenant from Microsoft, it initially stays in the tiny tenant format where all the services are not provisioned for the Office 365 tenant in the backend.
Tiny tenant states does not allows us to modify or change exchange related services mostly even which are included in your existing License.
You may be prompted to run the Enable-OrganizationCustomization cmdlet before you create or modify objects in your Exchange Online organization.
Now we know when and why it happens, lets see how we can enable it.
Steps to Enable Organization Customization in Office365:
We will need help of Windows PowerShell to run the command, the PowerShell has to be first connected to exchange admin center and then it will allow us to execute the command.
Steps to connect to Exchange admin center using PowerShell:
Search for windows PowerShell on your computer and run it as an administrator:
If opened correctly, it should look like this:
We will have to first install the ExchangeOnlineManagement module that will help us to connect to Exchange online using PowerShell.
Even before installing the module, we will have to make sure that the execution policy set on your computer will allows us to install it.
Setting the Execution policy to Remotesigned, allows us to install the scripts which are digitally signed.
To set the execution policy to RemoteSigned, Run the following Command:
Set-ExecutionPolicy Remotesigned -Scope CurrentUser
Allow it to set the execution policy if prompted by entering A.
After that run:
Install-Module -Name ExchangeOnlineManagement -Scope CurrentUser
Allow permission to install if asked by entering Y.
Optional: If you want you can use the command: Install-Module -Name ExchangeOnlineManagement -Scope CurrentUser -Force
Using -Force Parameter at the end of the install-module command, make sure that the latest version of the Module gets installed for you.
After that run the below command to Import the ExchangeOnlineManagement module:
Import-Module -Name ExchangeOnlineManagement
Now we should be able to run the Command to connect to Exchange Online, for that run:
Enter your Global or Exchange Admin email address and password and it should get connected to ExchangeOnline on the PowerShell.
Once successfully connected, you can should see a message like this:
We will now run the below command to Enable Organization Customization:
To Enable Organization Customization on your Office 365 Tenant, run:
Once you run the above command and it completes without any error, It will take at least 30 minutes to enable all the services for your tenant in the back end.
For my Tenant, it is already enabled, so I get this error Message “This operation is not required. Organization is already enabled for customization.“:
You can run the below command to check the IsDehydrated parameter’s state:
Get-OrganizationConfig | fl IsDehydrated
If it is False, then we are good to go, but if it is True then you will have to try again after 15 minutes by running the Enable-OrganizationCustomization command again.
If you get the some error message that your Tenant is currently being upgraded or currently upgrading, try to run the Enable-OrganizationCustomization command couple of times and check.
Alternatively for this “your Tenant is currently being upgraded” error, you can try to use the Admin center method to enable the Organization Customization for your office 365 and if you get the same error that you tenant is being upgraded, try it couple of times and check.
These are the steps which we use for this Enable-OrganizationCustomization issue, do let us know if this helped you to fix the issue.
In case you are still not able to enable it or get any error then the best way to fix it is to connect with Microsoft by creating a ticket or you can refer the below link as alternative.
Related Useful links:
- Enable organization customization on Mac
- Enable Organization customization without Powershell
- Create a Support Ticket with Microsoft