InDesign Server ToS Allotment When Migrating Between VMs

Hello,

Background

My company has two premium and two developer licenses for the InDesign Server.  Each license is installed on a separate VM image and each image is running on a single Azure VMSS VM.  This is permitted by the ToS.  Moving all requests between the licenses would be problematic.

Summary of Concern/Question

I want to understand if and how long we would be allowed to run the same license twice before running afoul of the Genuine service?  This is for resource migration and to keep the image's OS patched only (no horizontal scaling to handle load spikes).

Concern/Questions

We need to do two things that do not appear to be explicitly allowed or denied and would like to confirm that the Genuine service (and the ToS) would allow it.

1. Each install needs to be migrated to a different scale set (another VM).  To prevent an outage, we would need to run the same image twice for around an hour to complete the migration.  New requests can be cut over quickly but the running job has no upper bound and validation/fallback testing is slower.

2. The images need to contain the latest Microsoft Security patches.  This requires installing the InDesign Server Service on a VM while the pre-existing VM handles requests.  Only basic endpoint testing would be performed before the VM is sysprepped and destroyed. We would then update the VMSS to use the image, scale-out to two VMs, move the tenants and scale back down to one VM. As above, we can reroute requests quickly, but cannot control the run duration of an active request.  Validation would also be much faster.

Are these use cases permitted? Do we need to ensure to not overstep a certain duration where the license is running twice?

Thank you.