Overview
This article answers common questions about deploying and configuring the Business Activity Monitoring (BAM) Push Model. It covers storage requirements, backend options, environment configuration, and global property management.
Business value
Getting deployment right the first time avoids rework and delays in activating BAM for your organization. This FAQ collection addresses the questions most commonly raised during initial setup.
How it works
This article covers questions across four setup areas: storage account requirements, backend deployment options, environment configuration, and global properties. Questions progress from initial infrastructure decisions through to post-deployment configuration.
FAQs
-
What Azure storage account type does the Push Model require?
The Push Model requires a general-purpose v2 storage account. Blob Storage and Data Lake Storage Gen2 accounts are not supported. The storage account must be in the same Azure region as your BAM function app to minimize latency. See Storage information for the full list of requirements. -
Can I use an existing storage account, or do I need to create a new one?
You can use an existing general-purpose v2 storage account provided it does not already contain queue names that conflict with the BAM-required queues. BAM creates specific queues in the storage account during deployment. If those queue names already exist with incompatible message schemas, deployment will fail. To avoid this, Turbo360 recommends a dedicated storage account for BAM. See Storage management for details. -
What is the difference between the standard deployment and bring your own backend?
The standard deployment provisions a Turbo360-managed Azure Function app that handles BAM data ingestion and processing. Bring your own backend (BYOB) lets you deploy the BAM processing logic into a function app in your own Azure subscription, giving you full control over the infrastructure, networking, and data residency. BYOB is the recommended option when your organization has strict data residency requirements or network access restrictions that prevent the standard Turbo360-hosted function app from reaching your storage account. See Bring your own backend for setup instructions. -
How do I verify that the BAM environment was set up correctly after deployment?
Run the post-deployment verification steps described in Deployment verification. This checks that all required Azure resources are active, the storage queues were created, and the function app can write to and read from storage. If any check fails, the verification output identifies which resource needs attention. -
What are global properties and when should I configure them?
Global properties are key-value pairs that apply across all business processes and transactions in your BAM environment. They are typically used to store environment-level configuration values — such as a base URL, environment name, or shared reference code — that you want to reuse across multiple transactions without repeating them in each configuration. Configure global properties immediately after deployment so they are available when you define your first business process. See Global property management. -
Can I change the storage account after the BAM environment is live?
Yes, but it requires reconfiguring the BAM environment with the new connection string and redeploying the function app. Existing transaction data in the original storage account is not migrated automatically — it remains in the old account and will not be visible in BAM after the switch. Plan any storage account change during a maintenance window and export any historical transaction data you need to retain before making the change. -
What permissions does the BAM function app need on the storage account?
The function app requires the Storage Queue Data Contributor role to write incoming transaction messages to the queue, and Storage Blob Data Contributor if your configuration uses blob storage for payload archiving. Assign both roles to the function app's managed identity in the Azure portal under the storage account's Access control (IAM) settings. See Deployment details for the full permission requirements.