Azure Monitor Logs connector for Logic Apps and Power Automate

Azure Logic Apps and Power Automate allow you to create automated workflows using hundreds of actions for a variety of services. The Azure Monitor Logs connector allows you to build workflows that retrieve data from a Log Analytics workspace or an Application Insights application in Azure Monitor. This article describes the actions included with the connector and provides a walkthrough to build a workflow using this data.

For example, you can create a logic app to use Azure Monitor log data in an email notification from Office 365, create a bug in Azure DevOps, or post a Slack message. You can trigger a workflow by a simple schedule or from some action in a connected service such as when a mail or a tweet is received.

Connector limits

The Azure Monitor Logs connector has these limits:

  • Max query response size ~16.7 MB MB (16 MiB). Connector infrastructure dictates that limit is set lower than query API limit
  • Max number of records: 500,000
  • Max query timeout 110 second
  • Chart visualizations could be available in Logs page and missing in the connector since the connector and Logs page don't use the same charting libraries currently

The connector may reach limits depending on the query you use and the size of the results. You can often avoid such cases by adjusting the flow recurrence to run more frequent on smaller time range, or aggregate data to reduce the results size. Frequent queries with lower intervals than 120 seconds aren’t recommended due to caching.


The following table describes the actions included with the Azure Monitor Logs connector. Both allow you to run a log query against a Log Analytics workspace or Application Insights application. The difference is in the way the data is returned.


The Azure Monitor Logs connector replaces the Azure Log Analytics connector and the Azure Application Insights connector. This connector provides the same functionality as the others and is the preferred method for running a query against a Log Analytics workspace or an Application Insights application.

Action Description
Run query and and list results Returns each row as its own object. Use this action when you want to work with each row separately in the rest of the workflow. The action is typically followed by a For each activity.
Run query and and visualize results Returns all rows in the result set as a single formatted object. Use this action when you want to use the result set together in the rest of the workflow, such as sending the results in a mail.


The following tutorials illustrate the use of the Azure Monitor connectors in Azure Logic Apps. You can perform these same example with Power Automate, the only difference being how to you create the initial workflow and run it when complete. Configuration of the workflow and actions is the same between both. See Create a flow from a template in Power Automate to get started.

Create a Logic App

Go to Logic Apps in the Azure portal and click Add. Select a Subscription, Resource group, and Region to store the new logic app and then give it a unique name. You can turn on Log Analytics setting to collect information about runtime data and events as described in Set up Azure Monitor logs and collect diagnostics data for Azure Logic Apps. This setting isn't required for using the Azure Monitor Logs connector.

Create logic app

Click Review + create and then Create. When the deployment is complete, click Go to resource to open the Logic Apps Designer.

Create a trigger for the logic app

Under Start with a common trigger, select Recurrence. This creates a logic app that automatically runs at a regular interval. In the Frequency box of the action, select Day and in the Interval box, enter 1 to run the workflow once per day.

Recurrence action

Walkthrough: Mail visualized results

The following tutorial shows you how to create a logic app that sends the results of an Azure Monitor log query by email.

Add Azure Monitor Logs action

Click + New step to add an action that runs after the recurrence action. Under Choose an action, type azure monitor and then select Azure Monitor Logs.

Azure Monitor Logs action

Click Azure Log Analytics – Run query and visualize results.

Screenshot of a new action being added to a step in the Logic App Designer. Azure Monitor Logs is highlighted under Choose an action.

Add Azure Monitor Logs action

Select the Subscription and Resource Group for your Log Analytics workspace. Select Log Analytics Workspace for the Resource Type and then select the workspace's name under Resource Name.

Add the following log query to the Query window.

| where EventLevelName == "Error" 
| where TimeGenerated > ago(1day)
| summarize TotalErrors=count() by Computer
| sort by Computer asc   

Select Set in query for the Time Range and HTML Table for the Chart Type.

Screenshot of the settings for the new Azure Monitor Logs action named Run query and visualize results.

The mail will be sent by the account associated with the current connection. You can specify another account by clicking on Change connection.

Add email action

Click + New step, and then click + Add an action. Under Choose an action, type outlook and then select Office 365 Outlook.

Select Outlook connector

Select Send an email (V2).

Office 365 Outlook selection window

Click anywhere in the Body box to open a Dynamic content window opens with values from the previous actions in the logic app. Select See more and then Body which is the results of the query in the Log Analytics action.

Select body

Specify the email address of a recipient in the To window and a subject for the email in Subject.

Mail action

Save and test your logic app

Click Save and then Run to perform a test run of the logic app.

Save and run

When the logic app completes, check the mail of the recipient that you specified. You should have received a mail with a body similar to the following:

Sample email

Next steps