I have already trial WinActor and WinDirector in Microsoft Azure. It should not have any problem.
Regarding limitations of OfficeRobot running on the cloud :
Activation of OfficeRobot is done by Node-locking method.
In the case of virtual environments, depending on the virtualization method, one that dynamically allocates memory, hard disk, and CPU specifications, and it get refreshed on every login.
In such a case, the license fails to validate the Hardware information assuming that the PC is changed at the time of license authentication process and hence license shows invalid which leads to fail in OfficeRobot startup.
It is a setting that the environment is refreshed every time when logout is done, the desktop is variablely assigned at the time of login, If you use OfficeRobot in an environment where it has auto scaling, we always request to use physical machine to use OfficeRobot on it.
Otherwise, please consider configuring such virtual machine occupied by VDI (virtual terminal that system information does not fluctuate dynamically).