Office 365 Platform Configuration and Provisioning

A guide to using Office 365 configuration and provisioning settings

Office 365 Platform Configuration and Provisioning

CloudMigrator includes a number of platform configuration and provisioning options for Office 365 migration that enable advanced automation scenarios. These options can be executed during the migration process and will run as part of the migration of users' data.

They allow you to automate many of the tasks that run in parallel with Office 365 data migration such as account provisioning, licensing and OneDrive activation.

Running these platform configuration tasks as part of the data migration means technicians can save time and reduce effort during the migration process.

In some cases these options can take a long time to run, as they are automating actions within your Office 365 tenant.

Performing any of these actions may result in changes to your Office 365 license utilization.

In some cases these operations can take a long time to run, as they are automating actions within your Office 365 tenant.

Getting Started

CloudMigrator utilises remote Powershell scripts to execute the configuration and provisioning tasks. This means there are some prerequisites that must be installed and configured on the primary server, but they are not required on any secondary servers.

If any of these modules are not installed, you will be notified within the interface:
Required Modules

Exchange Online

Exchange Online Powershell

Azure AD

Azure AD Powershell

System Requirements

Windows 10 Windows 8.1 Windows Server 2016 Windows Server 2012 or Windows Server 2012 R2 Windows 7 Service Pack 1 (SP1)* Windows Server 2008 R2 SP1*

For older versions of Windows, you need to install the Microsoft.NET Framework 4.5 or later and then an updated version of the Windows Management Framework: 3.0, 4.0, or 5.1 (only one). For more information, see

Running Tasks

Before utilizing any of the tasks, please specify values for Usage Location and License using the drop down lists. These options are used with several of the scripts.

  • Usage Location: Defines the geographical location of the user who is being assigned an Office 365 license.
  • License: Defines the license that you want to assign to users using CloudMigrator.
  • SKU Identifier: The SKU Code associated with your selected license. Automatically populated but may be overridden.
Licence Configuration

All tasks can be accessed via the destination platform configuration section. Scripts are separated into 4 sections:

  • Run before the whole migration (Global, Start)
  • Run before each user migration (User, Start)
  • Run after the whole migration (Global, End)
  • Run after each user migration (User, End)

Tasks can be executed together, enabling you to automate several actions within the migration process. They are enabled by ticking the checkbox next to the item.

Licence Configuration Licence Configuration

Available Tasks

In total there are 10 available pre-built tasks and the function of each is detailed below. In parentheses are linked tasks which can't be run together with the specified task. See the Licensing vs Global Scripts section for more information.

Run before the whole migration

1. Create Root Public Folder Mailbox

Creates a Root Public Folder Mailbox if it does not already exist and assigns permissions to it. This will be run at the start of a migration.
This script is recommended when migrating Exchange Public Folders to Office 365.

2. Provision OneDrive for Business for All Licensed Users (3,7,8)

Provision OneDrive for Business for All Licensed Users if O365 plan includes OneDrive. This will be run at the start of a migration.

3. License and Provision OneDrive for Business for All Users (2,4,7,8,9)

License and Provision OneDrive for Business for All Users with Full License available. The script will only process unlicensed users. You can assign licenses only to user accounts that have the UsageLocation property set. Some Office 365 services are not available in certain countries. This will be run at the start of a migration.

4. License Users for Exchange & Office (3,8,9)

License User for Exchange & Office Only. The script will only process an unlicensed user. You can assign licenses only to user accounts that have the UsageLocation property set. Some Office 365 services are not available in certain countries. This will be run for each user at the start of their migration.

5. Enable Mailbox Archive All Users (10)

Enables archiving on all user mailboxes. This will be run at the start of a migration. This script is recommended when migrating to Exchange Online Archive.

Run before each user migration

6. Check User Exists & Create

Check if a Mailbox, or Group exists for the User and create if it does not. This will be run for each user at the start of their migration.

7. Provision OneDrive for Business for User (2,3,8)

Provision OneDrive for Business for User if the Office 365 plan includes OneDrive. This will be run for each user at the start of their migration.

8. License and Provision OneDrive for Business for User (2,3,4,7,9)

License and Provision OneDrive for Business for User with Full License available. The script will only process an unlicensed user. You can assign licenses only to user accounts that have the UsageLocation property set. Some Office 365 services are not available in certain countries. This will be run for each user at the start of their migration.

9. License User for Exchange & Office (3,4,8)

License User for Exchange & Office Only. The script will only process an unlicensed user. You can assign licenses only to user accounts that have the UsageLocation property set. Some Office 365 services are not available in certain countries. This will be run for each user at the start of their migration.

10. Enable Mailbox Archive per User (5)

Enables archiving on a single user mailbox. This will be run for each user at the start of their migration.

Licensing vs Global Scripts

Execution/provision of licensing happens asynchronously and is not guaranteed to be immediate. As there is no way of knowing when these operations complete, or whether they have completed successfully, we do not allow certain combinations of scripts to be executed concurrently. For example, this means that if you run the global script to provision OneDrive then you cannot run the per-user script to provision OneDrive.

With regard to licensing scripts there are few things to note:

1. Users who are already licensed will be unaffected by the licensing scripts. Only unlicensed users are targeted.

2. If the user is unlicensed, the first licensing script you run will apply the chosen license. Any subsequent licensing tasks will not affect this user.

Additional Information

Logging from executing the Powershell scripts can be found in a special directory under the CloudMigrator installation e.g. C:\ProgramData\Cloud Technology Solutions\84a4969f-3d5d-4371-af6f-def973619e95\77b8c5fa-c2df-4ca6-9984-13c5fcd7008b\PowerShell\. Many of the pre-built scripts make use of replacement variables which are assigned values based on the migration configuration.