apoth0r.com

Enable-OrganizationCustomization is only available in the Cloud-based Exchange Online & Exchange Online – Advanced Threat Protection products

Status of your tenant – Enable-OrganizationCustomization

Errors that occur with the configuring and deployment of RBAC, rules or coexistence technologies hydration status of your tenant at Office 365.

Each Office 365 tenant is not “hydrated” by default, hydration is the adding of many settings in the Exchange Online directory service per tenant – by default tenants do not need these settings and so rather than creating the settings per tenant, each tenant shares these common settings. The hydrating of the tenant is the process of including these common settings in your tenant and operating at a hydrated status.

Examples of this include;

• New role groups or management roles
• Role assignment or modifying built in assignments
• Creating or modifying an Outlook Web App policy
• Creating or modifying a retention policy

To enable your own Transport Rules, Free/Busy Rich Coexistence and custom RBAC settings require that all the “common” settings in the directory are copied to the tenants area of the directory. To do this, means you need to run the Enable-OrganizationCustomization cmdlet in remote PowerShell to Exchange online.

Once this is complete the GUI will create RBAC, rules, free/busy etc. without having the Exception has been thrown by the target of an invocation error.

The Hybrid configuration Wizard is designed to normally inflate the tenant on your behalf, but in the case where you are met with the above exception error – please use the following Powershell Commands.

Powershell Command to Check Hydration Status

To test if your Office 365 is indeed Hydrated or Dehydrated please use the below command;

1. Start the Windows Powershell
2. $cred=Get-Credential tenant_admin@tenant.onmicrosoft.com (If domain
3. $EOSession = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.outlook.com/PowerShell/ -Credential $Cred -Authentication Basic -AllowRedirection
4. Import-PSSession $EOSession  -AllowClobber
5. Get-OrganizationConfig | fl Identity, IsDehydrated

You will then be provided information regarding the dehydrated status of either True or False

Powershell Command to Enable-OrganizationCustomization

The exact steps to perform on your Office 365 tenant before configuring RBAC, rules or coexistence are as follows:

1. Start the Windows Powershell
2. $cred=Get-Credential tenant_admin@tenant.onmicrosoft.com (If domain
3. $EOSession = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.outlook.com/PowerShell/ -Credential $Cred -Authentication Basic -AllowRedirection
4. Import-PSSession $EOSession  -AllowClobber
5. Enable-OrganizationCustomization