I was able to migrate the mashine to Azure.
First I had to V2V convert the mashine using VMware vCenter Converter.

After that I used StarWind V2V to migrate the local VM to Azure.

So I had not to bother with Access Token Lifetime.

This seems like the same problem:
https://forums.starwindsoftware.com/vie ... =15&t=5588

What makes you think it has something to do with the Token Lifetime?

The system hast two sperate hdd. The first one has a "System Reserverd" Partition and a normal "C:" partition. Both where selected during the convert. The second hdd is only a temp drive. With no real data in it. So i unchecked it during convert. Do I have to convert the second h...

Ok. I will try to extend the token after I could solve the "neither imageReference nor osDisk" problem in another thread.

Yes the disk is carrying the os.
I have attached the logs.

I am trying to convert a VM to Azure. To test if it works at all I left out the second hdd, since I always get Toxen Lifetime problems, but now I get another error message: 7/29 9:12:54.230 b40 Facility ???ERROR: VMConverter::AzureConverter::CreateVM: CreateVirtualMachine Status code: 409 Error code...

Same problem for me. Since Microsoft disabled the function for longer Token Lifetimes will there be another solution? Microsoft: "After hearing from customers during the preview, we've implemented authentication session management capabilities in Azure AD Conditional Access. You can use this ne...