remove non essential network components from SP deployment template

[grahamcrowell]

makes it simpler to restore VMs from an backed up image see back up docs

[grahamcrowell]

What would Jeff do?

Template from quickstart repo includes Load Balancer and Availability Sets

Would including these make our Azure environment not comparable to our on-prem enviroment?

I know that these complicate the restore/backup from image process but removing them from the template is also complicated. I need help finding path of least resistence.

We're using this template as starting point and adjusting it to fit our needs see our version of template.

[grahamcrowell]

In order to configure software/server roles like AD and Sp, Quick start templates use nested templates and desired state configurations via templateuri which set a web address that child template can be downloaded from.

These Uris point to Microsoft maintained github repo.

this creates the risk that the code in the quick start repo will change and break our deployment

Although I can copy repo contents from ms repo to vch repo and change templateuri to point to vch's repo and our copy of nested templates and dsc's the deployments that point to our repo fail

[grahamcrowell]

• control our own copy of code
  • break dependacy on ms maintained repo
• remove non essential network components (load balancer and availability set)
  • Removing makes it simpler to restore VMs from an backed up image see back up docs

[grahamcrowell]

no longer using quick start template found tutorial with code that explains use of automation account and DSC