Supported Azure resources

Prev Next

Overview

Turbo360 supports a broad set of Azure resource types for management and monitoring operations within Business Applications. Resources fall into two categories: top-level resource types and inner-level resource types.

Top-level resource types are the primary Azure services you associate directly with a Business Application. Inner-level resource types are child resources that exist within a parent resource. For example, queues and topics exist within a Service Bus namespace.

Business value

Knowing which resource types Turbo360 supports helps you plan your Business Application structure and ensures you can apply monitoring, dashboards, service maps, and automated tasks to the Azure services your workloads depend on.

How it works

Top-level resource types

Turbo360 supports the following Azure resource types for management and monitoring at the Business Application level:

Resource type
API App
APIM Management
Application Insight
App Registrations
App Service Certificate
Azure Function App
Cosmos Database
Data Factory
Enterprise Application
Event Grid
Event Grid Domain
Event Hub Namespace
Key Vault
Kubernetes Service
Log Analytics Workspace
Logic App
Power Automate Flow
Relay
Resource Graph Query
Runbook
Service Bus Namespace
SQL Database
Storage Account
Synapse Pipeline
Virtual Machine
Virtual Network Gateway
Web App

Inner-level resource types

Turbo360 also supports management and monitoring for the following inner-level resource types:

Inner-level resource type
APIM API
APIM Operation
APIM Product
Azure Functions
Cosmos SQL Container
Cosmos Table
Data Factory Pipeline
Data Factory Node
Event Grid Topic
Event Grid Subscription
Event Grid Domain Topic
Event Grid Domain Subscription
Hybrid Connection
Logic App Standard
Logic App Standard Workflow
Service Bus Queue
Service Bus Topic
Service Bus Topic Subscription
SQL Elastic Pool
Storage File
Storage Blob
Storage Table
Storage Queue
Web Job

Additional resource support

Turbo360 continues to expand management and monitoring capabilities beyond the resource types listed above. You can also add any Azure resource to a Business Application and configure monitoring rules and dashboards based on the available Azure metrics for that resource.

FAQs

  1. What is the difference between top-level and inner-level resource types?
    Top-level resource types are primary Azure services you associate directly with a Business Application . For example, a Service Bus Namespace or a Logic App. Inner-level resource types are child resources that exist within a parent. For example, Service Bus Queues and Topics exist inside a Service Bus Namespace.

  2. Can I add an Azure resource that is not in the supported list?
    Yes. You can add any Azure resource to a Business Application and configure monitoring rules and dashboards based on the Azure metrics available for that resource. Full management and monitoring feature coverage is only guaranteed for listed resource types.

  3. Which resource types support management operations such as Start, Stop, and Enable?
    Management operations are supported for a subset of the listed resource types. Refer to the Managing Business Applications article for the full compatible resource table.

  4. Are inner-level resource types counted separately in licensing?
    Yes. Each resource associated with a Business Application, whether top-level or inner-level, increases the licensing count by one. Adding the same resource to another Business Application does not increase the count again.

  5. Does Turbo360 add new supported resource types over time?
    Yes. Turbo360 continues to expand its supported resource list. Resources added after the list was last updated may appear under the All Resources tab when associating resources with a Business Application.

Related articles