Microsoft Hyperv fail-over-cluster ws2025 in workgroup environment

[pmfna]

Hello

A customer asked me to build a POC with a hyperv cluster 2025 in workgroup environment because now Microsoft supports live migration using Certificate-Based Authentication.

I was able to add the nodes individually to Veeam v13, but when I try to add by the cluster name is shows an error.

Anyone try this successfully?

[pmfna]

well,

I was able to test this further, and noe I'm able to add the hyper-v nodes individually to veeam inventory.
I've realized that veeam disabled NTLM access in V13.

I've created a VMgroup at cluster level, and if I add the group to the JOB (cluster is two nodes, so I've added two VMgroup with the same name) and the job runs.

One thing I've noticed, is, if I migrate the vm from one host to another, veeam is creating a new full job for that vm in a new disk in repository, is this the expected behaviour ?

Is this configuration supported by veeam, couldnt see anything otherway in docs