Customer feedback on rds-deployment-existing-ad template

[mmarch]

From: Dharmesh Chauhan
Sent: Tuesday, March 7, 2017 6:38 AM
Subject: RE: [REG:117013115250952] Re ticket 117012615231936 FAO Azure AD Domain Ser

Hi All,
Thanks for your help, after much trial and error I have managed to deploy a set of servers using the template, when I was expecting it to work “straight out of the box” with it being a quickstart template. Below is some feedback which I hope helps you with making the templating more user friendly, and more applicable to customer environment set ups.

• When completing the template BASICS section, there is an option to select New or existing resource group, however this contradicts with the fact that I was only able to complete the deployment without failure if I chose the RG the VNet was a part of.
  Hand in hand with that, I had to modify the template variables to use specific values for dns labels, storage account and container, dns server etc as some of these values had concatenated resource group values, and with the VNet RG had a hyphen and mixed upper and lower case, this was causing issues with limitations in naming conventions of some resources therefore failing deploying, e.g. storage accounts can only be in lower case.

• Also some of the parameter name and descriptions on https://azure.microsoft.com/en-gb/resources/templates/rds-deployment-existing-ad/ are not clear enough:
  adVnetName – I was able to use the ARM Vnet and did not have to use the classic Vnet where AAD is hosted.
  adSubnetName - The subnet name of AD domain. I found this to be incorrect as was able to set the VMs to in in a subnet where the AD is not located, i.e. subnet BTApp
  adminUsername – From trial and error I realised this has to be a domain account with admin permissions, as from reading the description I interpreted this as declaring a username for a local admin account to be created.

• Also there are the limitations that all VMs have to be in one subnet, and all resources in one resource group however I understand there is probably a way to split this out.

Kind Regards,

Daz Chauhan | Senior Technical Analyst

[jasonagilbertson]

This issue was moved to Azure/RDS-Templates#44