This guide outlines the necessary prerequisites and steps for setting up Microsoft Azure Storage as a destination platform for your CloudM Migrate projects.
Important Note: If you are migrating from Azure Storage as a source, the data must have been previously imported to that storage using CloudM Migrate or CloudM Archive. It is not possible to export data from a generic Azure storage blob if the data was not originally placed there by a CloudM process.
Important Considerations for Azure Storage Migrations
- Owned Items Only: Currently, only owned items will be migrated to Azure Storage.
- Universal Compatibility: Microsoft Azure Storage supports every source platform and every item type supported by CloudM Migrate.
Phase 1: Setting up a Storage Account
To prepare your Azure Storage for migration, you must first create a storage account and a container.
- Sign in to Microsoft Azure: Go to the Microsoft Azure Home.
- Navigate to Storage Accounts: Open the Portal menu (hamburger icon) and select Storage Accounts.
- Create a New Account: Select Create on the Storage Accounts screen.
-
Configure Basics:
- Subscription/Resource Group: Select the appropriate subscription and existing group (or create a new one).
- Name: Choose a unique name (3-24 characters, lowercase and numbers only).
- Region: Select the region closest to your data's primary users.
- Configure Advanced & Data Protection: Set the Access Tier (Hot or Cool). Review optional data protection settings for blob data.
- Review and Create: Select Review + Create, then Create. Allow a few minutes for deployment.
Phase 2: Creating a Storage Container
- Access the Account: From the 'Storage Accounts' list, click your new account name.
- Open Containers: Scroll to Blob Services Containers.
- Add Container: Select + Container.
- Configure Details: Enter a Name and set Public Access Level to Private.
- Confirm: Click Create.
Phase 3: Obtaining Storage Access Keys
- Navigate to Access Keys: In your storage account menu, select Settings Access Keys.
- Copy Key: Select Show Keys and copy the value from Key 1 Key.
- Secure Storage: Save this key securely; you will need it for the CloudM Migrate destination settings.
Phase 4: Setting Up Azure Key Vault (Optional)
Required only if using encryption for migrated data. Ensure your Application ID and Client Secret are recorded accurately to allow CloudM to communicate with the Vault.