Migrate Windows 10 to Azure

Home Forums Client Operating Systems Windows 10 Migrate Windows 10 to Azure

Tagged: ,

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author

  • clickit

    hello there,

    I’m very newbie to Azure, I have a dev box running windows 10 professional non-hyper-v, 1tb, 16gb, i7-6th gen, with shadowprotect with full bare metal backup, Is there a way I can virtualize or transform this dev box to the azure cloud as virtual desktop without changing any configration, etc.

    thanks in advance


    The Following process needs to be followed in order to migrate to AZURE
    Prepare to use Azure with Azure Migrate:Server Migration.
    Check requirements for machines you want to migrate, and prepare a machine for the Azure Migrate replication appliance that’s used to discover and migrate machines to Azure.

    Add the Azure Migrate Server Migration tool in the Azure Migrate hub.
    Set up the replication appliance.
    Install the Mobility service on machines you want to migrate.
    Enable replication.
    Run a test migration to make sure everything’s working as expected.
    Run a full migration to Azure. Prepare Azure
    Prepare Azure for migration with Server Migration.

    Task Details
    Create an Azure Migrate project Your Azure account needs Contributor or Owner permissions to create a project.
    Verify permissions for your Azure account Your Azure account needs permissions to create a VM, and write to an Azure managed disk.
    Assign permissions to create a project
    In the Azure portal, open the subscription, and select Access control (IAM).
    In Check access, find the relevant account, and click it to view permissions.
    You should have Contributor or Owner permissions.
    If you just created a free Azure account, you’re the owner of your subscription.
    If you’re not the subscription owner, work with the owner to assign the role.
    Assign Azure account permissions
    Assign the Virtual Machine Contributor role to the Azure account. This provides permissions to:

    Create a VM in the selected resource group.
    Create a VM in the selected virtual network.
    Write to an Azure managed disk.
    Create an Azure network
    Set up an Azure virtual network (VNet). When you replicate to Azure, Azure VMs are created and joined to the Azure VNet that you specify when you set up migration.

    Prepare for migration
    To prepare for physical server migration, you need to verify the physical server settings, and prepare to deploy a replication appliance.

    Check machine requirements for migration
    Make sure machines comply with requirements for migration to Azure.


    When migrating physical machines, Azure Migrate:Server Migration uses the same replication architecture as agent-based disaster recovery in the Azure Site Recovery service, and some components share the same code base. Some content might link to Site Recovery documentation.

    Verify physical server requirements.
    Verify that on-premises machines that you replicate to Azure comply with Azure VM requirements.
    There are some changes needed on VMs before you migrate them to Azure.
    For some operating systems, Azure Migrate makes these changes automatically.
    It’s important to make these changes before you begin the migration. If you migrate the VM before you make the change, the VM might not boot up in Azure. Review Windows and Linux changes you need to make.
    Prepare a machine for the replication appliance
    Azure Migrate: Server Migration uses a replication appliance to replicate machines to Azure. The replication appliance runs the following components.

    Configuration server: The configuration server coordinates communications between on-premises and Azure, and manages data replication.
    Process server: The process server acts as a replication gateway. It receives replication data; optimizes it with caching, compression, and encryption, and sends it to a cache storage account in Azure.
    Prepare for appliance deployment as follows:

    You prepare a machine to host the replication appliance. Review the machine requirements.
    The replication appliance uses MySQL. Review the options for installing MySQL on the appliance.
    Review the Azure URLs required for the replication appliance to access public and government clouds.
    Review [port] (migrate-replication-appliance.md#port-access) access requirements for the replication appliance.

    The replication appliance shouldn’t be installed on a source machine that you want to replicate or on the Azure Migrate discovery and assessment appliance you may have installed before.

    Add the Server Migration tool
    Set up an Azure Migrate project, and then add the Server Migration tool to it.

    In the Azure portal > All services, search for Azure Migrate.

    Under Services, select Azure Migrate.

    In Overview, click Assess and migrate servers.

    Under Discover, assess and migrate servers, click Assess and migrate servers.
    In Discover, assess and migrate servers, click Add tools.

    In the Migrate project, select your Azure subscription, and create a resource group if you don’t have one.

    In Project Details, specify the project name, and geography in which you want to create the project, and click Next. Review supported geographies for public and government clouds.
    In the Select assessment tool, select Skip adding an assessment tool, for now,> Next.

    In Select migration tool, select Azure Migrate: Server Migration > Next.

    In Review + add tools, review the settings, and click Add tools

    After adding the tool, it appears in the Azure Migrate project > Servers > Migration tools.

    I know this process is a bit tough to understand but there are some youtube tutorial videos which you can checkout

Viewing 2 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.

Live Webinar - Thursday, December 2nd! Active Directory Masterclass: AD Configuration Strategies for Stronger SecurityREGISTER NOW - Thursday, December 2, 2021 @ 1 pm ET

Active Directory (AD) is leveraged by over 90% of enterprises worldwide as the authentication and authorization hub of their IT infrastructure—but its inherent complexity leaves it prone to misconfigurations that can allow attackers to slip into your network and wreak havoc. 

Join this session with Microsoft MVP and MCT Sander Berkouwer, who will explore:

  • Whether you should upgrade your domain controllers to Windows Server
    2019 and beyond
  • Achieving mission impossible: updating DCs within 48 hours
  • How to disable legacy protocols and outdated compatibility options in
    Active Directory

Sponsored by: