Forum Discussion
PhilPreece1010
Oct 04, 2021Copper Contributor
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...
- Oct 05, 2021Hi 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?
PhilPreece1010
Oct 05, 2021Copper Contributor
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?
Johan_Vanneuville
Oct 05, 2021Iron Contributor
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.
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.