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
This command imports the key named ITByok from the location that the KeyFilePath parameter specifies.
98
+
This command imports the key named ITByok from the location that the *KeyFilePath* parameter specifies.
98
99
The imported key is an HSM-protected key.
99
100
100
101
To import a key from your own hardware security module, you must first generate a BYOK package (a file with a .byok file name extension) by using the Azure Key Vault BYOK toolset.
The first command converts a string into a secure string by using the ConvertTo-SecureString cmdlet, and then stores that string in the $Password variable.
110
-
For more information, type Get-Help ConvertTo-SecureString.
110
+
The first command converts a string into a secure string by using the **ConvertTo-SecureString** cmdlet, and then stores that string in the $Password variable.
111
+
For more information, type `Get-Help ConvertTo-SecureString`.
111
112
112
113
The second command creates a software password in the Contoso key vault.
113
114
The command specifies the location for the key and the password stored in $Password.
The first command converts a string into a secure string by using the ConvertTo-SecureString cmdlet, and then stores that string in the $Password variable.
124
+
The first command converts a string into a secure string by using the **ConvertTo-SecureString** cmdlet, and then stores that string in the $Password variable.
124
125
125
-
The second command creates a DateTime object by using the Get-Date cmdlet, and then stores that object in the $Expires variable.
126
+
The second command creates a **DateTime** object by using the **Get-Date** cmdlet, and then stores that object in the $Expires variable.
126
127
127
128
The third command creates the $tags variable to set tags for high severity and IT.
128
129
@@ -139,12 +140,12 @@ Note: To use HSM as your destination, you must have a key vault that supports HS
139
140
For more information about the service tiers and capabilities for Azure Key Vault, see the Azure Key Vault Pricing website (http://go.microsoft.com/fwlink/?linkid=512521).
140
141
141
142
This parameter is required when you create a new key.
142
-
If you import a key by using the KeyFilePath parameter, this parameter is optional:
143
+
If you import a key by using the *KeyFilePath* parameter, this parameter is optional:
143
144
144
-
-- If you do not specify this parameter, and this cmdlet imports a key that has .byok file name extension, it imports that key as an HSM-protected key.
145
+
- If you do not specify this parameter, and this cmdlet imports a key that has .byok file name extension, it imports that key as an HSM-protected key.
145
146
The cmdlet cannot import that key as software-protected key.
146
147
147
-
-- If you do not specify this parameter, and this cmdlet imports a key that has a .pfx file name extension, it imports the key as a software-protected key.
148
+
- If you do not specify this parameter, and this cmdlet imports a key that has a .pfx file name extension, it imports the key as a software-protected key.
Specifies the path of a local file that contains key material that this cmdlet imports.
231
232
The valid file name extensions are .byok and .pfx.
232
233
233
-
-- If the file is a .byok file, the key is automatically protected by HSMs after the import and you cannot override this default.
234
+
- If the file is a .byok file, the key is automatically protected by HSMs after the import and you cannot override this default.
234
235
235
-
-- If the file is a .pfx file, the key is automatically protected by software after the import.
236
-
To override this default, set the Destination parameter to HSM so that the key is HSM-protected.
236
+
- If the file is a .pfx file, the key is automatically protected by software after the import.
237
+
To override this default, set the *Destination* parameter to HSM so that the key is HSM-protected.
237
238
238
-
When you specify this parameter, the Destination parameter is optional.
239
+
When you specify this parameter, the *Destination* parameter is optional.
239
240
240
241
```yaml
241
242
Type: String
@@ -255,14 +256,14 @@ If you do not specify this parameter, all operations can be performed.
255
256
256
257
The acceptable values for this parameter are a comma-separated list of key operations as defined by the JSON Web Key (JWK) specification (http://go.microsoft.com/fwlink/?LinkID=613300&clcid=0x409):
Specifies a hash table that contains certificate tags.
348
+
349
+
To use HSM as your destination, you must have a key vault that supports HSMs.
350
+
For more information about the service tiers and capabilities for Azure Key Vault, see the Azure Key Vault Pricing website (http://go.microsoft.com/fwlink/?linkid=512521).
351
+
352
+
This parameter is required when you create a new key.
353
+
If you import a key by using the *KeyFilePath* parameter, this parameter is optional:
354
+
355
+
- If you do not specify this parameter, and this cmdlet imports a key that has .byok file name extension, it imports that key as an HSM-protected key.
356
+
The cmdlet cannot import that key as software-protected key.
357
+
358
+
- If you do not specify this parameter, and this cmdlet imports a key that has a .pfx file name extension, it imports the key as a software-protected key.
347
359
348
360
```yaml
349
361
Type: Hashtable
@@ -388,11 +400,11 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable
0 commit comments