A workload onboarding plan identifies machines that have been data-collected from a cloud account endpoint but that are not yet managed by a Cloud Assembly project.

If you add a cloud account/region to Cloud Assembly that contains machines that were deployed outside of Cloud Assembly, you can bring those machines into Cloud Assembly management by first data-collecting them and then adding them to a workload onboarding plan. When you add the machines to an workload onboarding plan, you can group all or some of them into a single deployment, or onboard each machine as a separate deployment.

A workload onboarding plan allows you to bring unmanaged machines into Cloud Assembly management. You create a plan, populate it with machines, and then run the plan to import the machines and create Cloud Assembly deployments. You can also generate a blueprint as part of this process.

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.

The person who runs the workload onboarding plan is automatically assigned as the machine owner.

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

See Use Case: Onboard an Amazon Web Services Unmanaged Machine.