--- title: "Use cases" slug: "business-application-use-cases" updated: 2026-10-30T08:37:44Z published: 2026-10-30T08:37:44Z canonical: "docs.turbo360.com/business-application-use-cases" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.turbo360.com/llms.txt > Use this file to discover all available pages before exploring further. # Use cases ## Overview Business Applications supports a wide range of operational scenarios, from service-level health monitoring to Azure governance. This article describes the most common use cases across teams and roles. ### Business value - Understand which Business Applications capabilities apply to your role and responsibilities - Decide how to structure your Azure environment and monitoring strategy around business services - Connect service-level visibility to better operational outcomes ## How it works Business Applications groups the relevant Azure resources under a named business application, applies monitoring rules and escalation policies at the service level, and shows health and alert data in one view. Every use case below relies on the same core capability: resource grouping, monitoring, and alerting. What changes is how teams organize their business applications to reflect their operational domain. ## Use cases Business Applications is used across six primary use cases. Each one names the teams it suits, the problem it solves, and the key scenarios it covers. ### 1. E-commerce order processing ![business-applications-use-case-1-e-commerce-order-processing.png](https://cdn.document360.io/a21734f9-5f67-4835-bb81-a488f8191fa8/Images/Documentation/business-applications-use-case-1-e-commerce-order-processing.png) **Who it's for:** Operations teams, integration engineers, on-call engineers An e-commerce platform relies on a chain of Azure services: Logic Apps for order orchestration, Service Bus for message queuing, Azure Functions for payment processing, and API Management for storefront integration. Without Business Applications, a failure in any one of these resources raises an isolated alert that does not show the business impact. Key scenarios: - **Business-level grouping:** group all the order processing resources under a single "Order Processing" application - **Alerts in business context:** see a Service Bus queue delay as an Order Processing issue instead of an isolated resource alert - **Correct escalation:** trigger the right escalation path as soon as an alert fires ### 2. SaaS application health monitoring ![business-applications-use-case-2-saas-application-health.png](https://cdn.document360.io/a21734f9-5f67-4835-bb81-a488f8191fa8/Images/Documentation/business-applications-use-case-2-saas-application-health.png) **Who it's for:** Operations teams, platform engineers, account teams A software company hosts multiple tenants on Azure, each with its own Logic Apps, databases, and API endpoints. Monitoring each resource on its own makes it hard to assess the health of a specific tenant's service. Key scenarios: - **Tenant-level applications:** create one business application per tenant to keep each tenant's resources together - **Consistent coverage:** apply monitoring rules at the business application level so every tenant is monitored the same way - **Service-level health:** read health status for each tenant's service instead of each resource - **Incident communication:** respond to tenant-specific incidents and share status with account teams ### 3. Integration platform operations ![business-applications-use-case-3-integration-platform-operations.png](https://cdn.document360.io/a21734f9-5f67-4835-bb81-a488f8191fa8/Images/Documentation/business-applications-use-case-3-integration-platform-operations.png) **Who it's for:** Integration teams, on-call engineers, operations teams An enterprise integration team manages dozens of Logic Apps, Service Bus topics, and Event Grid subscriptions that connect internal systems and external partners. Tracking which integrations are healthy means correlating data across many individual resources. Key scenarios: - **Domain-based grouping:** group integrations into business applications by domain, for example "Finance Integration", "HR Sync", and "Partner Portal" - **Service-level view:** see the health of each integration domain without correlating individual resources - **Faster triage:** let on-call engineers see which business domain a failure affects without manual investigation ### 4. Business process continuity monitoring ![business-applications-use-case-4-business-process-continuity.png](https://cdn.document360.io/a21734f9-5f67-4835-bb81-a488f8191fa8/Images/Documentation/business-applications-use-case-4-business-process-continuity.png) **Who it's for:** Operations teams, process owners, on-call teams An operations team runs critical business processes on Azure, such as invoice approval, procurement workflows, and employee onboarding. Each process spans multiple Azure resources. When a process stalls, the team needs to know which step failed and which business process is affected. Key scenarios: - **Process-to-application mapping:** map each business process to a named application that contains its Azure resources - **SLA thresholds:** enforce SLA thresholds with monitoring rules - **Targeted escalation:** notify the right team through escalation policies when a process exceeds its expected duration or encounters an error ### 5. Multi-environment service management ![business-applications-use-case-5-multi-environment-service-management.png](https://cdn.document360.io/a21734f9-5f67-4835-bb81-a488f8191fa8/Images/Documentation/business-applications-use-case-5-multi-environment-service-management.png) **Who it's for:** Development teams, QA teams, operations teams A development team manages separate Azure environments for development, staging, and production. Each environment contains the same logical services but different resource instances. Key scenarios: - **Mirrored structure:** create parallel business applications for each environment so the service structure matches across them - **Cross-environment comparison:** compare health across environments - **Pre-promotion validation:** validate staging before promotion - **Incident isolation:** isolate production incidents from development activity ### 6. Azure resource governance and tagging compliance ![business-applications-use-case-6-governance-and-tagging-compliance.png](https://cdn.document360.io/a21734f9-5f67-4835-bb81-a488f8191fa8/Images/Documentation/business-applications-use-case-6-governance-and-tagging-compliance.png) **Who it's for:** Cloud administrators, governance teams, compliance teams An operations team responsible for Azure governance needs to verify that all resources supporting critical services are correctly tagged, monitored, and owned. Key scenarios: - **Service-level inventory:** review which resources belong to each business application - **Tagging and monitoring gaps:** identify untagged or unmonitored resources - **Ownership:** enforce ownership assignments for the resources behind each service - **Audit record:** maintain an auditable record of which resources support which services ## Related articles - [What are Business Applications?](https://docs.turbo360.com/docs/what-are-business-applications) - [Benefits](https://docs.turbo360.com/docs/business-application-benefits) - [Architecture](https://docs.turbo360.com/docs/business-applications-architecture) - [Business Applications quick start](https://docs.turbo360.com/docs/business-applications-quick-start) - [Managing Business Applications](https://docs.turbo360.com/docs/managing-business-applications) - [Managing resources](https://docs.turbo360.com/docs/managing-resources) - [Rules configuration](https://docs.turbo360.com/docs/monitor-rules-configuration) - [Managing escalation policies](https://docs.turbo360.com/docs/managing-escalation-policies-in-business-applications)