CloudM Migrate Azure Environment Setup

CloudM have designed an Azure Marketplace product to allow for the easy deployment of CloudM Migrate in a multi-server configuration in your own Azure environment.

You can find it here: 

The deployed solution is a fully-fledged CloudM Migrate multi-server installation, it can be managed, using the same methods and tools as you would any other Virtual machine in Azure.

Deploying this solution comprises 5 simple steps, that enable you to deploy a multi-server CloudM Migrate installation.

Support When Using This Solution

For issues regarding CloudM Migrate, please contact our support. For any other issues, related to the Azure infrastructure please contact Azure support.

Please ensure that you have adequate Core Count in order to deploy the Solution. Please see this Microsoft Support Article for more information.
Please ensure that you have purchased your CloudM Migrate licenses prior to completing the deployment of your solution.

In this Article

The solution is available from the Azure Marketplace and can be found by searching for "CloudM Migrate"



A direct link to the solution in the marketplace is available here: Microsoft 365 Migration Azure

Step 1: Configure Basic Settings


Either select a pre-existing Resource group or create a new group to contain the resources. Additionally, pick a location for this resource group.

Step 2: Configure Storage and Network Settings

A Virtual Network will be automatically created by the solution.


You will need to confirm the subnet information, ensuring that the subnet name and address prefix is present.

(This information is pre-populated, and just needs confirming)

You will need to provide a DNS Prefix, this should be unique.

Step 3: CloudM Migrate Servers 

This step is split into 3 sections, Primary Servers, SQL and Secondary Servers.


When entering passwords please be aware of the password requirements within Azure.

The solution pre-populates the size requirement for a CloudM Migrate Primary Server. This size is chosen primarily to produce a cost-effective migration solution, however, in some cases, it may be required to increase the specification of either the Primary or Secondary servers to an SKU other than the one populated by the solution. Please refer to the System Requirements article for more information on the requirements for CloudM Migrate.

Customers are free to make these changes but should be aware of the cost implications of doing so.

As the solution is deployed in your own Azure environment it is the responsibility of the system administrator to ensure the Virtual Machines running CloudM Migrate are up to date.

Primary Servers



Ensure that you record the username and password entered in this step. Failure to do so will require resetting the VM password.

Enter a Username and Password, that will be used to access the Primary Server by RDP. 

SQL Server Express

Ensure that you record the username and password entered in this step. Failure to do so will require redeploying the whole solution.


CloudM Migrate uses a SQL Server Express install as part of the migration process. This SQL instance is located on the Primary CloudM Migrate server. 

Enter a username and password to be used for the SQL instance.

Secondary Server

Enter the number of servers required. In general, is suggested that you have a secondary server per 20 users.

It is recommended that you always deploy at least 1 Secondary server. This will allow you to increase the number of Secondary Servers at a later date.

For most migrations, 5 secondary servers are recommended as a starting point.

The max number of Secondary Servers is 100, the best practice is 1 server per 100 users.


Step 4: CloudM Migrate Settings

 Ensure that you record the username and password entered in this step. Failure to do so will require redeploying the whole solution.


In most cases, it is not required to change the Max Users per Secondary Server value.

Enter a username (full email address) and password to be used to log in to the CloudM Migrate web interface. Be sure to record these details.

Destination Microsoft 365 Migration Configuration


Please ensure that you have purchased your CloudM Migrate licenses prior to completing the deployment of your solution. Visit our website for more information.

Enter the destination Microsoft 365 Domain you are migrating to.

Enter the Global Admin username for the domain you are migrating to.

Enter the CloudM Migrate license key to be used for this migration.

Select whether you wish to install Google Chrome on the Primary Server during creation.

Step 5: Summary

This page shows a summary of your entered settings. You can now click through the start of the deployment. It will take on average 30-35 minutes, depending on the number of secondary servers selected for deployment.

You should access CloudM Migrate via https://cloudm.local/ on the primary server, otherwise, the firewall rules need updating for external access to the DNS name assigned by Azure.

Using The Solution

Once the solution is deployed, you can log in to your CloudM Migrate instance by connecting to your Primary server's IP/ DNSName, and accessing the CloudM Migrate web interface.

This can be accessed from the CloudM Start Menu folder under CloudM Migrate Local Website, or by browsing to https://cloudm.local/ from within a web browser on the Primary Server.

Updating CloudM Migrate

From time to time, CloudM will release new versions of CloudM Migrate, often with new or updated features. It is the responsibility of the systems administrator to update CloudM Migrate on the primary and secondary servers.Please see this article Remotely Upgrading Multiple CloudMigrator Installations for a method of updating CloudM Migrate in a Multi-Server environment.


Was this article helpful?
0 out of 0 found this helpful