Overview
Turbo360 has four modules — Cost Analyzer, Business Applications, Business Activity Monitoring (BAM), and Azure Documenter — and they don't overlap. Each one addresses a specific operational problem. If you're new to Turbo360 and trying to figure out where to begin, or if you're evaluating which module your team should prioritize next, this guide walks you to the right answer.
Business value
Starting with the module that directly addresses your most pressing problem means your team sees value faster and builds internal support for the platform more quickly.
Start with the question you're actually trying to answer
"Our Azure bill keeps growing and I don't know why." → Cost Analyzer
Cost Analyzer gives you visibility into where Azure spend is going, helps you detect anomalies before they compound, and surfaces actionable optimization opportunities — schedules, rightsizing, reservations, and more. It connects directly to your Azure subscriptions and imports cost data, so you can start analyzing within minutes of setup.
Cost Analyzer is your module if:
- You need to understand and justify Azure spend to finance or leadership
- You want to automatically stop dev/test resources outside business hours
- You need to identify over-provisioned resources and rightsize them
- You want to model commitment-based discounts (reservations, savings plans)
- You're responsible for FinOps governance across multiple subscriptions
"When something breaks in our Azure integration environment, it takes too long to figure out which resource caused it." → Business Applications
Business Applications groups your Azure resources into logical units that map to the services and workflows your business runs — and monitors them as a cohesive solution rather than a collection of isolated infrastructure components. When an incident occurs, you see which service is affected, not just which resource.
Business Applications is your module if:
- You want a single view of health across the Azure resources that support a business service
- You need monitoring rules for availability, metric thresholds, API endpoint health, or Azure activity logs
- Your resources span multiple subscriptions or resource groups and you're tired of cross-checking them in the Azure portal
- You need automated operations — starting, stopping, or restarting resources — from one place
- You want your operations team to manage alerts and incidents without deep Azure portal knowledge
→ Business Applications quick start
"Support teams can't answer basic questions like 'where is my order?' without escalating to a developer." → BAM
Business Activity Monitoring (BAM) tracks individual business transactions as they move through your Azure integration services, stage by stage. It gives support teams and business users a searchable, real-time view of process execution — without log queries, without developer involvement, and with the ability to reprocess failed transactions directly from the interface.
BAM is your module if:
- Your integration platform processes business events (orders, payments, invoices, bookings) and you need transaction-level visibility
- First-line support teams are escalating routine "where is X?" questions to developers
- You need to track a message as it flows across multiple Azure services (Logic Apps, Service Bus, Functions, APIM)
- You need an audit trail of every transaction instance with its stage progression and tracked properties
- You want to reprocess failed transactions without custom retry code
"We spend hours manually compiling Azure documentation for audits, governance reviews, and architecture handovers." → Azure Documenter
Azure Documenter generates structured documentation of your Azure environment automatically — resource inventories, cost breakdowns, security compliance assessments, access reviews, rightsizing recommendations, and more. Documents are generated on demand or on a schedule and delivered as PDF, Word, or Excel, or published directly to Document360.
Azure Documenter is your module if:
- You need recurring documentation for governance, compliance, or architecture review purposes
- You produce regular reports for stakeholders who need Azure information in non-technical formats
- You want to surface rightsizing and reservation recommendations in a shareable report format
- You're responsible for audit documentation and want it to always reflect current state, not a snapshot from last quarter
- You're a managed service provider documenting multiple customer environments
→ Azure Documenter quick start
Quick reference
| My primary concern | Module to start with |
|---|---|
| Azure spend is too high or growing unexpectedly | Cost Analyzer |
| I can't tell which Azure resource is causing an incident | Business Applications |
| Support teams can't answer "where is my transaction?" | BAM |
| I spend too much time producing Azure documentation manually | Azure Documenter |
| I need to rightsize or schedule Azure resources | Cost Analyzer |
| I need to monitor Logic Apps, Service Bus, or Azure Functions as a group | Business Applications |
| I need to track orders, payments, or invoices end to end | BAM |
| I need a compliance or security report on my Azure environment | Azure Documenter |
Most teams eventually use more than one
The modules are complementary, not competitive. The most common combinations:
Cost Analyzer + Business Applications — cost governance paired with operational health monitoring. The most common starting combination for enterprises running production Azure workloads.
Business Applications + BAM — infrastructure health visibility paired with business process tracking. Use Business Applications to know when a resource is unhealthy; use BAM to know when a business transaction failed because of it.
All four — common for managed service providers and large enterprises where cost governance, operational monitoring, transaction tracking, and compliance documentation are all active requirements.