Skip to content

Commit 0d6f383

Browse files
authored
Update key-vault-windows.md
The existing documentation is missing some key details on how to configure the dependencies between VMMS extensions. Adding this link should help with defining these dependencies more easily.
1 parent f59b642 commit 0d6f383

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

articles/virtual-machines/extensions/key-vault-windows.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -317,6 +317,8 @@ To enable waiting for certificate to be installed, set the following setting:
317317
}
318318
```
319319

320+
Refer to [Sequence extension provisioning in Virtual Machine Scale Sets](../../virtual-machine-scale-sets/virtual-machine-scale-sets-extension-sequencing.md) on how to set-up dependencies between extensions.
321+
320322
> [!Note]
321323
> Using this feature is not compatible with an ARM template that creates a system assigned identity and updates a Key Vault access policy with that identity. Doing so will result in a deadlock as the vault access policy cannot be updated until all extensions have started. You should instead use a *single user assigned MSI identity* and pre-ACL your vaults with that identity before deploying.
322324

0 commit comments

Comments
 (0)