This will help you diagnose fatal errors. Unfortunately not all exceptions are fatal, and if you have any timers, unawaited async or unhandled task pool exceptions these can cause your application to behave unexpectedly without you knowing about it.
You can use the UnobservedTaskException to catch some of those ones:
To attach a data disk to the virtual machine you can use the following configuration just below the osDisk definition.
lun (Logical Unit Number) should be unique for each attached disk and starts from zero.
diskSizeGB has a maximum of 1000 (1 TB) in Azure currently.
createOption should be “Empty” for a new disk.
vhd.Uri is the full path you want the blob created in.
If we deployed the template with this now, we will get a raw unformatted disk with no drive label. You can view it in Disk Manager or by running the following PowerShell on the box.
Get-Disk | Where partitionstyle -eq'raw'
We need one more resource to complete the deployment and give us a formatted disk. We can use the CustomScriptExtension to run a PowerShell script which will format any raw attached disks (in case you want to do multiple drives).
dependsOn will need to be the resource path for our virtual machine to ensure this extension is run after its provisioned.
fileUris is an array of any files we want downloaded and made available to execute. This needs to be a path to an azure blob, unfortunately you cannot link to any other domains like github.
commandToExecute is a cmd.exe command, so we need to call out to powershell to invoke our script. The working directory will have your downloaded file already there, so you don’t need the full path to execute it, just the name.
You will need to upload the following script to a blob: