Azure Portal Templates need Versioning, Releases and Deprecation flags
Azure Portal Templates need versioning for testing. Having a "network" template with a label of "released" or "published" would allow editing of a template while still being able to use it in production.
You should also be able to deploy a template using "version 1.0" and flag an older version as "deprecated"
Thanks for idea, we will definitely take this feedback and work on improving it.