Again, it is a general tendency to declare many parameters for a resource configuration, and these parameters are put randomly within the parameters section. Ideally, the parameters for a resource configuration should be grouped together as a single parameter and sent to the ARM template.
In this example, an ARM template accepts a single SQL Server resource configuration parameter of the object data type:
"sqlServerProperties": {
"type": "object"
},
And the parameters file provides all the parameters to it as a single object, as shown next:
"sqlServerProperties": {
"value": {
"administratorLogin": "eCommerceAdmin",
"databaseName": "eCommerceDatabase",
"collation": "SQL_Latin1_General_CP1_CI_AS",
...