We would like to be able to use the great work you did in ovn-kubernetes on our machines in Azure, but this is not straight forward. It would look like this:
- scale up a machine set, wait for the node to be up
- cordon the node and shut it down
- add nic connected to a different subnet through the azure portal, boot the machine
- add a default route with a higher weight
ip route add default via 10.56.140.1 metric 999
- EgressIP can then be assigned on the node as usual, using the  k8s.ovn.org/egress-assignable label node and the EgressIP resources.

ideally we should be able to define the machinespec with extra subnets, in similar fashion
```
          networkResourceGroup: net-01
          subnet: paas1
          secondaryInterfaces:
          - subnet: dmz
          - subnet: public
```
the machinespec would be in charge of creating the nic in the right subnet as you said.