Merge pull request #224561 from msmbaldwin/akv-misc

Updates

Author: prmerger-automator[bot]

articles/key-vault/general/authentication-requests-and-responses.md

@@ -9,7 +9,7 @@ tags: azure-resource-manager
 ms.service: key-vault
 ms.subservice: general
 ms.topic: conceptual
-ms.date: 09/15/2020
+ms.date: 01/20/2023
 ms.author: mbaldwin
 
 ---

articles/key-vault/general/client-libraries.md

@@ -8,19 +8,19 @@ tags: azure-resource-manager
 ms.service: key-vault
 ms.subservice: general
 ms.topic: tutorial
-ms.date: 08/14/2020
+ms.date: 01/20/2023
 ms.author: mbaldwin
 
 
 ---
 
 # Client Libraries for Azure Key Vault
 
-The client libraries for Azure Key Vault allow programmatic access to Key Vault functionality from a variety of languages, including .NET, Python, Java, and JavaScript.
+The client libraries for Azure Key Vault allow programmatic access to Key Vault functionality from a several languages, including .NET, Python, Java, and JavaScript.
 
 ## Client libraries per language and object
 
-Each SDK has separate client libraries for key vault, secrets, keys, and certificates, per the table below.
+Each SDK has separate client libraries for key vault, secrets, keys, and certificates.
 
 | Language | Secrets | Keys | Certificates | Key Vault (Management plane) |
 |--|--|--|--|--|

articles/key-vault/general/integrate-databricks-blob-storage.md

@@ -5,7 +5,7 @@ author: msmbaldwin #Required; your GitHub user alias, with correct capitalizatio
 ms.author: mbaldwin #Required; microsoft alias of author; optional team alias.
 ms.service: key-vault #Required; service per approved list. service slug assigned to your service by ACOM.
 ms.topic: tutorial
-ms.date: 06/16/2020 #Required; mm/dd/yyyy format.
+ms.date: 01/20/2023
 ---
 
 # Tutorial: Access Azure Blob Storage using Azure Databricks and Azure Key Vault

articles/key-vault/general/logging.md

@@ -8,16 +8,16 @@ tags: azure-resource-manager
 ms.service: key-vault
 ms.subservice: general
 ms.topic: how-to
-ms.date: 12/18/2020
+ms.date: 01/20/2023
 ms.author: mbaldwin
 #Customer intent: As an Azure Key Vault administrator, I want to enable logging so I can monitor how my key vaults are accessed.
 ---
 
 # Azure Key Vault logging
 
-After you create one or more key vaults, you'll likely want to monitor how and when your key vaults are accessed, and by whom. You can do this by enabling logging for Azure Key Vault, which saves information in an Azure storage account that you provide. For step by step guidance on setting this up, see [How to enable Key Vault logging](howto-logging.md).
+After you create one or more key vaults, you'll likely want to monitor how and when your key vaults are accessed, and by whom. Enabling logging for Azure Key Vault saves this information in an Azure storage account that you provide. For step by step guidance, see [How to enable Key Vault logging](howto-logging.md).
 
-You can access your logging information 10 minutes (at most) after the key vault operation. In most cases, it will be quicker than this.  It's up to you to manage your logs in your storage account:
+You can access your logging information 10 minutes (at most) after the key vault operation. In most cases, it will be quicker.  It's up to you to manage your logs in your storage account:
 
 * Use standard Azure access control methods in your storage account to secure your logs by restricting who can access them.
 * Delete logs that you no longer want to keep in your storage account.
@@ -58,17 +58,17 @@ The following table lists the field names and descriptions:
 | Field name | Description |
 | --- | --- |
 | **time** |Date and time in UTC. |
-| **resourceId** |Azure Resource Manager resource ID. For Key Vault logs, this is always the Key Vault resource ID. |
+| **resourceId** |Azure Resource Manager resource ID. For Key Vault logs, it is always the Key Vault resource ID. |
 | **operationName** |Name of the operation, as documented in the next table. |
 | **operationVersion** |REST API version requested by the client. |
 | **category** |Type of result. For Key Vault logs, `AuditEvent` is the single, available value. |
 | **resultType** |Result of the REST API request. |
 | **resultSignature** |HTTP status. |
-| **resultDescription** |Additional description about the result, when available. |
-| **durationMs** |Time it took to service the REST API request, in milliseconds. This does not include the network latency, so the time you measure on the client side might not match this time. |
+| **resultDescription** |More description about the result, when available. |
+| **durationMs** |Time it took to service the REST API request, in milliseconds. The time does not include the network latency, so the time you measure on the client side might not match this time. |
 | **callerIpAddress** |IP address of the client that made the request. |
 | **correlationId** |An optional GUID that the client can pass to correlate client-side logs with service-side (Key Vault) logs. |
