Closed stevenjudd closed 4 years ago
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @mjconnection, @Drewm3
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @mjconnection, @Drewm3
The cmdlet Set-AzVMBootDiagnostic is just changing the configuration of the client side object for the VM. To get that version of the VM to be applied to the VM in Azure you need to execute: Update-AzVM -VM $vmobject -ResourceGroupName $vmobject.ResourceGroupName
Let me know if this resolves the issue.
@stevenjudd, please let me know if the details above do not actually resolve this issue.
Thanks for working with Microsoft on GitHub! Tell us how you feel about your experience using the reactions on this comment.
Description
Running the Set-AzVMBootDiagnostic cmdlet with the -Disable parameter does not actually disable the boot diagnostics. The object that comes back shows the DiagnosticsProfile.BootDiagnostics.Enabled value as False yet checking the VM object shows it to be True
Steps to reproduce
Environment data
Module versions
Debug output
Error output