Azure Migrate
Azure Migrate helps you to discover on-premises workloads and assess them for Azure suitability. You can also find the cost to run the workload in Azure.
1. Discovery and assessment for on-premises virtual machines
2. Inbuilt dependency mapping for high-confidence discovery of multi-tier applications
3. Intelligent rightsizing to Azure virtual machines
4. Compatibility reporting with guidelines for re-mediating potential issues
5. Integration with Azure Database Management Service for database discovery and migration
If you have a technical issue, please open a post on the MSDN forum.
-
Move resource(s) to another location.
I wish I could move resource(s) to another location just like I can move it now to another Resource Group or Subscription.
For example, I just created a new Function App, with a new Storage Account and put them in a new Resource Group. After all resources were provisioned, I realized that I forget to picked up a location I want. Instead of South Central US, I need them to be in West US.
It would be super handy if I can just move them all to the West US location. Instead, I have to delete resources and recreate them…
118 votes -
Support for physical machine migration
Add support for assessing physical servers for migration.
39 votes -
Migrate VM to Azure Stack
As a service provider, having to possibility to use Azure Migrate for the Migration of On-premise VM of our customers to our multi-tenant Azure Stack platfom will be very helpfull
36 votesSupport for migration to Azure Stack is in the backlog, but not yet prioritized. Please use the comments section and upvote the ask if you would like this functionality to light up soon.
-
Spreadsheet pricing
would be great to have a spreadsheet import for Azure pricing. There are many times where customers want to know how much their VMs will cost to run, but they don't or can't install anything. If there was a way to take a spreadsheet with CPU, Memory, and disk space info and just import that list to the Azure Pricing Calculator or Azure Migrate to get pricing info, that would be perfect.
33 votesThis ask is under review.
-
Automated migration assessment tool from one subscription to another.
when a customer wants to move from subscriptions like Pay-As-You-Go to CSP we used to use this tool http://azurecspassessment.azurewebsites.net/ for assessment. Since the tool is shut down it has become very difficult to assess the resources manually. It is taking hours when moving a big customer from PAYG to CSP. Some resources in PAYG are not supported in CSP or having dependencies. This is creating a huge impact on time, labor, and cost (down time in re-deploying the services). Please do review and hope you come up with a new tool.
24 votes -
I want to migrate Hyper-v datacenters using Azure Migrate
Today Azure Migrate can only discover VMware environments. We want to be able to discover Hyper-v environments and assess+migrate them to Azure.
24 votesThis functionality is currently in preview. If interested, please sign up here: http://aka.ms/migrate/previewsignup
-
List of the Powershell Commands for Azure Migrate
I can see the commands for Azure Site Recovery but are there any new ones for the Azure Migrate platform?
13 votes -
Currently Virtual machines created from Marketplace resources with plans attached cannot be moved between subscriptions or Resource Group.
Currently, Virtual machines created from Marketplace resources with plans attached cannot be moved between subscriptions or Resource Group.
It would be very helpful if you could add this feature as soon as possible. Due to this limitation, customer's have to set up the VM from scratch.
13 votes -
Limit VM collection scope to folders
We are running clusters with lots of VMs (1700 in one case) but organise the VMs into folders which contain VMs that belong to a specific customer. At the moment the scope for data collection is limited to selecting a Cluster, but no more granular than that. So if I create an Azure Migrate project for a customer with 100 VMs in their folder, it still has to collect data for all 1700 VMs in the cluster.
I have tried using a user account to connect to vCenter that has read-only access to just the folder containing the VMs I…
11 votes -
"Start Delta Sync" Button
We need a button to force a delta sync. I'm in a scenario right now where we have a migration soon and don't have the time to wait an hour for the delta sync to start by itself. Azure Migrate replication has been down for a week and we don't know how long the deltas are going to take so a button like this would be very helpful.
9 votes -
Machine Selection for Assessment
After discovery, choosing machines for a group is very difficult. It displays 9 machines at a time, select all doesn't allow you to unselect individual machines, and you can't search for parts of machines names to then select a group. Would be great if the selection process for groupings offered more customization. I am doing an assessment now if you want to see what is going on.
8 votesWe are planning to add more customization/filtering option for grouping in Azure Migrate. Filtering by name, OS, IP Address is something that we currently support. We are planning to add filtering by vCenter host/cluster/folder, it would really help us if you could comment on the criteria that you use for grouping VMs.
-
Add support for Azure Databox
Integrate Azure Migrate with Azure Databox for Offline Migration for large VM estate.
VHD files should be placed on Databox and after Import to Azure, only Deltas should be fetched from on-premises running VMs.7 votes -
Allow multiple windows credentials for assessment
Assessment appliances only allow one set of credentials? This does not scale if my customer has different credentials required to do discovery. This means we have to deploy multiple VMs to assess, which increases costs and creates more friction towards migrating workloads. Do you want to accellerate migration or slow it down?
6 votes -
Rename a VM during migration
Provide for a means to rename a VM during the migration process.
IE if on-prem server is named Server1, during migration, the name could be changed and the VM would be in Azure named AZServer1.
Reasons: Some organizations have naming standards where servers in Azure must have AZ in front of them. Or they could be migrating from a data center they don't own and the data center forced their naming scheme on the organization. Or it could be that the org has changed their naming standards.5 votes -
programmatically/automate installation of extension post migration using Azure Migrate
So we have been using Azure Migrate to basically do a IAAS migration from our VMware infra to Azure. However all vms upon migration also need significant post migration work where we need to install the various IAAS extenstions for monitoring, Powershell DSC , Azure vm agent etc.
is there a way to configure Azure migrate so that it can install these agents automatically post migration. Or is there any other way to automate it.
5 votes -
Mark VM as SQL
It would be good to be able to mark a discovered VM as being OS Only, SQL Std or SQL Ent. Then the SQL license costs could be included in the costs on the assessments generated
5 votes -
Move resources groups to another subscription
Doing some migrations and movement between subscriptions, I see a lot of improvements there. As currently there is no dry run, once you start the migration there is no stopping anymore, There is also no progress on how long this migration will take, but after 4 hours there is an error message that it failed and a full rollback will take place. also handeling resource groups that have more than 100 items can be moved in one time If there are tight resources that are all connected to each other then migration is a pain. the limit is 800 items…
4 votes -
Do not allow target VM size to be one not allowed by Azure policy.
When suggesting or selecting a target VM size. Allow Azure Migrate to check against the Azure Policies set and either do not show the size not allowed or alternatively, allow the selection but post a warning. Thus allowing changes to the policy to be made.
Currently the migration will fail with a policy error.
3 votes -
Add support for hyper-v agentless migration of Linux generation 2 servers
Add support for hyper-v agentless migration of Linux generation 2 servers.
Even though hyper-v server migrations to Azure is agentless based, at the moment only windows generation 2 servers are supported. For Hyper-V migrations to Azure with over 600 linux machines, we do not want to do to this agentbased.
3 votes -
Azure Migrate - Support for region and zone migration
The region of the first migration in Azure Migrate is pinned and is the only allowed region for that Azure Migrate project going forward. Subsequent regions for migration require a new project\appliance. Can support be added to use the location that is pinned in the Assessment.
Secondly, can support be added for migrating on premis VM's into a "Zone" in a region. To get VM's pinned to a Zone users need to migrate to a different region and then use ASR to migrate and pin the VM to a zone.
3 votes
- Don't see your idea?