101-aks-advanced-networking- how to add parameters --enable-autoscaler & VMSS in the templae

Using 101-AKS-Advanced-Networking template and trying to induce template with "Availabilityset: "VirtualmacheScaleSets" in the agent pool.
------------------------------------
"agentPoolProfiles": [
{
"name": "wmsdevk8s",
"osDiskSizeGB": "[parameters('osDiskSizeGB')]",
"diskSizesGB": [64],
"count": "[parameters('agentCount')]",
"vmSize": "[parameters('agentVMSize')]",
"availabilityProfile": "VirtualMachineScaleSets",
"osType": "[parameters('osType')]",
"storageProfile": "ManagedDisks",
"maxPods": "[parameters('maxPods')]",
"vnetSubnetID": "[parameters('vnetSubnetID')]"
}
],
loadBalancer": "standard" ,
---------------------------------------------

Eventhough, defined
1) LoadBalancer type standard, 2) Availability Profile# VMSS & 3) DiskSizeGB , these parameters are ignored and not utilized by the aks-engine.

Please let me know, how to define these parameters in the AKS-Advanced-Networking template.

Also looking to enable Cluster-Autoscaler components in the template as well.

I coludn't see AKS- Engine Cluster definition file like ACS (https://github.com/Azure/acs-engine/blob/master/docs/clusterdefinition.md)

Please suggest.

Start with the 101-AKS-Advanced-Networking template and inspect how its agentPoolProfiles and loadBalancer settings are passed to AKS Engine. Compare the requested VMSS, disk-size, standard load balancer, and cluster-autoscaler options with the linked ACS cluster-definition reference; done means the template exposes supported parameters and the generated deployment uses them.

Written by the indexing model from the issue text.