1. CloudM
  2. Migrate
  3. Engineering References
  4. How-tos and Common Features

Migrating to and from Azure Storage

Permanently deleted user
Updated
Exclamation.png Currently, only owned items will be migrated.

 

Exclamation.png Microsoft Azure Storage supports every source platform and every item type for storage.

 

Exclamation.png Please note that CloudM Migrate migrates to Azure Blob Storage, and not Azure Files.

 

General and Source Platform prerequisites 

You will be required to be logged in with a Microsoft account on the tenant you wish to migrate to.  

 

Destination Platform prerequisites

Setting up a Storage Bucket

  1. Sign in to Microsoft Azure Home.
  2. Open the Portal menu, using the Hamburger menu icon.
  3. Select Storage Accounts.
  4. On the Storage Accounts screen, select Create
  5. On the Basic tab, enter the following information:
    • Subscription - Select the subscription for the new storage account.
    • Resource Group - Create a new resource group for this storage account, or select an existing one
    • Storage Account Name - Choose a unique name for your storage account. Storage account names must be between 3 and 24 characters in length and may contain numbers and lowercase letters only.
    • Region - Select the appropriate region for your storage account.

Create_account.png

  1. On the Advanced tab, set Access Tiers to either HOT or COOL, as required. 
  2. On the Data Protection tab, you can configure data protection options for blob data in your new storage account. These options can also be configured after the storage account is created.
    • In CloudM Archive, the data retention rules can be rewritten using the Data Retention policies.
  3. Once you have configured these settings, select Review + Create, and then select Create again.
  4. The Storage Account will be created. This process can take a couple of minutes to complete.
  5. You will need to navigate back to the Storage Accounts screen.
  6. Click on the name of the newly created account in the list of Storage Accounts.
  7. In the menu, scroll down and select Blob Services > Containers.
  8. Now, select the + Container button,
  9. In the pop up screen, enter:
    • Name - A unique name for the container
    • Public Access Level - Set to Private
    • Advanced Settings > Encryption Scope - Leave as default.
  10. Click on Create.

Add_a_new_container_AZURE_2.png

  1. On the same Storage Account page, select the Settings > Access Keys menu option.
  2. In the Access Keys page, click on the name of the newly created key and then click again on the current version.
  3. Select the Show Keys button at the top of the screen.
  4. Copy the value in the Key 1 > Key field. You will need this value later so you should copy into a document or notepad application.

Add_a_new_container_AZURE3.png

 

Setup Azure Key Value (optional - only complete if requiring encryption)

We don't require you to use encryption, but you can use the following process if it is required.

Use the same method (either using encryption or not using encryption) throughout your project to avoid issues.

  1. In the Search bar at the top of the screen, enter Key Vaults and select the Key Vaults option.
  2. On the Key Vaults screen, select Create.
  3. Under the Basics tab, enter the Subscription, Resource Group and Name.
  4. Select Create + Review, and then select Create again,
  5. When the Key Vault is being created, you will be taken away from the Key Vaults section so navigate back to Key Vaults using the Search bar.
  6. On the Key Vaults screen, select the newly created Key Vault.
  7. Select Keys.
  8. Select Generate.

Key_Vault_1.png

Key_Vault_2.png

  1. Click on the newly created key, copy the key identifier without the version info at the end. This is the value for the CloudM Migrate Key Vault URL setting.

Key_Vault_3.png

  1. Navigate to Azure Active Directory -> App Registrations, and select New registration.

Key__Vault_4.png

  1. Fill out the details and select Register.
  2. On the App Registration screen, click on the name of the newly registered application.
  3. Select API permissions from the menu on the left side of the screen.

Key_Vault_5.png

  1. Select Add a permission and add either of the following:
    • User Read
    • user_impersonation

Key_Vault_6.png

  1. In the menu on the left, select the Certificates & Secrets option. 
  2. Select New client secret and copy the Secret ID. This is the value for the CloudM Migrate Azure key vault client secret setting.

Key_Vault_7.png

  1. In the left side menu, select Overview, and copy the Application (client) ID for the CloudM Migrate Azure key vault client ID setting.

Key_Vault_8.png

  1. Return to Home > Key Vault,
  2. Ensure that the Permission Model is set to Vault access policy,
  3. Select + Add Access Policy,

