Skip to content

Commit 356d3b4

Browse files
Merge pull request #217935 from jlichwa/patch-34
Update key-vault-windows.md
2 parents de55bd6 + 1e73ad7 commit 356d3b4

File tree

1 file changed

+4
-3
lines changed

1 file changed

+4
-3
lines changed

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

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -20,6 +20,7 @@ The Key Vault VM extension provides automatic refresh of certificates stored in
2020

2121
The Key Vault VM extension supports below versions of Windows:
2222

23+
- Windows Server 2022
2324
- Windows Server 2019
2425
- Windows Server 2016
2526
- Windows Server 2012
@@ -62,7 +63,7 @@ The Key Vault VM extension is also supported on custom local VM that is uploaded
6263

6364
## Extension schema
6465

65-
The following JSON shows the schema for the Key Vault VM extension. The extension does not require protected settings - all its settings are considered public information. The extension requires a list of monitored certificates, polling frequency, and the destination certificate store. Specifically:
66+
The following JSON shows the schema for the Key Vault VM extension. The extension doesn't require protected settings - all its settings are considered public information. The extension requires a list of monitored certificates, polling frequency, and the destination certificate store. Specifically:
6667

6768
```json
6869
{
@@ -163,7 +164,7 @@ The JSON configuration for a virtual machine extension must be nested inside the
163164
```
164165

165166
### Extension Dependency Ordering
166-
The Key Vault VM extension supports extension ordering if configured. By default the extension reports that it has successfully started as soon as it has started polling. However, it can be configured to wait until it has successfully downloaded the complete list of certificates before reporting a successful start. If other extensions depend on having the full set of certificates install before they start, then enabling this setting will allow those extension to declare a dependency on the Key Vault extension. This will prevent those extensions from starting until all certificates they depend on have been installed. The extension will retry the initial download indefinitely and remain in a `Transitioning` state.
167+
The Key Vault VM extension supports extension ordering if configured. By default the extension reports that it has successfully started as soon as it has started polling. However, it can be configured to wait until it has successfully downloaded the complete list of certificates before reporting a successful start. If other extensions depend on having the full set of certificates installed before they start, then enabling this setting will allow those extensions to declare a dependency on the Key Vault extension. This will prevent those extensions from starting until all certificates they depend on have been installed. The extension will retry the initial download indefinitely and remain in a `Transitioning` state.
167168

168169
To turn this on set the following:
169170
```
@@ -271,7 +272,7 @@ Please be aware of the following restrictions/requirements:
271272
272273
### Frequently Asked Questions
273274
274-
* Is there is a limit on the number of observedCertificates you can setup?
275+
* Is there a limit on the number of observedCertificates you can set up?
275276
No, Key Vault VM Extension doesn’t have limit on the number of observedCertificates.
276277
277278
### Troubleshoot

0 commit comments

Comments
 (0)