Can not run template with Gen2 Virtual Machines

--------------------MESSAGE FROM ADMIN, DELETE BEFORE SUBMITTING----------------------

Sorry to hear you had a bad experience with one of the templates :worried: But, in case you're just asking a question, we're happy to help. You can also check if the question might already have been asked here https://github.com/Azure/azure-quickstart-templates/issues?utf8=%E2%9C%93&q=is%3Aissue

We've created an outline of recommended sections to fill out that will help make this Pull Request awesome!

--------------------MESSAGE FROM ADMIN, DELETE BEFORE SUBMITTING----------------------

[Template Name goes here](Template link goes here)

### Issue Details
I'm an internal Microsoft employee and need the ability to run this template with 2019-datacenter-gensecond and 2016-datacenter-gensecond ImageSKUs (DSc2-Series and Dsc3-series). The tenant I use ONLY support generation 2 virtual machines. Can the template be updated to support new Generation 2 virtual machines?

When I customize the template to run these sku I fails with the following error:

{"code":"MultipleErrorsOccurred","details":[{"code":"InvalidContentLink","message":"Unable to download deployment content from '[https://raw.githubusercontent.com/Azure/azure-quickstart-templates/master/application-workloads/active-directory/nested/vnet.json'.](https://raw.githubusercontent.com/Azure/azure-quickstart-templates/master/application-workloads/active-directory/nested/vnet.json%27.) The tracking Id is 'bc8c3fb9-b781-4767-a435-f966777d7039'. Please see https://aka.ms/arm-deploy for usage details."},{"code":"InvalidContentLink","message":"Unable to download deployment content from '[https://raw.githubusercontent.com/Azure/azure-quickstart-templates/master/application-workloads/active-directory/nested/CreateAndPrepnewVM.json'.](https://raw.githubusercontent.com/Azure/azure-quickstart-templates/master/application-workloads/active-directory/nested/CreateAndPrepnewVM.json%27.) The tracking Id is 'bc8c3fb9-b781-4767-a435-f966777d7039'. Please see https://aka.ms/arm-deploy for usage details."},

I'm pretty sure this is because the templates do not support modification in this way.

### Repro steps (*if necessary, delete otherwise*)
1.
2.
3.
4.
5.

Start by inspecting application-workloads/active-directory/nested/vnet.json and CreateAndPrepnewVM.json, then try the deployment with the 2019-datacenter-gensecond or 2016-datacenter-gensecond ImageSKU. Done means the template can be customized and deployed for the Gen2 virtual machines described without the reported content-link errors.

Written by the indexing model from the issue text.