You use a workload onboarding plan to identify machines that have been data-collected from a cloud account type in a target region or data center but that are not yet managed by a Cloud Assembly project.
When you add a cloud account that contains machines that were deployed outside of Cloud Assembly, the machines are not managed by Cloud Assembly until you onboard them. Use an onboarding plan 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. Using the onboarding plan, you can create a blueprint and can also create one or many deployments.
You can onboard one or many unmanaged machines in a single plan. You can select machines manually or by using a filtering rule. Filtering rules select machines for onboarding based on criteria such as machine name, status, IP address, and tags.
Machines that are available for workload onboarding are listed on the Discovered in the Origin column. Only machines that have been data-collected are listed. After you onboard the machines, they appear in the Origin column as Deployed.page relative to a specific cloud account type and region and labeled as
The person who runs the workload onboarding plan is automatically assigned as the machine owner.
For examples of onboarding techniques, see Example: Onboard selected machines as a single deployment in Cloud Assembly and Example: Onboard rule-filtered machines as separate deployments in Cloud Assembly.
Onboarding event subscriptions
A Deployment Onboarded event is created when you run the plan. Using Extensibility tab options, you can subscribe to these deployment events and perform actions on them.