Skip to content

Commit a639dbd

Browse files
committed
update links to png and files
1 parent 2534f2a commit a639dbd

File tree

1 file changed

+19
-19
lines changed

1 file changed

+19
-19
lines changed

articles/data-explorer/provision-aad-app.md

Lines changed: 19 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -9,11 +9,11 @@ ms.topic: conceptual
99
ms.date: 04/01/2020
1010
---
1111

12-
# Create an Azure Active Directory application registration
12+
# Create an Azure Active Directory application registration in Azure Data Explorer
1313

1414
Azure Active Directory (Azure AD) application authentication is used for applications, such as an unattended service or a scheduled flow, that need to access Azure Data Explorer without a user present. If you're connecting to an Azure Data Explorer database using an application, such as a web app, you should authenticate using service principal authentication. This article details how to create and register an Azure AD service principal and then authorize it to access an Azure Data Explorer database.
1515

16-
## Create Azure AD Application Registration
16+
## Create Azure AD application registration
1717

1818
Azure AD application authentication requires creating and registering an application with Azure AD.
1919
A service principal is automatically created when the application registration is created in an Azure AD tenant.
@@ -26,7 +26,7 @@ A service principal is automatically created when the application registration i
2626

2727
![Start a new app registration](media/provision-aad-app/create-app-reg-new-registration.png)
2828

29-
1. Fill in the following:
29+
1. Fill in the following information:
3030

3131
* **Name**
3232
* **Supported account types**
@@ -42,11 +42,11 @@ A service principal is automatically created when the application registration i
4242
> [!NOTE]
4343
> You'll need the application ID to authorize the service principal to access the database.
4444
45-
![Copy app registration id](media/provision-aad-app/create-app-reg-copy-applicationid.png)
45+
![Copy app registration ID](media/provision-aad-app/create-app-reg-copy-applicationid.png)
4646

4747
1. In the **Certificates & secrets** blade, select **New client secret**
4848

49-
![Initiate creation of client secret](media/provision-aad-app/create-app-reg-new-client-secret.png)
49+
![Start creation of client secret](media/provision-aad-app/create-app-reg-new-client-secret.png)
5050

5151
> [!TIP]
5252
> This article describes using a client secret for the application's credentials. You can also use an X509 certificate to authenticate your application. Select **Upload certificate** and follow the instructions to upload the public portion of the certificate.
@@ -55,10 +55,10 @@ A service principal is automatically created when the application registration i
5555

5656
![Enter client secret parameters](media/provision-aad-app/create-app-reg-enter-client-secret-details.png)
5757

58-
1. Copy the key value
58+
1. Copy the key value.
5959

6060
> [!NOTE]
61-
> When you leave this page, the key value won't be accessible. You will need the key to configure client credentials to the database.
61+
> When you leave this page, the key value won't be accessible. You'll need the key to configure client credentials to the database.
6262
6363
![Copy client secret key value](media/provision-aad-app/create-app-reg-copy-client-secret.png)
6464

@@ -71,11 +71,11 @@ If your application needs to access Azure Data Explorer using the credentials of
7171
1. In the **API permissions** blade, select **Add a permission**.
7272
1. Select **APIs my organization uses**. Search for and select **Azure Data Explorer**.
7373

74-
![Add Azure Data Explorer API permission](media/provision-aad-app/configure-delegated-add-api-permisions.png)
74+
![Add Azure Data Explorer API permission](media/provision-aad-app/configure-delegated-add-api-permissions.png)
7575

7676
1. In **Delegated permissions**, select the **user_impersonation** box and **Add permissions**
7777

78-
![Select delegated permissions with user impersonation](media/provision-aad-app/provisionaadapp-configuredelegated-click-add-permissions.png)
78+
![Select delegated permissions with user impersonation](media/provision-aad-app/configure-delegated-click-add-permissions.png)
7979

8080
## Grant the service principal access to an Azure Data Explorer database
8181

