Forum Discussion
Azure VD - AD/AADDS Required?
I'm trying to set up an Azure Virtual Desktop test lab for evaluation purposes. I've created a new test Azure tenant with some M365 Business Premium licenses. I've added some dummy test users, assign...
- Hi Vince, no still having issues.
Earlier today i cleaned up the Azure tenant once again. I deleted all the resources that were deployed by the AADDS wizard and the Azure Virtual Desktop wizard. I then successfully re-deployed AADDS, applied the recommended DNS fix and ran the AVD wizard again. This time i selected 'domain to join = AADDS' but the wizard failed again. This time with a different error:
easy-button-inputvalidation-job-linked-template - conflict
I do have MFA enabled for all users? Perhaps that is the issue then?
PhilPreece1010Hey Phil. Did you resolve this in the end? I am also getting this same issue with the password.
I wonder if it's to do with MFA?
Thanks
Vince
Hi Vince, no still having issues.
Earlier today i cleaned up the Azure tenant once again. I deleted all the resources that were deployed by the AADDS wizard and the Azure Virtual Desktop wizard. I then successfully re-deployed AADDS, applied the recommended DNS fix and ran the AVD wizard again. This time i selected 'domain to join = AADDS' but the wizard failed again. This time with a different error:
easy-button-inputvalidation-job-linked-template - conflict
I do have MFA enabled for all users? Perhaps that is the issue then?
Earlier today i cleaned up the Azure tenant once again. I deleted all the resources that were deployed by the AADDS wizard and the Azure Virtual Desktop wizard. I then successfully re-deployed AADDS, applied the recommended DNS fix and ran the AVD wizard again. This time i selected 'domain to join = AADDS' but the wizard failed again. This time with a different error:
easy-button-inputvalidation-job-linked-template - conflict
I do have MFA enabled for all users? Perhaps that is the issue then?
- Phil, correct it's my understanding that MFA is not yet supported when using AAD joined VM's and trying to login to them via AVD. I could be wrong but maybe worth a shot. I will also test this myself tomorrow and let you know.
- Thanks all for the assistance. AVD has now deployed successfully.
Quick summary of the steps i took.
- Cleaned up Azure tenant (ie: deleted all the remnants of the failed AVD deployment, such as: adds, avd, all resources, etc).
- Used the AVD 'Getting Started' wizard (rather than 'deploy a host pool' option) and allowed this to build a new instance of Azure ADDS for me.
- Disabled MFA against the accounts i used in the AVD getting started wizard.
- Before logging into the AVD client i had to reset the test users password so the hash is sync'd back to ADDS.- Great News.
- If you use the quickstart wizard you need to use an account that doesn't have MFA enabled. If you check the runbook behind the getting started wizard it will give you that error message.
If you create AADDS with the wizard you also need to make sure that your custom domain is added otherwise the wizard will fail also. - I think your right Vince, i've just stumbled across this article:
https://techcommunity.microsoft.com/t5/azure-virtual-desktop/getting-started-wizard-in-azure-virtual-desktop/m-p/2451385
2. Requirements and limitations
Accounts used with getting started cannot have MFA.
