Skip to content

Commit 109c5ab

Browse files
committed
added clientid
1 parent a49692f commit 109c5ab

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ First, you need to have an [Azure Active Directory](https://azure.microsoft.com/
3434

3535
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.
3636

37-
* After the application is added, find the **Application ID** on the **Registered app** blade.
37+
* After the application is added, find the **Application ID** (also known as AAD ClientID or AppID) on the **Registered app** blade.
3838
The application ID is assigned later to the **$spName** (Service Principal name) parameter in the PowerShell script to enable Azure Key Vault Integration.
3939

4040
![Application ID](./media/virtual-machines-sql-server-akv-prepare/aad-application-id.png)

0 commit comments

Comments
 (0)