You can get to Azure Migrate directly @ https://portal.azure.com/#create/Microsoft.AzureMigrate
Setting up Device42 from the Azure Migrate Portal
1. Begin by signing up for an Azure account if you don’t already have one. You’ll have to provide a credit card to verify your identity, and agree to the conditions to continue:
2. Click the button to continue to the Azure portal, and once there, choose “Assess and Migrate servers” as pictured below:
3. Next, you’ll want to begin adding migration tools; click “Add a tool”:
4. Choose an existing Resource Group, or click the “Create new” link (highlighted) to create a new one. The “Resource Group” name represents the group of machines you’ll be migrating, and can be a name of your choosing, but should be descriptive; Then press “OK”:
5. Give your migration project a name, and when finished, press “Next” to continue:
6. Select Device42 as your Azure Migration assessment tool by clicking on it so it is selected as pictured. Click “Next” to choose Device42:
7. You can add a migration tool at this point if know which you want to use, but the default is to skip adding a migration tool for now (you can choose a tool when you are ready to migrate). Ensure the “skip adding a migration tool for now” checkbox is checked, and choose “Next” to continue.
8. Review your tool choice(s) and then click “Add tool(s)” to continue:
You’ll see confirmation the deployment has been initialized:
9. Click “Learn more” to head to the Device42 information page:
10. From the Device42 information page, click the orange “Try it now, free” button to jump over to the Device42 download page:
11. Fill out the form & click “Start your Free Trial” to download Device42. Your download should be e-mailed to you immediately.
For help installing Device42, head over to the Device42 documentation @ https://docs.device42.com.
1. The Getting Started with Installation section is a great place to begin! https://docs.device42.com/getstarted/installation/
2. Once you’ve installed, you’ll want to begin discovering your environment. See the “Getting started with autodiscovery” section of the documentation here – https://docs.device42.com/getstarted/getting-started-with-auto-discovery/
3. When you’ve finished with discovery and assessment, you can export your discovered data back to Microsoft Azure. Instructions on exporting can be found here:
Exporting your Business Apps to Azure for Migration
Register an Azure Active Directory user
- Login to Azure Portal, and create an “App Registration” in Azure Active Directory. You’ll need this user to authenticate to Azure when uploading your export. Create a User:
- Create Client Secret and Save the value for Device42
- Create a new Migration Project (if you haven’t already; See the prior section on this page.):
Collect required information from Azure
Collect the following information from Azure:
- Tenant ID: Azure Active Directory -> Properties
- Subscription ID: Subscriptions
- Client ID: Azure Active Directory -> App registrations
- Client Secret: Saved from app registration creation
- Migrate Project Name: The name you chose when creating the project.
Export your Business Application(s) from Device42
- Login to Device42 and go to Business Apps. Select one or more Business App(s) to export by checking the check-boxes next to them, and Choose ‘Create Migration for Selected Objects’:
- Select ‘Azure’ as your Target from the dropdown:
- Enter Migrate Project information from Azure collected in the last step:
- Click Export. Go back to the Azure Migrate Hub, and Click Refresh. You should now see your exported data in Azure!
Reviewing your Device42 exports in Azure Migrate
After exporting your Business Applications from Device42 [as explained in the prior section] to the Azure Migrate portal, log back into the Azure Migrate portal, or refresh if you are already logged in. You should see something similar to the following example (but with your data, of course):
If you need help with steps or processes discussed on this page and haven’t found the answer here, please don’t hesitate to reach out to email@example.com!