You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/data-explorer/provision-aad-app.md
+19-19Lines changed: 19 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,11 +9,11 @@ ms.topic: conceptual
9
9
ms.date: 04/01/2020
10
10
---
11
11
12
-
# Create an Azure Active Directory application registration
12
+
# Create an Azure Active Directory application registration in Azure Data Explorer
13
13
14
14
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.
15
15
16
-
## Create Azure AD Application Registration
16
+
## Create Azure AD application registration
17
17
18
18
Azure AD application authentication requires creating and registering an application with Azure AD.
19
19
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
26
26
27
27

28
28
29
-
1. Fill in the following:
29
+
1. Fill in the following information:
30
30
31
31
***Name**
32
32
***Supported account types**
@@ -42,11 +42,11 @@ A service principal is automatically created when the application registration i
42
42
> [!NOTE]
43
43
> You'll need the application ID to authorize the service principal to access the database.
1. In the **Certificates & secrets** blade, select **New client secret**
48
48
49
-

49
+

50
50
51
51
> [!TIP]
52
52
> 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
.add database Logs viewers ('aadapp=f778b387-ba15-437f-a69e-ed9c9225278b') 'Azure Data Explorer App Registration'
96
96
```
97
97
98
98
The last parameter is a string that shows up as notes when you query the roles associated with a database.
99
99
100
100
> [!NOTE]
101
101
> 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.
102
102
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).
104
104
105
-
## Using Application Credentials to Access a Database
105
+
## Using application credentials to access a database
106
106
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).
108
108
109
109
```C#
110
110
. . .
@@ -123,27 +123,27 @@ var queryResult = client.ExecuteQuery($"{query}");
123
123
> [!NOTE]
124
124
> Specify the application id and key of the application registration (service principal) created earlier.
125
125
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).
127
127
128
128
## Troubleshooting
129
129
130
130
### Invalid resource error
131
131
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.
133
133
Not doing so will result in an error similar to the following, when an authentication attempt is made:
134
134
135
135
`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...`
136
136
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).
138
138
139
139
### Enable user consent error
140
140
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:
142
142
143
143
`AADSTS65001: The user or administrator has not consented to use the application with ID '<App ID>' named 'App Name'`
144
144
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.
146
146
147
147
## Next steps
148
148
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