Resources in Business Applications

Overview

In the context of Business Applications, a resource group refers to the collection of Azure resources associated with a single Business Application. This is distinct from an Azure resource group — an Azure resource group is a native Azure container tied to a subscription; a Business Application resource group is a Turbo360 concept that can draw resources from across multiple Azure subscriptions, regions, and native resource groups.

Understanding how resources are grouped within a Business Application is essential before configuring monitoring, dashboards, service maps, or automated tasks.

Business value

Grouping resources under a Business Application eliminates the need to track individual Azure services across subscriptions and portals. It gives operations teams a unified resource inventory for each solution, making it faster to identify gaps, apply monitoring rules, and act on alerts without context-switching between Azure portals.

How it works

Resource classification

When you associate resources with a Business Application, Turbo360 classifies them into two groups:

• Resources (Management & Monitoring) — feature-rich resource types that support both management operations and monitoring rules. These are the primary resource types for operational use.
• All Resources — a broader set that includes recently added resource types. Some of these support monitoring operations; management operations may be limited.

This classification determines which Turbo360 features are available for a given resource within the Business Application.

Cross-subscription association

A single Business Application can contain resources from multiple Azure subscriptions. Each subscription is accessed via a configured service principal. When adding resources, you select the service principal first, then choose the specific Azure resources from that subscription. You can repeat this process for as many subscriptions as needed.

Friendly names

Each resource in a Business Application can be assigned a friendly name — a display alias that replaces the original Azure resource name across all Turbo360 features, including Monitoring, Service Maps, Dashboards, and Automated Tasks. Friendly names help teams identify resources by function rather than by Azure naming conventions.

Friendly names must be unique within a Business Application to avoid confusion. They appear as tooltips alongside the original resource name when you hover over a resource.

Shared resources

A single Azure resource can be associated with more than one Business Application. This is useful when a shared service (such as a common Service Bus namespace) is used by multiple line-of-business solutions. The licensing count increments only once per unique resource — adding the same resource to a second Business Application does not increase the count again. The count decreases only when the resource is removed from all Business Applications it belongs to.

Azure tags

Azure tags (name/value pairs) can be assigned to resources within a Business Application. Tags let you categorise resources and support cost allocation and billing consolidation across resource groups and subscriptions. Tag values are case-sensitive.

Related articles

• Managing resources
• Supported Azure resources
• Automated resource association
• Understanding Business Applications
• Monitoring profiles