@Waqar the problem is not fixed.

Did a clean install on local Hyper-V, and it tries to start the agent, and it even hangs for 4 minutes on startup - please see the attached image.
My guess would be, that the detection if it is "Microsoft Corporation" also triggers locally, since Hyper-V locally is also on Microsoft.

So my suggestion would still be to follow what upsteam says, and remove it, and then let people install it if they want to run TrueNAS in Azure.

As it is now, the local install is broken, so I would suggest going that route, since it does not seem like there is any way to differentiate between Hyper-V in Azure and Hyper-V elsewhere.

@Bjarke istrup Pedersen  - I suspect you can use the nightly build to try and validate ( https://download.truenas.com/truenas-scale-nightly/ ). I'll be giving that a shot here in the next couple of days unless I see someone confirms it first.

@Waqar since it has been marked as fixed, is there a way for me to test?

22.02 PR: https://github.com/truenas/scale-build/pull/209

No, I only have it running locally.

If you haven't used Azure before, you can setup a free account, with some free credit that you can use to test it in there. (Getting a VM in there with a custom image is a bit more tricky).

Do you need me to test something locally?