In the last 5 years we've experimented with Linux on top of hyper-v a few times. The basic I/O, compile & runtime performance was significantly inferior to xen & kvm (didn't bench against vmware, phasing it out due to cost), it wasn't worth any effort to even deploy apps for testing. Therefore I don't see Linux on hyper-v being a compelling option for the cost conscientious technical officer or lead engineer.
Network on Azure though is a totally wrecked thing:
- A0 instance is capped to a miserable 5 megabit/s uplink (downlink is fine);
- If you want TCP/UDP ports open, you need to open them one-by-one, going through a 2-page wizard with 8 fields in total to fill in for each port you are opening, and then waiting 15-20 seconds for each "change" to be applied. Good luck opening a 1024-port range for your SIP server;
- You can't open ICMP/GRE/IPSEC or any other custom protocol;
- There are ton of really weirdly configured network gear between your VM and the Internet - packet drops and private IPs in traceroute, etc...
- On a plus side, you can enable so called "direct server return" and you will get incoming packets with your public IP as a destination IP; a really nice feature sorely missing on AWS.