Add "dataDisks": [ ],
in virtualMachineProfile

"[concat('Microsoft.Network/networkInterfaces/', variables('nicName'), '1')]"], both VM NIC reference is invalid json => so https://github.com/chagarw/MDPP/blob/master/101-availabilityset-simple-windows-md-implicit/azuredeploy.json template wont really deploy.

I'm not sure if this is a bug or what, but I would like to create a 32TB disk. Is this possible without striping on the client side?

has vmStorageAccountContainerName this is misleading and should be dropped.
"OSDiskName": "osdiskforwindowssimple", is not used and should be dropped.
"storageAccountType": "Standard_LRS", not used should be dropped.

couple of places mentions Windows Version params and should be dropped

Need to add toLower() to the dnsLabelPrefix because you are using the resourcegroup value which does not have to be lowercase.

Does anyone knows how to change the default size for a Linux VMSS when creating it and if the VMSS already exists managed how to modify the size of the OS ?

thx

In trying to provision a VM, I get the error:

{
"error": {
"code": "InvalidParameter",
"target": "managedDisk",
"message": "This subscription is not registered to use managedDisk feature."
}
}

How do I request support for managed disks?

Thanks

Using the template in 101-create-image-from-blob-and-vm-from-image as a guide I setup the following:

    {
        "type": "Microsoft.Compute/images",
        "apiVersion": "2016-04-30-preview",
        "name": "ComplianceServer-VM-Image",
        "location": "[variables('location')]",
        "properties": 
        {
            "storageProfile": 
            {
              "osDisk": {
                "osType": "linux",
                "osState": "Generalized",
                "blobUri": "https://x6lx28yt88h0mgqn.blob.core.windows.net/system/Microsoft.Compute/Images/images/compliance-osDisk.0cd1c41f-aea1-43aa-9836-d74130bb8e68.vhd",
                "caching": "ReadWrite",
                "storageAccountType": "Standard_LRS"
              }
            }
        }
    }

However when this is deployed to Azure I immediately get the following error:

{
  "error": {
    "code": "InvalidParameter",
    "target": "disk.blobUri",
    "message": "The blob name in URL https://x6lx28yt88h0mgqn.blob.core.windows.net/system/Microsoft.Compute/Images/images/compliance-osDisk.0cd1c41f-aea1-43aa-9836-d74130bb8e68.vhd contains a slash. This is presently not supported for disks."
  }
}

The URI is the URL to a custom image that has been generalised and was built by Packer.

I do not understand the error that is being given. The SA that is referenced is in the same resource group and location as the Image I am trying to create.

What am I missing? Thanks.