Moving the local Hyper-V WLC image to an Azure tenant is not a supported deployment scenario. The image is optimized for on-premise hypervisors (local ESXi/Hyper-V) and has not been validated for the Azure network stack.
The reason for this question is we might be running some old WAPs for a couple more years yet and want to get away from hosting the controller within our own virtual stack.
