An error occurred while saving the commentShannon commented
This is necessary in large part because Nested Templates don't support some important features of External/Linked Templates; e.g. their own parameters, references, resource group targeting, etc. For example, if we desire services deployed in two resource groups to be connected to the same Virtual Network, one or both subnets must be deployed by Linked Template. If nested templates were full-featured, I would be able to convert modular templates into monolithic ones. Also, the AZ CLI would be able to automatically do that for me, effectively providing the capability requested here.