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/key-vault/general/about-keys-secrets-certificates.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,10 +14,10 @@ ms.author: mbaldwin
14
14
15
15
# Azure Key Vault keys, secrets and certificates overview
16
16
17
-
Azure Key Vault enables Microsoft Azure applications and users to store and use several types of secret/key data: keys, secrets, and certificates. All keys, secrets, and certificates are generically referred to as Objects.
17
+
Azure Key Vault enables Microsoft Azure applications and users to store and use several types of secret/key data: keys, secrets, and certificates. Keys, secrets, and certificates are collectively referred to as "objects".
18
18
19
-
## Object Identifiers
20
-
Objects are uniquely identified within Key Vault using a case-insensitive identifier called the Object Identifier. No two objects in the system have the same identifier, regardless of geo-location. The identifier consists of a prefix that identifies the Key Vault, object type, user provided Object Name, and an Object Version. Identifiers that don't include the Object Version are referred to as Base Identifiers. Key Vault Object Identifiers are also valid URL but should always be compared as case-insensitive strings.
19
+
## Object identifiers
20
+
Objects are uniquely identified within Key Vault using a case-insensitive identifier called the object identifier. No two objects in the system have the same identifier, regardless of geo-location. The identifier consists of a prefix that identifies the key vault, object type, user provided object name, and an object version. Identifiers that don't include the object version are referred to as "base identifiers". Key Vault object identifiers are also valid URLs, but should always be compared as case-insensitive strings.
21
21
22
22
For more information, see [Authentication, requests, and responses](authentication-requests-and-responses.md)
23
23
@@ -36,13 +36,13 @@ Where:
36
36
37
37
| Element | Description |
38
38
|-|-|
39
-
|`vault-name` or `hsm-name`|The name for a vault or a Managed HSM pool in the Microsoft Azure Key Vault service.<br /><br />Vault names and Managed HSM pool names are selected by the user and are globally unique.<br /><br />Vault name and Managed HSM pool name must be a 3-24 character string, containing only 0-9, a-z, A-Z, and not consecutive -.|
40
-
|`object-type`|The type of the object, "keys", "secrets", or 'certificates'.|
41
-
|`object-name`|An `object-name` is a user provided name for and must be unique within a Key Vault. The name must be a 1-127 character string, starting with a letter and containing only 0-9, a-z, A-Z, and -.|
42
-
|`object-version`|An `object-version` is a system-generated, 32 character string identifier that is optionally used to address a unique version of an object.|
39
+
|`vault-name` or `hsm-name`|The name for a key vault or a Managed HSM pool in the Microsoft Azure Key Vault service.<br /><br />Vault names and Managed HSM pool names are selected by the user and are globally unique.<br /><br />Vault name and Managed HSM pool name must be a 3-24 character string, containing only 0-9, a-z, A-Z, and not consecutive -.|
40
+
|`object-type`|The type of the object, "keys", "secrets", or "certificates".|
41
+
|`object-name`|An `object-name` is a user provided name for and must be unique within a key vault. The name must be a 1-127 character string, starting with a letter and containing only 0-9, a-z, A-Z, and -.|
42
+
|`object-version`|An `object-version` is a system-generated, 32 character string identifier that is optionally used to address a unique version of an object.|
43
43
44
44
## DNS suffixes for object identifiers
45
-
Key Vault resource provider supports two resource types: vaults and managed HSMs. This table shows the DNS suffix used by the data-plane endpoint for vaults and managed HSM pools in various cloud environments.
45
+
The Azure Key Vault resource provider supports two resource types: vaults and managed HSMs. This table shows the DNS suffix used by the data-plane endpoint for vaults and managed HSM pools in various cloud environments.
46
46
47
47
Cloud environment | DNS suffix for vaults | DNS suffix for managed HSMs
0 commit comments