Before you begin
Confirm account, tenant and active role in the account menu. Inspection requires view permission; changing records requires the specific management permission. A hidden or disabled action can reflect authorized scope; do not switch tenants to evade a denial. Work only with records in the workspace you are allowed to administer.
Procedure
- In Cloud workers → Workers inspect the source, use Pause or Drain worker and wait for active work to finish.
- Open Reassign references, review the authorized compatible destination and confirm impact.
- Inspect Dependency backups to restore or reassign metadata.
- To preserve continuity before retiring infrastructure, verify destination capacity and migrated references. To remove a VM without first migrating, follow Remove VM and unlink and review its impact.
Behavior and limits
Reassignment changes references; it does not move databases, files, operating system or credentials. A dependency backup preserves metadata and integrity; it is not a VM image or complete backup. Public retirement checks cross-tenant references and historical versions still in use.
Removal requires verified identity and ownership, permissions and a confirmed cloud result. An unknown-state read does not prove absence. Remove VM and unlink can clear references after confirmed deletion; Pause/Stop retain active-work and default-capacity protections.
Before applying, confirm that the destination satisfies the referenced objects’ capabilities. Unreachable historical versions are preserved and do not block retirement by themselves. Files and connections must be available through their separate authorized procedure.
Verify the result
After saving or confirming, reopen the detail and check the state reported by the server. Distinguish an accepted request from a completed operation and retain only minimal evidence without sensitive information. When an operation is pending, wait for its final state in the corresponding view before starting another action on the same object.
Laboratory example
Use the synthetic tenant documentation-lab and, where relevant, worker worker-demo-a. Note the previous state, perform one authorized action and compare the resulting state. These names illustrate the procedure; they do not identify production records or authorize creating cloud resources. For a review without changes, inspect the detail and cancel any open form.
If something fails
If a conflict appears, refresh the inventory and review current values before repeating. If the session expired, sign in and complete MFA when required. For a permission error, check the role and membership; for a provider error, inspect the operation and its safe message. Do not alter storage, revisions or controls to force an outcome.
Related reading
Remove a VM and recover assignments
Open Remove VM and unlink, review resource identity and impact on Sessions, executions and pools, then confirm the intended deletion. For a supported owned VM, manually dismantling every reference or first powering it off is not a prerequisite for this operation. Removing capacity can interrupt active executions; schedule the operation to suit your needs.
After confirming provider absence, Dova retires the active worker, clears Runtime references and shows Unassigned for Session bindings that used it. Definitions, published versions, configuration and audit history are preserved. If the VM is deleted directly in the provider, reconciliation applies the same treatment after verifying absence. A provider-read error is not evidence that the VM was deleted.
Before running again, select compatible authorized capacity and review the environment pool. Unassigned does not silently choose another worker. You can provision a new VM and assign it explicitly. Permissions, resource ownership, the protected base server and pending operations remain checked; removal does not bypass these protections.