A workload onboarding plan identifies data-collected unmanaged machines from a named cloud account that you want to onboard into a Cloud Assembly project.

Workload onboarding plans allow you to bring unmanaged vSphere, Amazon AWS, and Microsoft Azure machines into Cloud Assembly management. You create a plan, populate it with machines, and then run the plan to import machines and create Cloud Assembly deployments.

Machines that are available for resource onboarding are listed on the Resources > Machines page relative to a specific cloud account type and region and labeled as Discovered in the Origin column. Only machines that have been data-collected are listed.

When you run the workload onboarding plan you can select the machines to add to the deployment. You can select specific machines to include in the deployment or onboard machines individually. You can also choose to create a blueprint for the deployment.

Table 1. How Machines are Impacted By Onboarding

Before workload onboarding

After workload onboarding

Unmanaged single machine (vSphere)

Cloud Assembly managed single machine (vSphere)

Unmanaged multi-tier application (vSphere) - for example multiple vSphere machines with networking and security, load balancer, and software applications

Cloud Assembly managed multi-tier application (vSphere)

Applications deployed and managed in Amazon AWS

Cloud Assembly managing the applications deployed and managed in Amazon AWS

Applications deployed and managed in Microsoft Azure

Cloud Assembly managing the applications deployed and managed in Microsoft Azure

To experiment with the options that are availablr when running a workload onboarding plan, see Use Case: Onboard an Amazon Web Services Unmanaged Machine.