Carbon documentation

Moving a workload into Azure is straightforward. Moving it back out is not - which is why organisations that decide to repatriate a VM, whether for cost, control or because the workload never suited the cloud, often find themselves rebuilding it by hand.

Carbon does that migration for you. It connects to your Azure subscription, lists your VMs with the detail you need to choose (name, status, CPU, memory, IP address, operating system), then replicates and converts the machine you pick into your on-premises environment - sizing CPU, memory and disk to match the Azure specification rather than leaving you to work it out.

Direction of travel: Azure to on-premises. Carbon is a repatriation tool; it does not migrate the other way.

Target hypervisors: VMware and Hyper-V.

Migrations run with email notification of progress, so a multi-hour transfer does not need watching.

Start here: Getting started for the overview, Install to deploy it, and VMware permissions for the access Carbon needs on the target side. Migrate a VM is the canonical walkthrough, and Post-migration covers what to check once a machine has landed.