Overview
This article covers common issues encountered during Business Activity Monitoring (BAM) Push Model deployment. It addresses storage account configuration errors, ARM template failures, environment setup problems, and bring your own backend connectivity issues.
Business value
Resolving deployment failures quickly reduces the time between installation and a working BAM environment. This article helps you identify the root cause of common deployment errors without raising a support ticket.
FAQs
-
The ARM template deployment fails with a "StorageAccountAlreadyExists" error.
Cause: A storage account with the same name already exists in the target Azure subscription or region. Storage account names must be globally unique across all Azure tenants.
Fix: Open the ARM template parameters and provide a unique storage account name. Use a name that combines your organization prefix, environment label, and a short random suffix (for example,contosoprod7x3). Redeploy after updating the parameter. -
The ARM template deployment completes but the BAM environment fails the post-deployment verification check.
Cause: One or more required Azure resources (Service Bus namespace, storage queues, or function app) did not provision fully before the verification step ran. This typically occurs when Azure takes longer than expected to replicate the new resources.
Fix: Wait five minutes and re-run the deployment verification. Navigate to Deployment verification and follow the manual verification steps to confirm each resource is active. If a specific resource shows as missing, redeploy only the failed resource using the individual ARM template segment. -
The storage account is provisioned but BAM cannot write transaction data to it.
Cause: The function app's managed identity or service principal does not have the Storage Queue Data Contributor role on the storage account. Without this role, the function app cannot enqueue transaction messages.
Fix: In the Azure portal, open the storage account > Access control (IAM) > Add role assignment. Assign Storage Queue Data Contributor to the function app's managed identity. Allow up to two minutes for the role assignment to propagate, then retry a test transaction. -
The "Setting up the BAM environment" step fails with a connection string validation error.
Cause: The storage connection string entered during environment setup contains a trailing space or was copied with line-break characters from a text editor.
Fix: Copy the connection string directly from the Azure portal storage account under Access keys using the copy icon — do not type or paste from a secondary source. Re-enter the value in the Environment setup screen and save. -
The bring your own backend (BYOB) configuration cannot connect to the custom Azure Function endpoint.
Cause: The custom function app URL entered in the bring your own backend configuration is either incorrect or the function app is not running. BYOB connectivity requires the function app to be active and accessible from the Turbo360 service.
Fix: Verify the function app is running in the Azure portal. Confirm the URL follows the formathttps://<function-app-name>.azurewebsites.net/api/<function-name>. Test the endpoint directly in a browser or with a tool such as Postman before saving the BYOB configuration in Turbo360. If authentication is required, confirm the function app key is included in the URL as a query parameter. -
Global properties set during deployment are not visible in the BAM environment after setup completes.
Cause: Global properties are written to storage at deployment time. If the storage account was not fully active when the properties were written, the values may not have persisted.
Fix: Navigate to Global property management and re-enter the required properties manually. Save each property individually to confirm it persists across a page refresh.