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.

Storage information

  • 3 minute(s) read
Prev Next

Overview

Business Activity Monitoring (BAM) uses an Azure Storage Account and an Azure SQL Database to persist tracked data. Understanding these infrastructure dependencies helps you configure the correct firewall rules, connection strings, and deployment settings before initiating a BAM environment.

Business value

Correctly associating a Storage Account and SQL Database ensures that tracked message headers, message bodies, and transaction data are stored reliably in your own Azure environment. This gives your team full control over data residency and access, and prevents tracking failures caused by misconfigured infrastructure.

Prerequisites

Before associating storage resources, ensure the following are in place:

  • An active Azure subscription with permissions to create or access SQL databases and storage accounts.
  • An Azure SQL Database with the connection string available.
  • An Azure Storage Account with the connection string available.
  • The Azure Function's IP address noted for firewall configuration.

Required permissions

You must be the Account Owner of the Turbo360 account to initiate BAM environment deployment.

How it works

Business Activity Monitoring uses two Azure resources to store tracking data:

  • Database in SQL Server — tracked transaction data is stored in an Azure SQL Database. Turbo360's backend APIs read this database to display tracking information in the Turbo360 application.
  • Storage Account — tracked message headers and message bodies are stored in blob containers within the associated Azure Storage Account.

When you provide connection strings for both resources and validate them successfully, BAM initiates deployment. After deployment completes, a sample business process, transaction, and transaction instances are provisioned automatically so you can verify the setup immediately.

Steps

Use the following steps to associate a Storage Account and SQL Database and initiate BAM environment deployment. Navigate to the BAM Getting started setup screen in the Turbo360 application to begin.

Configure Azure SQL Database firewall

Before connecting your SQL Database, configure firewall access so the Azure Function can write tracking data.

  1. Open the Azure SQL Server resource in the Azure application.
  2. Navigate to Firewall settings.
  3. Add the Azure Function's IP address to the list of allowed IPs.
  4. Enable Allow Azure services and resources to access this server.
Note:

Enabling Allow Azure services and resources is recommended as a best practice for Turbo360 Business Activity Monitoring to function correctly.

Associate storage resources and deploy

Associating both connection strings triggers BAM environment provisioning.

  1. In the BAM setup screen, enter the Azure SQL Database connection string in the SQL Database field.
  2. Enter the Azure Storage Account connection string in the Storage Account field.
  3. Click Validate to verify both connection strings.
  4. Once validation succeeds, click Initiate Deployment.

After deployment completes, the BAM environment is ready. A sample business process, transaction, and transaction instances are created automatically for verification purposes.

Troubleshooting

  1. Validation fails for the SQL Database connection string.
    Cause: The connection string is incorrect, or the Azure SQL Server firewall is blocking the request.
    Fix: Verify the connection string format and confirm the Azure Function's IP is added to the SQL Server firewall. Enable Allow Azure services and resources if not already enabled.

  2. Validation fails for the Storage Account connection string.
    Cause: The connection string is missing or contains an invalid key.
    Fix: Retrieve the connection string from the Access keys section of the Storage Account in the Azure application and re-enter it.

  3. Initiate Deployment button is unavailable after validation.
    Cause: One or both connection strings did not pass validation.
    Fix: Re-enter and revalidate both connection strings. Both must show a successful validation state before deployment can proceed.

  4. BAM environment was created but no sample data appears.
    Cause: Deployment completed but the sample business process provisioning is still in progress.
    Fix: Wait a few minutes and refresh the BAM application. If sample data still does not appear, verify that the Azure Function has network access to the SQL Database.

  5. Tracked data is not appearing in the application after deployment.
    Cause: The Azure Function cannot reach the SQL Database due to a firewall restriction added after initial setup.
    Fix: Return to the SQL Server firewall settings and confirm the Azure Function's IP is still in the allowed list.

Related articles