Merge pull request #106378 from dahlweid/patch-1

Court72 · web-flow · commit 50facb7a01a4 · 2023-03-15T09:00:51.000-06:00
Update key-vault-windows.md
diff --git a/articles/virtual-machines/extensions/key-vault-windows.md b/articles/virtual-machines/extensions/key-vault-windows.md
@@ -317,6 +317,8 @@ To enable waiting for certificate to be installed, set the following setting:
 }
 ```
 
+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.
+
 > [!Note] 
 > 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.
 

Original file line number	Diff line number	Diff line change
`@@ -317,6 +317,8 @@ To enable waiting for certificate to be installed, set the following setting:`
`317`	`317`	`}`
`318`	`318`	```
`319`	`319`
	`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`	`+`
`320`	`322`	`> [!Note]`
`321`	`323`	`> 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.`
`322`	`324`