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.

Environment setup

  • 3 minute(s) read
Prev Next

Overview

Environment setup for the Data Queries (Pull Model) tracking type connects Turbo360 to your existing Azure data sources — Application Insights, Log Analytics, or Azure Data Explorer — so you can build business process tracking views from logs your integrations already produce. Unlike the Custom Logging type, no new infrastructure is deployed and no changes are required to your existing Azure workloads.

Business value

The Pull Model setup requires no changes to your existing Azure workloads. Once configured, Turbo360 can query your data sources directly and surface end-to-end transaction visibility without additional instrumentation in your integrations.

Prerequisites

Before you begin, confirm the following:

  • You have access to the Turbo360 portal.
  • Your Azure data sources (Application Insights, Log Analytics, or Azure Data Explorer) are already configured in Azure.

Required permissions

Permission Role required
Create a Business Process group BAM Owner
Configure a service principal Turbo360 Account owner

Dependencies

A service principal must be configured in Turbo360 with the Log Analytics Reader permission for Log Analytics, or with read access to the Application Insights resource you want to query. See Managing service principals in Pull Model for setup instructions.

How it works

The pull model setup creates a Business Process group with the Data Queries tracking type. During setup, you provide a service principal and define the subscription scope within which Turbo360 will discover data sources such as Application Insights, Log Analytics, and Azure Data Explorer. Turbo360 uses this configuration to resolve data sources when you later build business process queries.

Steps

Use the following steps to create a Business Process group using the Data Queries (pull model) tracking type. Navigate to Business Activity Monitoring in Turbo360 to get started.

  1. Select Data Queries as the tracking type and click Next.

  2. Enter a group name to organize your business processes within the group and click Next.

  3. Enter your service principal details and click Validate. Click Next once validation succeeds.

  4. Define the subscription scope within which Turbo360 will discover data sources. This controls which Application Insights, Azure Data Explorer, and Log Analytics resources are available when building queries.

  5. Click Create business process group.

The Business Process group is created with the Data Queries tracking type. You can now configure business processes and transactions within this group.

Example scenario

A team runs Logic App Standard workflows that emit traces to Application Insights. They create a BAM Business Process group with the Data Queries tracking type, provide a service principal with Application Insights read access, and scope the setup to the relevant subscription. After setup, they can build transaction queries against those Application Insights traces to track end-to-end order processing without modifying their Logic Apps.

Troubleshooting

  1. Service principal validation fails
    Cause: The service principal credentials are incorrect, expired, or the service principal does not have the required permissions on the target data source.
    Fix: Verify the client ID, client secret, and tenant ID. Confirm the service principal has at least Log Analytics Reader or Application Insights Reader access on the target resources. Re-validate after correcting the credentials.

  2. No data sources appear after setting the subscription scope
    Cause: The service principal does not have access to the selected subscription, or no supported data sources (Application Insights, Log Analytics, ADX) are deployed in that subscription.
    Fix: Confirm the service principal has Reader access at the subscription level. Verify that supported data sources exist within the scoped subscription in the Azure portal.

  3. Business Process group creation fails
    Cause: The group name may already be in use, or the service principal validation was not completed before attempting to create the group.
    Fix: Use a unique group name. Ensure the service principal validation step returns a success status before clicking Create business process group.

  4. Scope selection screen does not load
    Cause: The service principal provided does not have sufficient permissions to enumerate subscriptions, or a network issue is preventing the portal from reaching Azure.
    Fix: Verify the service principal has Reader access on at least one Azure subscription. Refresh the page and retry. If the issue persists, check your network connectivity and browser console for errors.

  5. Data Queries option is not visible during setup
    Cause: The Business Activity Monitoring feature may not be fully enabled for your organization, or your user role does not have permission to create Data Queries groups.
    Fix: Confirm that BAM is enabled under your Turbo360 subscription and that your account has the BAM Owner role. Contact your organization administrator if the option remains unavailable.

Related articles