@@ -92,19 +92,19 @@ Now that your service principal application registration is created, you need to
9292
For example:
9393
9494
```kusto
95-
.add database Logs viewers ('aadapp=f778b387-ba15-437f-a69e-ed9c9225278b') 'Kusto App Registration'
95+
.add database Logs viewers ('aadapp=f778b387-ba15-437f-a69e-ed9c9225278b') 'Azure Data Explorer App Registration'
9696
```
9797
9898
The last parameter is a string that shows up as notes when you query the roles associated with a database.
9999
100100
> [!NOTE]
101101
> After creating the application registration, there may be a several minute delay until Azure Data Explorer can reference it. If you receive an error, that the application is not found, when executing this command, wait and try again.
102102
103-
For additional information see [security roles management](../security-roles.md) and [ingestion permissions](../../api/netfx/kusto-ingest-client-permissions.md).
103+
For additional information, see [security roles management](/azure/kusto/management/security-roles) and [ingestion permissions](azure/kusto/api/netfx/kusto-ingest-client-permissions.md).
104104
105-
## Using Application Credentials to Access a Database
105+
## Using application credentials to access a database
106106
107-
Use the application credentials to programmatically access your database by using the [Kusto client library](../../api/netfx/about-kusto-data.md).
107+
Use the application credentials to programmatically access your database by using the [Azure Data Explorer client library](azure/kusto/api/netfx/about-kusto-data.md).
108108
109109
```C#
110110
. . .
@@ -123,27 +123,27 @@ var queryResult = client.ExecuteQuery($"{query}");
123123
> [!NOTE]
124124
> Specify the application id and key of the application registration (service principal) created earlier.
125125
126-
> For more information, see [authenticate with AAD for Azure Data Explorer access](./how-to-authenticate-with-aad.md) and [use Azure Key Vault with .NET Core web app](/azure/key-vault/tutorial-net-create-vault-azure-web-app#create-a-net-core-web-app).
126+
> For more information, see [authenticate with AAD for Azure Data Explorer access](/azure/kusto/management/access-control/how-to-authenticate-with-aad) and [use Azure Key Vault with .NET Core web app](/azure/key-vault/tutorial-net-create-vault-azure-web-app#create-a-net-core-web-app).
127127
128128
## Troubleshooting
129129

130130
### Invalid resource error
131131

132-
If your application is used to authenticate users or applications for Kusto access, you must set up delegated permissions for Kusto service application, i.e. declare that your application can authenticate users or applications for Kusto access.
132+
If your application is used to authenticate users or applications for Azure Data Explorer access, you must set up delegated permissions for Azure Data Explorer service application. You must declare your application can authenticate users or applications for Azure Data Explorer access.
133133
Not doing so will result in an error similar to the following, when an authentication attempt is made:
134134

135135
`AADSTS650057: Invalid resource. The client has requested access to a resource which is not listed in the requested permissions in the client's application registration...`
136136

137-
You will need to follow the instructions on [setting up delegated permissions for Kusto service application](#set-up-delegated-permissions-for-kusto-service-application).
137+
You'll need to follow the instructions on [setting up delegated permissions for Azure Data Explorer service application](#configure-delegated-permissions-for-the-application-registration).
138138

139139
### Enable user consent error
140140

141-
Your AAD tenant administrator may enact a policy that prevents tenant users from giving consent to applications. This situation will result in an error similar to the following, when a user tries to login to your application:
141+
Your AAD tenant administrator may enact a policy that prevents tenant users from giving consent to applications. This situation will result in an error similar to the following, when a user tries to log in to your application:
142142

143143
`AADSTS65001: The user or administrator has not consented to use the application with ID '<App ID>' named 'App Name'`
144144

145-
You will need to contact your AAD administrator to grant consent for all users in the tenant, or enable user consent for your specific application.
145+
You'll need to contact your AAD administrator to grant consent for all users in the tenant, or enable user consent for your specific application.
146146

147147
## Next steps
148148

149-
* See [Kusto connection strings](../../api/connection-strings/kusto.md) for list of supported connection strings.
149+
* See [Kusto connection strings](/azure/kusto/api/connection-strings/kusto.md) for list of supported connection strings.

0 commit comments

Comments
 (0)