---
title: "Understanding the Pull Model"
slug: "understanding-the-pull-model"
updated: 2026-10-29T11:13:41Z
published: 2026-10-29T11:13:41Z
canonical: "docs.turbo360.com/understanding-the-pull-model"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.turbo360.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Understanding the Pull Model

## Overview

The pull model is one of two deployment approaches in Business Activity Monitoring (BAM). In the pull model, your Azure services write logs to an existing data store — Application Insights, Log Analytics, or Azure Data Explorer — and Turbo360 queries that data store to retrieve and correlate those log messages into a business process view.

Unlike the push model, where your components actively send tracking events to the BAM API, the pull model works with log data your architecture already produces. No instrumentation changes are required as long as your components are logging to a supported data source.

### Business value

The pull model lets you build business process visibility on top of your existing Azure observability infrastructure. Teams running Logic Apps, Azure Functions, API Management, or Data Factory can create end-to-end transaction views without adding new instrumentation or modifying existing workflows. This significantly reduces the time to first insight and lowers the operational overhead of adopting BAM.

## How it works

Turbo360 connects to your data sources using a service principal that has read access to the relevant Azure resources. When you query transaction instances in BAM, Turbo360 executes queries against the configured data sources and correlates the results into a structured business process view.

The following data sources are supported:

- Application Insights
- Log Analytics
- Azure Data Explorer (ADX)

Any Azure component that logs to one of these data sources can participate in a pull model business process. The table below shows the common technology-to-data-source pairings:

| Technology | Supported data source |
| --- | --- |
| Logic App Standard | - Application Insights - Logic App Business Process Tracking from ADX |
| Logic App Consumption | - Log Analytics |
| Azure Functions | - Application Insights |
| API Management | - Application Insights |
| Data Factory | - Log Analytics |
| Custom code | - Application Insights - Custom logging to ADX via Event Hub |

The diagram below shows an example where a Logic App logs to Application Insights and Turbo360 queries either Application Insights or Log Analytics to retrieve the log data.

![](https://cdn.document360.io/a21734f9-5f67-4835-bb81-a488f8191fa8/Images/Documentation/image(967).png)

## Related articles

- [Environment setup](https://docs.turbo360.com/docs/environment-setup-pull-model)
- [Push Model vs Pull Model](https://docs.turbo360.com/docs/push-model-vs-pull-model)
- [Understanding the Push Model](https://docs.turbo360.com/docs/understanding-the-push-model)
- [Managing service principals](https://docs.turbo360.com/docs/managing-service-principals-in-pull-model)