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/attestation/quickstart-powershell.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,7 +17,7 @@ Follow the below steps to create and configure an attestation provider using Azu
17
17
18
18
> [!NOTE]
19
19
> Az.Attestation module is now integrated into Az PowerShell module. Minimum version of Az module required to support attestation operations:
20
-
- Az PowerShell 6.5.0
20
+
- Az PowerShell module 6.5.0
21
21
22
22
The PowerShell Gallery has deprecated Transport Layer Security (TLS) versions 1.0 and 1.1. TLS 1.2 or a later version is recommended. Hence you may receive the following errors:
To perform this action, an Azure AD user must have "Attestation Reader" role on the attestation provider. The read permissions can be also be inherited with roles such as "Reader" (wildcard permissions) on the subscription/ resource group.
55
+
To perform this action, an Azure AD user must have "Attestation Reader" role on the attestation provider. Read permissions are also part of roles such as "Reader" (wildcard permissions) on the subscription/ resource group.
56
56
57
57
To verify the roles in PowerShell, run the below steps:
58
58
@@ -215,6 +215,7 @@ InvalidOperation
215
215
Invalid content provided (for example, upload policy/ unsigned policy when policy signing is required)
216
216
217
217
```
218
+
218
219
Native operation failed with 74: ..\Shared\base64url.h(226)\(null)!: (caller: ) Exception(0) 83FF004A Bad message Msg:[Unknown base64 character: 41 (')')]
@@ -229,7 +230,7 @@ Ensure that the policy in Text format is UTF-8 encoded.
229
230
230
231
If policy signing is required, attestation policy must be configured only in RFC7519 JSON Web Token (JWT) format. If policy signing is not required, policy can be configured in text or JWT format.
231
232
232
-
To configure a policy in JWT format, use JWT with a claim named "AttestationPolicy". Value of the claim is Base64URL encoded version of the policy text. If the attestation provider is configured with policy signer certificates, the JWT must be signed with private key of any of the valid policy signer certificates associated with the provider.
233
+
To configure a policy in JWT format, use JWT with a claim named "AttestationPolicy". Value of the claim is Base64URL encoded version of the policy text. If the attestation provider is configured with policy signer certificates, the JWT must be signed with private key of any of the valid policy signer certificates associated with the provider.
233
234
234
235
To configure a policy in text format, specify policy text directly.
235
236
@@ -239,12 +240,12 @@ See attestation [policy examples](./policy-examples.md) and [how to author an at
239
240
240
241
## 3. Az.Attestation installation issues in PowerShell
241
242
242
-
Unable to install Az or Az.Attestation modules in PowerShell
243
+
Unable to install Az Powershell or Az.Attestation PowerShell modules in PowerShell
243
244
244
245
### Error
245
246
246
247
WARNING: Unable to resolve package source 'https://www.powershellgallery.com/api/v2'
247
-
PackageManagement\Install-Package: No match was found for the specified search criteria and module name
248
+
PackageManagement\Install-Package: No match was found for the specified search criteria and module name
Copy file name to clipboardExpand all lines: articles/key-vault/general/network-security.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,7 +23,7 @@ This section will cover the different ways that an Azure Key Vault firewall can
23
23
24
24
### Key Vault Firewall Disabled (Default)
25
25
26
-
By default, when you create a new key vault, the Azure Key Vault firewall is disabled. All applications and Azure services can access the key vault and send requests to the key vault. Note, this configuration doesn't mean that any user will be able to perform operations on your key vault. The key vault still restricts access to secrets, keys, and certificates stored in key vault by requiring Azure Active Directory authentication and access policy permissions. To understand key vault authentication in more detail, see [Authentication in Azure Key Vault](authentication.md). For more information, see [Access Azure Key Vault behind a firewall](access-behind-firewall.md).
26
+
By default, when you create a new key vault, the Azure Key Vault firewall is disabled. All applications and Azure services can access the key vault and send requests to the key vault. This configuration doesn't mean that any user will be able to perform operations on your key vault. The key vault still restricts access to secrets, keys, and certificates stored in key vault by requiring Azure Active Directory authentication and access policy permissions. To understand key vault authentication in more detail, see [Authentication in Azure Key Vault](authentication.md). For more information, see [Access Azure Key Vault behind a firewall](access-behind-firewall.md).
@@ -38,9 +38,9 @@ If you would like to authorize a particular service to access key vault through
38
38
39
39
To allow an IP Address or range of an Azure resource, such as a Web App or Logic App, perform the following steps.
40
40
41
-
1.Log in to the Azure portal.
41
+
1.Sign in to the Azure portal.
42
42
1. Select the resource (specific instance of the service).
43
-
1.Click on the 'Properties' blade under 'Settings'.
43
+
1.Select on the 'Properties' blade under 'Settings'.
44
44
1. Look for the "IP Address" field.
45
45
1. Copy this value or range and enter it into the key vault firewall allowlist.
46
46
@@ -52,7 +52,7 @@ If you are trying to allow an Azure resource such as a virtual machine through k
52
52
53
53
In this case, you should create the resource within a virtual network, and then allow traffic from the specific virtual network and subnet to access your key vault.
Copy file name to clipboardExpand all lines: articles/key-vault/general/troubleshooting-access-issues.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -53,7 +53,7 @@ If you're creating an on-premises application, doing local development, or other
53
53
54
54
Give the AD group permissions to your key vault using the Azure CLI `az keyvault set-policy` command, or the Azure PowerShell Set-AzKeyVaultAccessPolicy cmdlet. See [Assign an access policy - CLI](assign-access-policy-cli.md) and [Assign an access policy - PowerShell](assign-access-policy-powershell.md).
55
55
56
-
The application also needs at least one Identity and Access Management (IAM) role assigned to the key vault. Otherwise it will not be able to login and will fail with insufficient rights to access the subscription. Azure AD Groups with Managed Identities may require up to eight hours to refresh tokens and become effective.
56
+
The application also needs at least one Identity and Access Management (IAM) role assigned to the key vault. Otherwise it will not be able to log in and will fail with insufficient rights to access the subscription. Azure AD Groups with Managed Identities may require up to eight hours to refresh tokens and become effective.
57
57
58
58
### How can I redeploy Key Vault with ARM template without deleting existing access policies?
Copy file name to clipboardExpand all lines: articles/key-vault/keys/about-keys-details.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -139,7 +139,7 @@ For more information on other possible attributes, see the [JSON Web Key (JWK)](
139
139
140
140
You can specify more application-specific metadata in the form of tags. Key Vault supports up to 15 tags, each of which can have a 256 character name and a 256 character value.
141
141
142
-
> [!NOTE]
142
+
> [!NOTE]
143
143
> Tags are readable by a caller if they have the *list* or *get* permission to that key.
0 commit comments