Skip to content

Commit c446363

Browse files
committed
Updates
1 parent b373bc9 commit c446363

File tree

6 files changed

+14
-13
lines changed

6 files changed

+14
-13
lines changed

articles/attestation/quickstart-powershell.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ Follow the below steps to create and configure an attestation provider using Azu
1717

1818
> [!NOTE]
1919
> 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
2121

2222
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:
2323

articles/attestation/troubleshoot-guide.md

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -52,7 +52,7 @@ In order to manage policies, an Azure AD user requires the following permissions
5252
In order to read policies, an Azure AD user requires the following permission for "Actions":
5353
- Microsoft.Attestation/attestationProviders/attestation/read
5454

55-
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.
5656

5757
To verify the roles in PowerShell, run the below steps:
5858

@@ -215,6 +215,7 @@ InvalidOperation
215215
Invalid content provided (for example, upload policy/ unsigned policy when policy signing is required)
216216

217217
```
218+
218219
Native operation failed with 74: ..\Shared\base64url.h(226)\(null)!: (caller: ) Exception(0) 83FF004A Bad message Msg:[Unknown base64 character: 41 (')')]
219220
..\Enclave\api.cpp(618)\(null)!: (caller: ) LogHr(0) 83FF004A Bad message Msg:[Unhandled Enclave Exception: "Bad message"]
220221
At line:1 char:1
@@ -229,7 +230,7 @@ Ensure that the policy in Text format is UTF-8 encoded.
229230

230231
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.
231232

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.
233234

234235
To configure a policy in text format, specify policy text directly.
235236

@@ -239,12 +240,12 @@ See attestation [policy examples](./policy-examples.md) and [how to author an at
239240

240241
## 3. Az.Attestation installation issues in PowerShell
241242

242-
Unable to install Az or Az.Attestation modules in PowerShell
243+
Unable to install Az Powershell or Az.Attestation PowerShell modules in PowerShell
243244

244245
### Error
245246

246247
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
248249

249250
### Troubleshooting steps
250251

articles/key-vault/general/network-security.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ This section will cover the different ways that an Azure Key Vault firewall can
2323

2424
### Key Vault Firewall Disabled (Default)
2525

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).
2727

2828
### Key Vault Firewall Enabled (Trusted Services Only)
2929

@@ -38,9 +38,9 @@ If you would like to authorize a particular service to access key vault through
3838

3939
To allow an IP Address or range of an Azure resource, such as a Web App or Logic App, perform the following steps.
4040

41-
1. Log in to the Azure portal.
41+
1. Sign in to the Azure portal.
4242
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'.
4444
1. Look for the "IP Address" field.
4545
1. Copy this value or range and enter it into the key vault firewall allowlist.
4646

@@ -52,7 +52,7 @@ If you are trying to allow an Azure resource such as a virtual machine through k
5252

5353
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.
5454

55-
1. Log in to the Azure portal
55+
1. Sign in to the Azure portal
5656
1. Select the key vault you wish to configure
5757
1. Select the 'Networking' blade
5858
1. Select '+ Add existing virtual network'

articles/key-vault/general/troubleshooting-access-issues.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -53,7 +53,7 @@ If you're creating an on-premises application, doing local development, or other
5353

5454
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).
5555

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.
5757

5858
### How can I redeploy Key Vault with ARM template without deleting existing access policies?
5959

articles/key-vault/key-vault-insights-overview.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -74,7 +74,7 @@ These views are also accessible by selecting the resource name of a key vault fr
7474

7575
![Screenshot of view from a key vault resource](./media/key-vaults-insights-overview/key-vault-resource-view.png)
7676

77-
On the **Overview** workbook for the key vault, it shows several performance metrics that help you quickly assess:
77+
On the **Overview** workbook for the key vault, it shows:
7878

7979
- Interactive performance charts showing the most essential details related to key vault transactions, latency, and availability.
8080

@@ -165,7 +165,7 @@ The time range will depend on the dashboard settings.
165165

166166
### What if I want to see other data or make my own visualizations? How can I make changes to the Key Vault Insights
167167

168-
You can edit the existing workbookwith edit mode, and then save your work as a new workbook that will have all your new changes.
168+
You can edit the existing workbook with edit mode, and then save your work as a new workbook that will have all your new changes.
169169

170170
## Next steps
171171

articles/key-vault/keys/about-keys-details.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -139,7 +139,7 @@ For more information on other possible attributes, see the [JSON Web Key (JWK)](
139139

140140
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.
141141

142-
> [!NOTE]
142+
> [!NOTE]
143143
> Tags are readable by a caller if they have the *list* or *get* permission to that key.
144144
145145
## Key access control

0 commit comments

Comments
 (0)