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.

Getting started FAQs

  • 3 minute(s) read
Prev Next

Overview

The BAM Pull Model queries your existing Azure data stores — Application Insights, Log Analytics, or Azure Data Explorer — to surface business process visibility without modifying your components. This article answers the most common questions teams have before and during initial setup.

Business value

Getting setup right from the start prevents the most common Pull Model failure modes — silent service principal errors, missing permissions, and scope gaps that cause tracking data to never arrive. This article answers the questions that most often block teams during their first Pull Model configuration.

How it works

This article covers questions across three areas: how the Pull Model differs from the Push Model, what permissions and infrastructure you need before starting, and what to expect once setup is complete.

FAQs

  1. What is the difference between the Pull Model and the Push Model in BAM?
    In the Pull Model, Turbo360 queries your existing Azure data stores — Application Insights, Log Analytics, or Azure Data Explorer — to retrieve transaction data. Your components do not need to be modified; they simply need to be logging to a supported data source. In the Push Model, your components actively send tracking events to the BAM API, which gives you explicit control over what gets tracked but requires instrumentation changes. Choose the Pull Model when your Azure components already log to a supported data source and you want business process visibility without touching existing workflows. See Understanding the Pull Model for a full comparison.

  2. Do I need to modify my existing Azure components to use the Pull Model?
    No. The Pull Model works with log data your components already produce. As long as your components write to Application Insights, Log Analytics, or Azure Data Explorer, Turbo360 can query that data without any instrumentation changes. The only prerequisite on the Azure side is that a supported data source exists and that a service principal has read access to it.

  3. Which Azure technologies and data sources are supported?
    The following pairings are supported:

    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

  4. What permissions do I need to set up the Pull Model?
    Two separate roles are required. You need the BAM Owner role in Turbo360 to create a Business Process group. You need the Turbo360 Account owner role to configure the service principal. If you hold one role but not the other, coordinate with an Account owner before starting setup. See Environment setup for the full prerequisites.

  5. What Azure permissions does the service principal need?
    The service principal requires Log Analytics Reader access for Log Analytics data sources, and read access to the Application Insights resource for Application Insights data sources. At minimum, the service principal also needs Reader access at the subscription level so Turbo360 can enumerate available resources during scope selection. See Managing service principals for full setup instructions.

  6. Can I use the same service principal for multiple Business Process groups?
    Yes. A single service principal can be scoped to multiple Business Process groups through the access policy configuration. You can also configure scope automation rules on the service principal to automatically extend access to new subscriptions that match a naming condition. Scope automation runs daily at 12:00 AM UTC.

  7. What happens if I select the wrong subscription scope during setup?
    The subscription scope controls which Application Insights, Log Analytics, and Azure Data Explorer resources are discoverable when you build business process queries. If you select the wrong scope, the target data sources will not appear during query configuration. You can update the scope by editing the service principal access policy after setup — no data is lost, but queries will not resolve until the correct subscription is in scope.

  8. How do I know when the Pull Model setup is complete and ready to use?
    Setup is complete after you click Create business process group and the group appears in the Business Activity Monitoring navigation. At that point you can create business processes and transactions within the group. To confirm the service principal and data source connections are working correctly, build a test transaction query and verify it returns results from the target data source. See Environment setup for the full setup walkthrough.

Related articles