Azure Data Explorer connector for Microsoft Power Automate

The Azure Data Explorer connector for Power Automate (previously Microsoft Flow) enables you to orchestrate and schedule flows, send notifications, and alerts, as part of a scheduled or triggered task.

You can:

• Send notifications and alerts based on query results, such as when thresholds exceed certain limits.
• Send regular, such as daily or weekly, reports containing tables and charts.
• Schedule regular jobs using control commands on clusters. For example, copy data from one table to another using the .set-or-append command.
• Export and import data between Azure Data Explorer and other databases.

For more information, see Azure Data Explorer Power Automate connector usage examples.

Create a new flow using the Azure Data Explorer connector

To use the connector, you must first add a trigger. You can define a trigger based on a recurring time period, or as a response to a previous flow action.

1. Sign in to Power Automate.

2. Create a new flow, or, from the Power Automate home page, select the My flows > + New flow.

   

3. Select Scheduled cloud flow.

   

4. In Build a scheduled cloud flow, enter the required information.

   

5. Select Create > + New step.

6. In the search box, enter Kusto or Azure Data Explorer, and select Azure Data Explorer.

   

7. Select an action from the list. For an explanation of each action and how to configure them, see Flow actions.

   Important

   You must have a valid Azure Data Explorer connection for your flow to run. For information about creating a connection, see Create an Azure Data Explorer connection in Power Automate.

   

Flow actions

When you select the Azure Data Explorer connector, you can choose one of the following actions to add to your flow:

• Run KQL query
• Run KQL query and render a chart
• Run async control command
• Run control command and render a chart
• Run show control command

This section describes the capabilities and parameters for each action and provides an example showing how to add an email action to any flow.

Run KQL query

Note

If your query starts with a dot, it's a control command. Use Run async control command.

Use this action to query the specified cluster. The actions that are added afterwards iterate over each line of the results of the query.

If the query takes more than 8 minutes to run, it will fail with a "RequestTimeout" exception. To prevent this issue, optimize your query or divide it into smaller parts. For more information, see Query best practices.

Example

The following flow triggers a query every minute. The query checks the number of records in the table, and then sends an email only if the number of records is greater than 0.

Run KQL query and render a chart

Note

If your query starts with a dot, it's a control command. Use Run control command and render a chart.

Use this action to visualize a KQL query result as a table or chart. For example, use this flow to receive daily reports by email.

If the query takes more than 8 minutes to run, it will fail with a "RequestTimeout" exception. To prevent this issue, optimize your query or divide it into smaller parts. For more information, see Query best practices.

Example

The following flow will present the query results as a timechart.

Run async control command

Use this action to run a control command asynchronously, which means it will continue to run in the background. The action returns an ID, state, and status. To check the status and details of an async command, use the .show operations command with the ID returned by this action.

If the async control command takes more than 60 minutes to run, it will fail with a "RequestTimeout" exception.

Example

The following flow triggers an async command to copy 10 records from the 'TransformedSysLogs' table to the 'TargetTable'. Note that the 'async' keyword is required in the query.

Run control command and render a chart

Use this action to run a control command and display the result as a chart. The chart options include an HTML table, pie chart, time chart, and bar chart.

If the control command takes more than 8 minutes to run, it will fail with a "RequestTimeout" exception.

Run show control command

This action runs the show control command and returns the result that can be used in the following connectors.

If the control command takes more than 8 minutes to run, it will fail with a "RequestTimeout" exception.

Example

The following flow runs the .show operation command to find the status of an async command using an operation ID returned by an async command execution.

Email Kusto query results

You can include a step in any flow to send reports by email, to any email address.

1. Select + New Step to add a new step to your flow.
2. In the search box, enter Office 365 and select Office 365 Outlook.
3. Select Send an email (V2).
4. Enter the email address to which you want the email report sent.
5. Enter the subject of the email.
6. Select Code view.
7. Place your cursor in the Body field, and select Add dynamic content.
8. Select BodyHtml.
9. Select Show advanced options.
10. Under Attachments Name -1, select Attachment Name.
11. Under Attachments Content, select Attachment Content.
12. If necessary, add more attachments.
13. If necessary, set the importance level.
14. Select Save.

Create an Azure Data Explorer connection

To run a flow that contains an Azure Data Explorer connector, you must use a valid Azure Data Explorer connection. You can create and authenticate a new connection from the Power Automate left pane, select Data > Connections or from within the flow, by selecting the Azure Data Explorer connector's menu > Add new connection.

The following steps show how to create a connection from within a flow.

1. In Run KQL query, select the three dots at the top right of the power automate connector.

   

2. Select Add new connection. When you connect for the first time, you're prompted to sign in to authenticate the connection.

   

Authentication

You can authenticate with user credentials or with an Azure Active Directory (Azure AD) application. To authenticate with credentials, select Sign in, and enter your credentials.

To authenticate with a Service Principal:

1. Select Connect with Service Principal.

2. Fill out the form with the following information:

   • Connection Name: A descriptive and meaningful name for the new connection. In this example, we've used "MyApplication".
   • Client ID: Your application ID.
   • Client Secret: Your application key.
   • Tenant: The ID of the Azure AD directory in which you created the application.

   Note

   Make sure your application is an Azure AD application and is authorized to run queries on your cluster.

   

   When authentication is complete, verify that your flow uses the new connection.

   

   Once the connection is set, the flow runs using the application credentials.

Test the flow

To check if your flow works, check the flow's run history:

1. Go to the Power Automate home page.

2. From the main menu, select My flows.

   

3. On the row of the flow you want to investigate, select the more commands icon, and then select Run history.

   

   All flow runs are listed, with information about start time, duration, and status.

   For full details about the flow, on My flows, select the flow you want to investigate.

   

To see why a run failed, select the run start time. The flow appears, and the step of the flow that failed is indicated by a red exclamation point. Expand the failed step to view its details. The Details pane on the right contains information about the failure so that you can troubleshoot it.

Limitations

• The maximum number of records per request is 50,000 and the maximum data size per request is 32 MB. These limits can't be changed.
• Synchronous requests have a timeout of 8 minutes.
• Asynchronous requests have a timeout of 60 minutes.
• The connector doesn't support operators that aren't supported by the getschema operator. For example, the fork, facet, and evaluate operators aren't supported.
• Flows work best on Microsoft Edge and Google Chrome.

Next steps

Learn about the Azure Kusto Logic App connector, which is another way to run Kusto queries and commands automatically, as part of a scheduled or triggered task.