Merge pull request #108099 from MashaMSFT/20200317_fixes

ClientID clarity

Author: PRMerger12

includes/virtual-machines-sql-server-akv-prepare.md

@@ -34,7 +34,7 @@ First, you need to have an [Azure Active Directory](https://azure.microsoft.com/
 
 Next, register an application with AAD. This will give you a Service Principal account that has access to your key vault, which your VM will need. In the Azure Key Vault article, you can find these steps in the [Register an application with Azure Active Directory](../articles/key-vault/key-vault-manage-with-cli2.md#registering-an-application-with-azure-active-directory) section, or you can see the steps with screenshots in the **Get an identity for the application section** of [this blog post](https://blogs.technet.com/b/kv/archive/2015/01/09/azure-key-vault-step-by-step.aspx). Before completing these steps, you need to collect the following information during this registration that is needed later when you enable Azure Key Vault Integration on your SQL VM.
 
-* After the application is added, find the **Application ID** on the **Registered app** blade.
+* After the application is added, find the **Application ID** (also known as AAD ClientID or AppID) on the **Registered app** blade.
     The application ID is assigned later to the **$spName** (Service Principal name) parameter in the PowerShell script to enable Azure Key Vault Integration.
 
    ![Application ID](./media/virtual-machines-sql-server-akv-prepare/aad-application-id.png)
@@ -45,7 +45,7 @@ Next, register an application with AAD. This will give you a Service Principal a
 
 * The application ID and the secret will also be used to create a credential in SQL Server.
 
-* You must authorize this new client ID to have the following access permissions: **get**, **wrapKey**, **unwrapKey**. This is done with the [Set-AzKeyVaultAccessPolicy](https://docs.microsoft.com/powershell/module/az.keyvault/set-azkeyvaultaccesspolicy) cmdlet. For more information, see [Azure Key Vault overview](../articles/key-vault/key-vault-overview.md).
+* You must authorize this new application ID (or client ID) to have the following access permissions: **get**, **wrapKey**, **unwrapKey**. This is done with the [Set-AzKeyVaultAccessPolicy](https://docs.microsoft.com/powershell/module/az.keyvault/set-azkeyvaultaccesspolicy) cmdlet. For more information, see [Azure Key Vault overview](../articles/key-vault/key-vault-overview.md).
 
 ### <a id="createkeyvault"></a> Create a key vault
 In order to use Azure Key Vault to store the keys you will use for encryption in your VM, you need access to a key vault. If you have not already set up your key vault, create one by following the steps in the [Getting Started with Azure Key Vault](../articles/key-vault/key-vault-overview.md) article. Before completing these steps, there is some information you need to collect during this set up that is needed later when you enable Azure Key Vault Integration on your SQL VM.