BizTalk BAM to Turbo360 Migration

For numerous organisations, BizTalk Server has served as the cornerstone of enterprise integration for many years. One of its most powerful and often overlooked capabilities has been Business Activity Monitoring (BAM), which enables the definition, tracking, and visualisation of business processes in a manner that resonates with business users.

As customers transition and upgrade their integrations to Azure Integration Services (AIS) using Logic Apps, API Management, Functions, and Service Bus, a key query frequently arises: “How can we replicate BizTalk BAM in the cloud?”

Enter Turbo360 Business Activity Monitoring, the natural successor to BizTalk BAM. This solution is crafted for the cloud era, equipping System Integrators with the necessary tools to offer business visibility in modern architectures.

Why BizTalk BAM was Essential

BizTalk BAM was not merely a tool for developers; it functioned as a crucial link between IT and business. It empowered integrators to set milestones and data points within orchestrations, enabling business users to promptly answer questions such as:

• What is the total number of orders processed today?
• Which invoices failed validation?
• What is the current status of customer order #5742?

This level of transparency fostered trust and assurance in the integration platform. However, during the transition to Azure, many organisations discover that a direct equivalent is missing, and without meticulous planning, that vital visibility can be lost.

The Challenges of Azure Integration Services

Azure Integration Services delivers remarkable flexibility and scalability, but it is also inherently distributed. You may encounter the following components:

• A Logic App receiving messages
• An Azure Function performing transformations
• Service Bus managing queuing processes
• API Management directing calls
• Data Factory transferring data downstream

Each component logs telemetry to different storage locations (App Insights, Log Analytics, Azure Monitor), and this information is not presented in a user-friendly manner for business users.

This means the “business view” that BizTalk BAM offered, including insights into transactions, milestones, and outcomes, can disappear unless it is explicitly recreated.

Introducing Turbo360 BAM: The Cloud-Native Solution

Turbo360 Business Activity Monitoring was thoughtfully developed to bridge this gap. It offers BizTalk-like visibility, tailored for contemporary, serverless, and hybrid integration architectures.

Turbo360 BAM adopts the same principles of business observability, traceability, and user self-service, but eliminates the complications and overhead of traditional infrastructure.

Guiding System Integrators through Migration

As a System Integrator, your objective is to facilitate your customers’ modernisation journey confidently, ensuring they retain the business visibility they depended on in BizTalk.

Here’s a useful framework to follow:

Step 1: Identify Critical Business Processes

Collaborate with your customer to compile a list of key BizTalk orchestrations currently monitored by BAM (for example, order processing, invoicing, shipments).

Step 2: Extract Current BAM Definitions

Examine existing BAM activities and milestones, which will serve as the foundation for your Turbo360 tracking design.

Step 3: Map to Azure Integration Workflows

Correlate each process to its Azure counterpart (Logic Apps, Functions, Data Factory pipelines, etc.).

Step 4: Configure Turbo360 BAM

Establish business transactions and milestones within Turbo360. This often can be accomplished visually and without any coding.

Step 5: Validate End-to-End Visibility

Conduct sample transactions to ensure the business data and correlation are accurately captured.

Step 6: Deliver Self-Service Dashboards

Equip your customer’s business and operations teams with Turbo360 dashboards, enabling them to monitor and search independently.

Example: Migrating an “Order Processing” BAM Activity

In BizTalk:

• The orchestration tracked milestones: Order Received, Validated, Invoiced, Shipped.
• Business users accessed the BAM portal to check the order status.

In Azure:

• A Logic App receives and validates orders.
• A Function App manages invoicing.
• Service Bus handles shipping notifications.

With Turbo360 BAM, you can:

• Track the same milestones.
• Capture identical business data (Order ID, Customer Name, etc.).
• Provide the same (or improved) visibility through an intuitive web dashboard.

Result: Smooth continuity for the customer, paired with a more modern, scalable architecture.

Key Advantages for System Integrators

Implementing Turbo360 BAM alongside Azure Integration migration transforms a mere technical migration into genuine business modernisation.

Integrating BAM into Your Modernisation Strategy

When proposing a migration from BizTalk to Azure, positioning Turbo360 BAM as a component of your delivery framework illustrates that:

• You’re not just shifting code; you’re safeguarding business capabilities.
• You’re addressing the needs of business users, not solely those of IT.
• You’re assisting the organisation in transitioning to Azure without sacrificing visibility or confidence.

This strategic assurance is crucial for earning customer trust and fostering long-term partnerships.

Final Thoughts

BizTalk BAM instilled confidence within organisations, guaranteeing that their business processes remained visible and accountable.

As these organisations make the switch to Azure Integration Services, Turbo360 BAM ensures that visibility not only persists but also evolves.

For System Integrators, this means you can modernise more swiftly, deliver enhanced value, and provide your customers with what they truly desire: a clear, continuous insight into their business in action.