-| **identity** |Identity from the token that was presented in the REST API request. This is usually a "user," a "service principal," or the combination "user+appId," as in the case of a request that results from an Azure PowerShell cmdlet. |
+| **identity** | Identity from the token that was presented in the REST API request. Usually a "user," a "service principal," or the combination "user+appId", for instance when the request comes from a Azure PowerShell cmdlet. |
 | **properties** |Information that varies based on the operation (**operationName**). In most cases, this field contains client information (the user agent string passed by the client), the exact REST API request URI, and the HTTP status code. In addition, when an object is returned as a result of a request (for example, **KeyCreate** or **VaultGet**), it also contains the key URI (as `id`), vault URI, or secret URI. |
 
 The **operationName** field values are in *ObjectVerb* format. For example:
@@ -190,9 +190,9 @@ The following table lists the **operationName** values and corresponding REST AP
 
 You can use the Key Vault solution in Azure Monitor logs to review Key Vault `AuditEvent` logs. In Azure Monitor logs, you use log queries to analyze data and get the information you need. 
 
-For more information, including how to set this up, see [Azure Key Vault in Azure Monitor](../key-vault-insights-overview.md).
+For more information, including how to set it up, see [Azure Key Vault in Azure Monitor](../key-vault-insights-overview.md).
 
-For understanding how to analyze logs, see [Sample kusto log queries](./monitor-key-vault.md#analyzing-logs)
+For understanding how to analyze logs, see [Sample Kusto log queries](./monitor-key-vault.md#analyzing-logs)
 
 ## Next steps
 

articles/key-vault/general/move-subscription.md

@@ -8,7 +8,7 @@ tags: azure-resource-manager
 ms.service: key-vault
 ms.subservice: general
 ms.topic: how-to
-ms.date: 05/05/2020
+ms.date: 01/20/2023
 ms.author: mbaldwin 
 ms.custom: devx-track-azurepowershell
 # Customer intent: As a key vault administrator, I want to move my vault to another subscription.
@@ -46,7 +46,7 @@ For more information about Azure Key Vault and Azure Active Directory, see
 > **Key Vaults used for disk encryption cannot be moved**
 > If you are using key vault with disk encryption for a VM, the key vault cannot be moved to a different resource group or a subscription while disk encryption is enabled. You must disable disk encryption prior to moving the key vault to a new resource group or subscription. 
 
-Some service principals (users and applications) are bound to a specific tenant. If you move your key vault to a subscription in another tenant, there is a chance that you will not be able to restore access to a specific service principal. Check to make sure that all essential service principals exist in the tenant where you are moving your key vault.
+Some service principals (users and applications) are bound to a specific tenant. If you move your key vault to a subscription in another tenant, there's a chance that you won't be able to restore access to a specific service principal. Check to make sure that all essential service principals exist in the tenant where you are moving your key vault.
 
 ## Prerequisites
 
@@ -61,7 +61,7 @@ You can check existing roles using [Azure portal](../../role-based-access-contro
 
 1. Sign in to the Azure portal at https://portal.azure.com.
 2. Navigate to your [key vault](overview.md)
-3. Click on the "Overview" tab
+3. Select on the "Overview" tab
 4. Select the "Move" button
 5. Select "Move to another subscription" from the dropdown options
 6. Select the resource group where you want to move your key vault
@@ -70,7 +70,7 @@ You can check existing roles using [Azure portal](../../role-based-access-contro
 
 ## Additional steps when subscription is in a new tenant
 
-If you moved your key vault to a subscription in a new tenant, you need to manually update the tenant ID and remove old access policies and role assignments. Here are tutorials for these steps in PowerShell and Azure CLI. If you are using PowerShell, you may need to run the Clear-AzContext command documented below to allow you to see resources outside your current selected scope. 
+If you moved your key vault to a subscription in a new tenant, you need to manually update the tenant ID and remove old access policies and role assignments. Here are tutorials for these steps in PowerShell and Azure CLI. If you are using PowerShell, you may need to run the Clear-AzContext command to allow you to see resources outside your current selected scope. 
 
 ### Update tenant ID in a key vault
 

articles/key-vault/general/rbac-migration.md

@@ -6,7 +6,7 @@ author: msmbaldwin
 ms.service: key-vault
 ms.subservice: general
 ms.topic: how-to
-ms.date: 8/30/2020
+ms.date: 01/20/2023
 ms.author: mbaldwin
 
 ---