Key_Vault_9.png

  1. On the Add access policy screen, make sure that the Select principal value is set to the required Application (as set in step 4 and 5),
  2. Ensure that the Key Permissions field is set to Get, Decrypt, Encrypt and Unwrap Key.
  3. Select Add.

Key_Vault_10.png

 

 

Configure Source Platform settings

Azure Storage 

Source_platform_-_Azure.PNG

Account Details

  • Domain Name – The name of the Microsoft domain to migrate to. This may be either a primary or secondary domain. 
  • Storage Account Name - The name of the Azure storage account.
  • Account Key - The Access Key for the Azure storage account.

 

Azure Storage Details

  • Container Name - The name of the container that has been created in Microsoft Azure, under Home > Storage accounts > (Your Storage Account) > Containers.

Azure_Storage_-_Advanced_Settings.PNG

 

 Options

  •  Page Size - Page Size to use when Listing Objects in Cloud Storage.

 

Azure Key Vault Decryption Options (optional - complete if encryption required)

  • Key Vault Decryption Key Url - The Url of the decryption key in Azure Key Vault.
  • Client Id - Client Id used to access Azure Key Vault.
  • Client Secret - Client Secret used to access Azure Key Vault.

 

Customer-Supplied Key Decryption Options (optional - complete if encryption required)

  • Decryption Key File Path - The location of your decryption key file.

 

Configure Destination Platform settings 

Azure StorageDestination_Platform_-_Azure_Storage.PNG 

Account Details

  • Domain Name – The name of the Microsoft domain to migrate to. This may be either a primary or secondary domain. Note: you can only migrate users to one domain at a time. If you have both primary and secondary domain users, they must be processed in separate migrations.
  • Storage Account Name - The name of the Azure storage account.
  • Account Key - The Access Key for the Azure storage account.

 

Azure Storage Details

  • Container Name - The name of the container that has been created in Microsoft Azure, under Home > Storage accounts > (Your Storage Account) > Containers.

 

Azure_Destination_-_Advanced_Settings.PNG

 

Storage Options

  • Max File Size - The maximum size of the files to be uploaded (bytes).
  • Cache Existing Object Details - Cache details of existing objects in the destination. Setting this to True will decrease the number of HTTP requests made per item at the expense of increased disk usage.
  • Compress Objects - Compress the Objects before they are uploaded. Setting this to True will use less cloud storage space at the expense of slowing down the Import. 

 

Azure Key Vault Decryption Options (optional - complete if encryption required)

  • Key Vault Decryption Key Url - The Url of the decryption key in Azure Key Vault.
  • Client Id - Client Id used to access Azure Key Vault.
  • Client Secret - Client Secret used to access Azure Key Vault.

 

Customer-Supplied Key Decryption Options (optional - complete if encryption required)

  • Decryption Key File Path - The location of your decryption key file.

 

Select which users to migrate

It's now time to add which users you'd like to migrate.

Add_Items_to_migrate.PNG

When migrating, you may be able to Get Users from the actions menu. If this option is unavailable, you can manually import users via a CSV file or simply add them individually via the plus icon.

Selecting a star next to any specific user or users will prioritize their migration. When a migration starts, threads will be assigned to any starred user so that their migration can start immediately.  

At this point you can choose what to migrate for each user. You can migrate mail, contacts and calendars.

Actions_-_365.PNG

Enter your user's full email address within the Export Name field. If you have already created your users, then you will just need to enter their username.

Items are migrated to Azure Storage as follows:

  • Emails: EML + Metadata
  • Calendars: Metadata only
  • Appointments: ICS + Metadata
  • Files: as-is + conversion to MS formats

 

Select how much mail to migrate

CloudM Migrate lets you decide how much mail you would like to migrate to your shiny new system.

mceclip1.png

If you are changing your email address as part of the migration you can verify that the domain names are correct here. You can also specify specific address replacements in the respective section of the advanced settings.

For more information on domain and address replacements, see this page.

Start your migration

We know that you may want to start your migration in the middle of the night, or over the weekend, but we don't expect you to stay up in order to do so. With CloudM Migrate, you can decide to schedule exactly when you'd like the migration to occur.

schedule_migration.PNG

Start the migration.

Start_Migration.PNG

Review your migration results

During the migration process, CloudM Migrate will report back in real time exactly who is being migrated and the items being processed. All you now need to do is sit back, relax and wait for your migration to complete.

Check the progress of your migration.

Once complete you can download a full report for your migration.

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