I appreciate your assistance. Unfortunately due to project time constraints I ended up using Azure Migrate to get the server migrated to Azure.

I'll post a screenshot when i get a chance. But when i did it, the OS drive defaulted to HDD0. I had an option to select HDD0 or HDD1. I left it the default of HDD0.

Tried excluding the D drive and received error creating the creating machine. 7/5 0:07:25.865 285c Facility ???INFO: CPPConverting::ConvertImage: Success 7/5 0:07:51.207 285c Facility ???INFO: VMConverter::AzureConverter::CreateVM: InProgress 7/5 0:07:51.301 285c Facility ???INFO: VMConverter::Azure...

So far been unable to get the migration to work using the Conditional Access policy.

Looks like configuring token lifetimes got retired. Message: Configure Token Lifetime for RT/ST (Refresh/Session Token) has been retired on May 30, 2020. New policy cannot be created anymore. Refer https://docs.microsoft.com/en-us/azure/active-directory/develop/active-directory-configurable-token-li...

Thanks! I'll look at that article.

Can the conversion work with StorageV1 or does it require the StorageV2 it keeps creating during the migration wizard?

If it does require StorageV2, can it use preconfigured StorageV2 name, or does it always randomly generate a new storage account name?

Sure! Thanks :D The log file name: 'logs\V2V_Log-20200629-164648.log' (PID 2260) 6/29 16:46:48.046 1684 Facility ???INFO: CV2V_ConverterApp::InitInstance: SetDllDirectory: C:\Program Files\StarWind Software\StarWind V2V Converter\lib 6/29 16:46:48.046 1684 Facility ???INFO: CV2V_ConverterApp::InitIn...

Used this article https://www.starwindsoftware.com/v2v-help/UsingStarWindV2VConverterwithMicrosoftAzure.html. The guide does not specify what type of Azure storage account to make. So created a StorageV1 account. After running Starwind V2V converter automatically created a new StorageV2 account. I h...