Azure / Azure/azure-powershell

Boot Diagnostics Not Switching to Managed Storage Account

Open
#28,041 3 comments 0 reactions 0 assignees View on GitHub
act-observability-squad Compute - VM customer-reported Possible-Solution question Service Attention Similar-Issue
Dominant language
C#
Stars
4.8k
Forks
4.3k
Avg merge
2d 17h
Merged PRs (30d)
51

Description

### Description

We initially enabled Boot Diagnostics using a custom storage account and were able to access the Windows desktop successfully.

Now, we are attempting to switch Boot Diagnostics to use a managed storage account instead. As part of the process, we followed these steps:

Disabled Boot Diagnostics:
$VM = Get-AzVM -ResourceGroupName $grp_name -Name $vm_name
Set-AzVMBootDiagnostic -VM $VM -Disable
Update-AzVM -VM $VM -ResourceGroupName $grp_name

Re-enabled Boot Diagnostics (expecting it to use a managed storage account):
$VM = Get-AzVM -ResourceGroupName $grp_name -Name $vm_name
Set-AzVMBootDiagnostic -VM $VM -Enable -ResourceGroupName $grp_name
Update-AzVM -VM $VM -ResourceGroupName $grp_name

However, after re-enabling, the VM continues to retain the previous custom storage account setting instead of switching to the default managed storage account as expected.

We would appreciate assistance in resolving this issue and ensuring Boot Diagnostics uses a managed storage account.

### Script or Debug output

```PowerShell

```

### Environment data

```PowerShell

```

### Module versions

```PowerShell

```

### Error output

```PowerShell

```

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.