Overview
This glossary defines key terms used across Turbo360 and its modules: Cost Analyzer, Business Applications, Business Activity Monitoring (BAM), and Azure Documenter. Use this reference to understand terminology as it appears in the product UI and documentation.
Business value
A shared vocabulary reduces onboarding time and prevents misinterpretation of product concepts. This glossary is the authoritative reference for term definitions used across Turbo360 documentation.
Platform terms
Administrator/Account owner
The highest-privilege role in Turbo360. Admins can manage organization settings, user access, service principals, and all module configurations.
Azure subscription
A logical container in Microsoft Azure that holds resources and is associated with billing. Turbo360 connects to one or more subscriptions to retrieve cost, resource, and activity data.
Cost management group
(Cost Analyzer) A logical grouping of Azure resources or subscriptions used to aggregate and analyze cost data. Cost management groups reflect organizational units such as teams, products, or environments.
Import
(Cost Analyzer) The process by which Turbo360 retrieves cost and utilization data from Azure Cost Management and stores it for analysis. Imports can be triggered manually or run on a schedule.
Module
A functional area within Turbo360. The available modules are Cost Analyzer, Business Applications, Business Activity Monitoring, and Azure Documenter. Each module is independently enabled and configured.
Organization
The top-level entity in Turbo360 that contains all users, subscriptions, modules, and settings. An organization corresponds to a single Turbo360 account.
Role
A permission set assigned to a user or team that controls which actions they can perform within Turbo360. Roles are defined at the organization and module level.
Service principal
An Azure Active Directory identity used by Turbo360 to authenticate with Azure and access subscription data. Each connected subscription requires a service principal with the appropriate permissions.
Team
A group of users in Turbo360 used to manage shared access to modules, notifications, and escalation policies.
Cost Analyzer terms
Anomaly detection
A feature that monitors Azure spend and flags statistically significant deviations from expected patterns. Anomaly detection generates alerts when spend spikes or drops unexpectedly.
Budget
A spend threshold defined for a subscription, resource group, or cost group. When actual or forecasted spend approaches or exceeds the budget, Turbo360 generates an alert.
Budget planner
A tool in Cost Analyzer for creating, managing, and tracking budgets across subscriptions and cost groups.
Escalation policy
A rule that defines how and to whom an unacknowledged alert is escalated after a defined time window. Escalation policies apply to budgets, anomaly detection, and monitoring rules.
Forecasting
A Cost Analyzer feature that projects future Azure spend based on historical cost trends. Forecasts are displayed on the dashboard and can be included in reports.
Group budget
A budget applied at the cost group level rather than the subscription level. Group budgets aggregate spend across all resources assigned to a cost group.
Impact tracker
(Cost Analyzer > Optimization) A feature that tracks the financial impact of cost optimization actions taken on Azure resources, showing estimated versus actual savings over time.
Rightsizing
(Cost Analyzer > Optimization) The process of identifying and adjusting over-provisioned Azure resources to reduce cost without degrading performance. Rightsizing recommendations are generated based on historical utilization data.
Saved view
A named configuration of filters, groupings, and chart settings in Cost Analyzer that can be recalled and shared. Saved views allow teams to standardize how they analyze cost data.
Schedule automation
(Cost Analyzer > Optimization > Schedules) A feature that starts, stops, or deallocates Azure resources on a defined schedule to reduce spend during periods of inactivity.
Business Applications terms
Alert incident
A record in Business Applications that groups related alerts triggered by the same monitoring rule within a defined time window. Alert incidents reduce noise by consolidating repeated alerts.
Business Application
A logical grouping of Azure resources that represent a business workload or integration solution. Business Applications are the primary unit of monitoring in this module.
Business Application group
A collection of Business Applications organized for shared management, reporting, or escalation policy assignment.
Monitoring profile
A reusable configuration that defines monitoring rules, thresholds, and notification settings. Monitoring profiles can be applied to multiple Business Applications to enforce consistent alerting.
Monitoring rule
A condition defined in Business Applications or BAM that triggers an alert when a resource or transaction meets specified criteria (e.g., failure count, duration exceeded, query result threshold).
Resource dashboard
A dashboard view in Business Applications that displays the health and activity of Azure resources associated with a Business Application.
Service map
A visual representation of the Azure resources and dependencies that make up a Business Application. Service maps help teams understand the topology of an integration solution.
Business Activity Monitoring terms
BAM (Business Activity Monitoring)
A Turbo360 module for tracking, monitoring, and analyzing business processes and transactions flowing through Azure integration services.
Business process
(BAM) A named workflow in BAM that represents an end-to-end business operation, such as order processing or invoice approval. Business processes contain one or more business transactions.
Business transaction
(BAM) A trackable unit of work within a business process. Business transactions have defined stages and can be queried and reprocessed through the BAM interface.
Pull model
(BAM) A BAM deployment model in which Turbo360 queries Azure data sources (such as Application Insights or Storage) to retrieve tracking data on a schedule.
Push model
(BAM) A BAM deployment model in which external systems send tracking events directly to the BAM API. Custom connectors and API Management integrations are commonly used in the push model.
Reprocess
(BAM) The action of re-submitting a failed or stalled business transaction for re-execution. Reprocess configuration defines which transactions are eligible and how they are resubmitted.
Stage
(BAM) A defined checkpoint within a business transaction that represents a step in the business process. Stages are used to track progress and detect delays or failures.
Transaction instance
(BAM) A specific execution of a business transaction. Transaction instances can be queried, inspected, and acted on individually through the BAM tracking interface.
Azure Documenter terms
Diagram
(Azure Documenter) An auto-generated visual representation of Azure resources and their relationships within a subscription or resource group. Architecture diagrams are included in documents and can be configured independently.
Document
(Azure Documenter) A generated output that describes the Azure infrastructure of a subscription or resource group. Documents can include resource details, cost comparisons, security compliance summaries, and architecture diagrams.
Document group
(Azure Documenter) A collection of document configurations managed together. Document groups are used to organize and batch-generate documentation for multiple scopes.
Document type
(Azure Documenter) A category of content included in a generated document, such as Executive Summary, Resource Details, Billing Details, or Security Compliance.
Limitations
- This glossary covers terms used in the current version of Turbo360. Terminology may be updated as new features are released.
- Terms specific to Azure services (such as resource types, SKUs, and regions) are not defined here. Refer to the Microsoft Azure documentation for Azure-native terminology.
- Module-specific terms are accurate as of the current documentation version. Verify against the product UI if terminology appears to differ.