Description
A VM can be created with boot diagnostics enabled. Diagnostics data is written to a storage account.
There is a feature to not specify a custom storage account, and instead use a storage account managed by Azure. This is probably the better option than using your own storage accounts because of the limitations (your storage account needs an open firewall, and many options for it are not supported).
The current module does not allow this configuration, instead you must always specify a custom storage account.
It would make much sense to add this feature, as it is probably the best way to activate boot diagnostics.
Inside an ARM template, you would specify the feature like this:
"diagnosticsProfile": {
"bootDiagnostics": {
"enabled": true
}
}So you actually just need to enable the feature, and not specify an existing storage account.
Description
A VM can be created with boot diagnostics enabled. Diagnostics data is written to a storage account.
There is a feature to not specify a custom storage account, and instead use a storage account managed by Azure. This is probably the better option than using your own storage accounts because of the limitations (your storage account needs an open firewall, and many options for it are not supported).
The current module does not allow this configuration, instead you must always specify a custom storage account.
It would make much sense to add this feature, as it is probably the best way to activate boot diagnostics.
Inside an ARM template, you would specify the feature like this:
So you actually just need to enable the feature, and not specify an existing storage account.