Inconsistent API versions for same type of resource #9
Description
In Azure-ARM/azuredeploy.json, the same type of resources are using different API versions:
- Microsoft.Resources/deployments is using apiVersion 2015-01-01, except on line 776 where it's using 2018-02-01
- likewise, the schema called in these nested deployments is using schema 2015-01-01, but the schema called by the template itself is 2019-04-01
- Microsoft.Sql/servers is using apiVersion 2019-06-01-preview, but the child resources are using different apiVersions
- Microsoft.Sql/servers/firewallrules is using 2015-05-01-preview
- Microsoft.Sql/servers/databases is using 2020-08-01-preview
The consistency of the apiVersions in the template might be easier to maintain using apiProfile instead of explicitly having apiVersion in each resource