An Azure service that is used to provision Windows and Linux virtual machines.
FWIW I had the same error message trying to get nested virtualisation working on Azure with a Windows 2025 Server of various supposedly supported VM sizes, in the end the issue turned out to be the hypervisor not being set to auto-start in the boot config. I'm not sure if that's something that happens automatically since Windows 2025 Server or when you're nesting HyperV in Azure because very few setup guides refer to it, but this troubleshooting article does - https://learn.microsoft.com/en-us/troubleshoot/azure/virtual-machines/windows/troubleshoot-vm-by-use-nested-virtualization
The TLDR is to run the following command and see if hypervisorlaunchtype appears on the output -
bcdedit /enum
If hypervisorlaunchtype is not listed then you can add it with the following command followed by a reboot -
bcdedit /set hypervisorlaunchtype auto