This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(134.4, 44%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDS%3C/text%3E%3C/svg%3E)
When I try to start my VM instance I get this error:
Key Vault <secret PII info removed> either has not been enabled for deployment or the vault id provided, <AKV resource id removed>, does not match the Key Vault's true resource id.
Resource id: <SQL VM Id removed PII info>
The AKV is configured for VM deployment:
The AKV resource id: <PII data removed>
How do I fix it?
Azure compute resources that are used to create and manage groups of heterogeneous load-balanced virtual machines.
Also, the UAMI of the VMSS has full secret and cert access defined through an access policy of the AKV
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(262.40000000000003, 96%, 35%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAY%3C/text%3E%3C/svg%3E)
Hello @David Shiflet ,
Thank you for posting your question on the Microsoft Q&A forum.
I understand it can be frustrating when a VMSS doesn't start even after following the correct steps. I'm here to help you resolve this issue.
This error usually occurs when one of the following checks fails:
I've contacted you via private message to discuss your availability. Let's schedule a call to debug the issue together.
This issue was caused by the VM referencing a certificate version in AKV that had been disabled due to auto-rotation of the certificate. Re-enabling the old certificate version unblocked it.
Root Cause :
The issue was identified as a disabled certificate in the Keyvault, which was causing the VM to fail during startup. After enabling the certificate, the VM started up successfully without any further problems. This resolved the startup failure and allowed normal operation to resume.