Hi All
Every time I start a VM from the Stopped (Deallocated) state it seems to configure a new Microsoft Hyper-V Network Adapter. I recently had a problem where I couldn't access a file share on another server in the same domain / virtual network and it turned out to be due to having 148 orphaned Microsoft Hyper-V Network Adapters (see my blog post here). Uninstalling these fixed the problem - just by luck that I came across this as a possible fix.
Is this behaviour by design and are Azure engineers aware of the possible problems it may cause?
Cheers - Graham