yes, the jumpbox is a short lived resource that orchestrates the build out of the environment initially. It is deployed, and then it manages downloading the required binaries, creating subnets / resourcegroups / vm's etc, makes sure things are configured properly, and then orchestrates the pairing of the environment back to the Horizon Cloud Service control plane.
Once done, and the node is connected, the jumpbox self-destructs and deletes itself.
A (new) jumpbox is again needed in the future when an upgrade of the environment is triggered, or for specific maintenance/debugging operations. But in all cases this is short lived.
fwiw; the jumpbox uses a Standard F2 (2 vcpus, 4 GB memory) VM
hope this helps. Ping back if you have further questions,
just checking back in... did this help answer the question?