You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -28,16 +28,16 @@ The Key Vault VM extension supports the following versions of Windows:
28
28
29
29
The Key Vault VM extension is also supported on a custom local VM. The VM should be uploaded and converted into a specialized image for use in Azure by using Windows Server 2019 core install.
30
30
31
-
> [!NOTE]
32
-
> The Key Vault VM extension downloads all certificates to the Windows certificate store or to the location specified in the `certificateStoreLocation` property in the VM extension settings.
33
-
34
-
### Supported certificate content types
31
+
### Supported certificates
35
32
36
33
The Key Vault VM extension supports the following certificate content types:
37
34
38
35
- PKCS #12
39
36
- PEM
40
37
38
+
> [!NOTE]
39
+
> The Key Vault VM extension downloads all certificates to the Windows certificate store or to the location specified in the `certificateStoreLocation` property in the VM extension settings.
40
+
41
41
## Updates in Version 3.0
42
42
43
43
Version 3.0 of the Key Vault VM extension for Windows adds support for the following features:
@@ -61,7 +61,7 @@ Review the following prerequisites for using the Key Vault VM extension for Wind
61
61
62
62
- Virtual Machine Scale Sets should have the following `identity` configuration:
63
63
64
-
```
64
+
```json
65
65
"identity": {
66
66
"type": "UserAssigned",
67
67
"userAssignedIdentities": {
@@ -72,7 +72,7 @@ Review the following prerequisites for using the Key Vault VM extension for Wind
72
72
73
73
- The Key Vault VM extension should have the following `authenticationSettings` configuration:
@@ -89,7 +89,7 @@ The following JSON shows the schema for the Key Vault VM extension. Before you c
89
89
90
90
- The extension doesn't require protected settings. All settings are considered public information.
91
91
92
-
- Observed certificates URLs should be of the form "https://myVaultName.vault.azure.net/secrets/myCertName".
92
+
- Observed certificates URLs should be of the form `https://myVaultName.vault.azure.net/secrets/myCertName`.
93
93
94
94
This form is preferred because the `/secrets` path returns the full certificate, including the private key, but the `/certificates` path doesn't. For more information about certificates, see [Azure Key Vault keys, secrets and certificates overview](/azure/key-vault/general/about-keys-secrets-certificates).
95
95
@@ -181,7 +181,7 @@ The following JSON shows the schema for the Key Vault VM extension. Before you c
181
181
182
182
## Property values
183
183
184
-
The JSON schema includes values for the following properties.
184
+
The JSON schema includes the following properties.
185
185
186
186
### [Version-3.0](#tab/version3)
187
187
@@ -216,7 +216,7 @@ The JSON schema includes values for the following properties.
216
216
|`linkOnRenewal`| true | boolean |
217
217
|`certificateStoreLocation`| LocalMachine or CurrentUser (case sensitive) | string |
@@ -419,55 +415,55 @@ Use PowerShell to deploy the version 1.0 Key Vault VM extension to an existing V
419
415
> [!WARNING]
420
416
> PowerShell clients often prefix a quote mark `"` with a backslash `\` in the settings JSON file. The extraneous characters cause the akvvm_service to fail with the error, "[CertificateManagementConfiguration] Failed to parse the configuration settings with:not an object."
421
417
>
422
-
> You can see the supplied backslash `\` and quote `"` characters in the Azure portal. Check the contents of the settings JSON file under **Settings** > **Extensions**. To avoid the error, initialize the `$settings` property as a PowerShell `HashTable` as follows:
418
+
> You can see the supplied backslash `\` and quote `"` characters in the Azure portal. Check the contents of the settings JSON file under **Settings** > **Extensions + Applications**. To avoid the error, initialize the `$settings` property as a PowerShell `HashTable` as follows:
0 commit comments