Setting up your first business application

Overview

This tutorial walks you through creating your first Business Application in Turbo360 from start to finish. You will connect an Azure service principal, associate Azure resources, configure monitoring rules, and set up alerts, ending with a working Business Application that monitors your first set of Azure resources.

Business value

Business Applications give you a unified view of distributed Azure resources that form a single solution. Instead of logging into the Azure portal to check each resource individually, you can monitor health, receive alerts, and take action from one place in Turbo360; reducing mean time to detect and respond to issues.

Prerequisites

Before you begin, make sure you have:

• A Turbo360 account with an active organization
• An Azure subscription connected to Turbo360
• At least two Azure resources (for example, a Logic App and a Service Bus namespace) that you want to group under a single application

Required permissions

You must have the Account owner, Owner, or Contributor role in Turbo360 to create a Business Application.

How it works

Turbo360 provides a step-by-step wizard for creating a Business Application. The wizard walks you through seven stages in sequence: naming the application, adding a service principal, defining the subscription scope, selecting Azure resources, configuring monitoring rules, configuring alert settings, and reviewing a summary before creation. Once you complete all stages, Turbo360 provisions the Business Application and begins monitoring the associated resources.

Steps

This tutorial guides you from the Turbo360 home screen through each wizard stage to a fully configured, monitoring-enabled Business Application.

Step 1: Name the application and add a service principal

The name you enter identifies the Business Application across the Turbo360 portal, and the service principal provides Turbo360 with authenticated access to your Azure resources.

1. Go to the Turbo360 home screen and click Get Started in the Business Applications module.
2. Enter a descriptive Business Application Name that reflects the solution it represents (for example, Order Processing or Claims Pipeline).
3. Under Service Principal information, either add a new service principal or deselect Add new Service Principal and choose a previously configured service principal from another module.

Step 2: Define the subscription scope

Defining the scope determines which Azure subscriptions and resource groups the service principal can access. Narrowing the scope to specific resource groups is a security best practice.

1. Enable the checkbox next to a subscription to grant access to all resource groups within it.
2. Alternatively, expand the subscription and select specific resource groups to restrict scope to those resource groups only.
3. Click Next to continue.

Step 3: Select Azure resources

Selecting resources determines which Azure services are grouped under this Business Application and become available for monitoring and management.

1. Click a parent resource type to pre-load its child resource types.
2. Select the resources you want to associate. Use the Associate all the child resources of the selected resources checkbox to select all child resources at once.
3. Click Next to continue.

Step 4: Configure monitoring rules

Configuring monitoring rules in the wizard sets the initial health checks that Turbo360 will run against your associated resources. You can apply a reusable monitoring profile or configure rules individually.

1. In the Monitoring rules section, choose one of the following:
   • Apply a monitoring profile: select an existing profile to apply its pre-configured rules to all matching resource types.
   • Configure rules individually: set metric thresholds, state checks, or query rules per resource type.
   • Skip for now: proceed without configuring monitoring. You can add monitoring rules after the Business Application is created.
2. Click Next to continue.

Step 5: Configure alert settings

Alert settings control when Turbo360 notifies your team and how often it evaluates the monitoring rules. Configuring this correctly ensures violations reach the right people without excessive noise.

1. In the Monitoring alerts section, set the Notification schedule: the frequency at which Turbo360 evaluates and sends alert notifications (for example, every 15 minutes).
2. Add one or more alert recipients: email addresses or Microsoft Teams channel webhooks.
3. Configure the Status report schedule if you want periodic health summaries regardless of violations.
4. Click Next to continue.

Step 6: Review and create

Reviewing the summary is your final chance to confirm every setting before Turbo360 provisions the Business Application.

1. Review all details in the summary screen: name, service principal, scope, resources, monitoring rules, and alert settings.
2. Click Create Business Application to complete the process.

Turbo360 creates the Business Application and begins monitoring the associated resources. You are taken to the Business Application dashboard, where the health status of each resource populates after the first monitoring cycle completes.

Troubleshooting

1. The Get Started button is not visible on the home screen
   Cause: The Business Applications module is not enabled for your organization, or your role does not include access to it.
   Fix: Contact your Turbo360 administrator to verify that Business Applications is enabled and that your role includes access to the module.

2. Service principal authentication fails during setup
   Cause: The service principal credentials are incorrect, expired, or the service principal does not have the required permissions on the target subscription.
   Fix: Verify the client ID, client secret, and tenant ID. Confirm the service principal has at least Reader access on the subscription. See Service principal setup.

3. No resources appear when selecting Azure resources in step 3
   Cause: The service principal scope defined in step 2 does not include the subscriptions or resource groups where the target resources reside, or the resource types are not supported.
   Fix: Go back and verify the subscription scope. Confirm the resources are in a scoped subscription or resource group and that their resource type is supported.

4. The Business Application is created but shows no monitoring data
   Cause: Monitoring rules were skipped during setup, or the first monitoring cycle has not yet completed.
   Fix: Open the Business Application, navigate to Monitoring rules, and configure or apply a monitoring profile. Allow one full evaluation cycle to complete.

5. Create Business Application button is disabled on the summary screen
   Cause: One or more required fields are incomplete or contain validation errors.
   Fix: Review each wizard stage for missing or invalid input, particularly the service principal and resource selection stages. Correct any flagged fields before returning to the summary.

Related articles

• What are Business Applications?
• Service principal setup
• Supported Azure resources
• Monitoring a Business Application
• Configuring monitoring profiles