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
Copy file name to clipboardExpand all lines: articles/virtual-machines/extensions/key-vault-windows.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -213,7 +213,7 @@ The following JSON shows the schema for the Key Vault VM extension. The extensio
213
213
214
214
Azure VM extensions can be deployed with Azure Resource Manager templates. Templates are ideal when deploying one or more virtual machines that require post deployment refresh of certificates. The extension can be deployed to individual VMs or Virtual Machine Scale Sets. The schema and configuration are common to both template types.
215
215
216
-
The JSON configuration for a key vault extension is nested inside the virtual machine or virtual machine scale set template. For Virtual Machine resource extension is nested under `"resources": []` virtual machine object and Virtual Machine Scale Set under `"virtualMachineProfile":"extensionProfile":{"extensions" :[]` object.
216
+
The JSON configuration for a key vault extension is nested inside the virtual machine or Virtual Machine Scale Set template. For Virtual Machine resource extension is nested under `"resources": []` virtual machine object and Virtual Machine Scale Set under `"virtualMachineProfile":"extensionProfile":{"extensions" :[]` object.
217
217
218
218
### [Version-1.0](#tab/version1)
219
219
@@ -459,7 +459,7 @@ The Azure PowerShell can be used to deploy the Key Vault VM extension to an exis
459
459
460
460
### [Version-1.0](#tab/version1)
461
461
462
-
The Azure CLI can be used to deploy the Key Vault VM extension to an existing virtual machine or virtual machine scale set.
462
+
The Azure CLI can be used to deploy the Key Vault VM extension to an existing virtual machine or Virtual Machine Scale Set.
463
463
464
464
* Deploy the extension on a VM:
465
465
@@ -522,7 +522,7 @@ Example settings (settings.json):
522
522
}
523
523
```
524
524
525
-
The Azure CLI can be used to deploy the Key Vault VM extension to an existing virtual machine or virtual machine scale set.
525
+
The Azure CLI can be used to deploy the Key Vault VM extension to an existing virtual machine or Virtual Machine Scale Set.
526
526
527
527
* Deploy the extension on a VM:
528
528
@@ -551,9 +551,9 @@ The Azure CLI can be used to deploy the Key Vault VM extension to an existing vi
551
551
### Frequently Asked Questions
552
552
553
553
#### Is there a limit on the number of observedCertificates you can set up?
554
-
No, Key Vault VM Extension doesn’t have limit on the number of observedCertificates.
554
+
No, Key Vault VM Extension doesn’t have limit on the number of observedCertificates.
555
555
#### What will be the default permission if no account is provided in settings?
556
-
Administrators and SYSTEM will gets Full Control by default.
556
+
Administrators and SYSTEM will get Full Control by default.
557
557
#### How do you determine if a certificate key is going to be CAPI1 or CNG?
558
558
We rely on the default behavior of [PFXImportCertStore API](../../../windows/win32/api/wincrypt/nf-wincrypt-pfximportcertstore). By default, if a certificate has Provider Name attribute that matches with CAPI1, certificate will be imported using CAPI1 certificate, else it will be imported using CNG APIs.
0 commit comments