Overview
Before deploying and configuring Business Activity Monitoring (BAM) in Turbo360, ensure the requirements below are in place. Complete these steps before setting up the Business Activity Monitoring environment.
Business value
Meeting prerequisites before setup prevents deployment failures and reduces the time to your first tracked business transaction. A complete environment ensures that event ingestion, transaction tracking, monitoring, and alerting all function correctly from the start.
How it works
BAM in Turbo360 tracks business transactions across your Azure integration services by receiving event data from your applications and workflows. Before you can deploy BAM, Turbo360 requires an active Azure subscription, a service principal with the correct permissions, and appropriate Azure storage and backend resources for the deployment model you choose.
The prerequisites fall into three areas:
- Turbo360 account — you must have an active Turbo360 account with an organization set up
- Azure environment — your Azure subscription, service principal, and the storage or data resources required by your chosen deployment model must be in place
- Permissions — the service principal used to connect Turbo360 to Azure must be assigned the correct Azure RBAC roles
BAM supports two deployment models. Your prerequisite requirements depend on which model you use:
- Push Model (Custom Logging type) — your applications send events directly to the BAM API. Requires an Azure Storage Account for event storage and message archival.
- Pull Model (Data Queries type) — BAM queries your existing Azure data sources (for example, Application Insights, Log Analytics) on a schedule. Requires access to the data source and appropriate query permissions.
Prerequisites
Before you begin, ensure the following are in place.
Turbo360 account
- An active Turbo360 account.
- An organization configured in Turbo360.
Azure environment
- An active Azure subscription.
- Access to the Azure portal to configure service principal permissions and storage resources.
- An Azure Storage Account in your subscription for BAM backend storage (required for the Push Model; used by the BAM deployment for event ingestion and archival).
- For the Pull Model: access to the Azure data source you intend to query (for example, an Application Insights instance or a Log Analytics workspace).
Service principal
- A service principal (app registration) created in Azure Active Directory (Microsoft Entra ID) with a client secret or certificate.
- The service principal must be registered in Turbo360. See Service principal management.
Permissions
- You must have Owner or User Access Administrator rights on the Azure subscription to assign roles to the service principal.
- The service principal must be assigned the Contributor role on the Azure Storage Account used for BAM backend storage.
- For the Pull Model, the service principal must have Read access to the target data source (for example, Monitoring Reader on Application Insights or Log Analytics).
Required permissions
| Permission | Reason |
|---|---|
| Turbo360 Account owner/Contributor/ModuleOwner role | Required to deploy and configure BAM in Turbo360 |
| Azure Owner or User Access Administrator | Required to assign roles to the service principal on the subscription |
| Contributor role on the Azure Storage Account | Required for BAM backend storage (Push Model) |
| Read/Monitoring Reader on the target data source | Required for BAM data queries (Pull Model) |