Setting up diagnostic with a new VM
When creating a new Virtual Machine portal, after you selected the Azure Resource Manager from the deployment model dropdown, and configured the basic settings and the size of a VM. You need to insure that the monitoring option is enabled and that you have selected a storage account where you would like to place these diagnostic files.
If you are using a Azure Resource Manager template, find your Virtual Machine resource and add a diagnostics profile section where you will identify the status or the diagnostic (enabled=True/False) and where to store the log files (“storageUri”: “[concat(‘http://’,parameters(newsStorageAccountName’), ‘.blob.core.windows.net’)]”). Remember to use the “2015-06-15” API version header
you can than deploy the VM normally. and the diagnostic will be turned on.
Update an Existing Virtual Machine
You can also update an existing ARM based Virtual Machine through the Portal to enable diagnostics. Navigate to your VM and select “Diagnostics” (1) in the settings blade. Enable the Status (2) and select the level of diagnostics you want to collect (3) and save your settings.
Remember that you must restart the VM for the changes to take effect.
to view the logs, in the portal select “Browse” and select “Audit Logs” to see all the event logs you have configured.
And for the “Boot Diagnostics”, In the portal navigate to your virtual machine and in the “settings” blade and select “Boot Diagnostics”. This will give you access to the screenshot for the boot process,