Setup FAQs
  • 05 Aug 2026
  • 4 Minutes to read
  • Dark
    Light
  • Download PDF

Setup FAQs

  • Dark
    Light
  • Download PDF

Article summary

Overview

This article answers common questions about setting up Turbo360 for the first time — including Azure subscription connection, service principal configuration, user provisioning, and initial module configuration. Use this article if you are an administrator completing an initial deployment or troubleshooting a setup that is not behaving as expected.

Business value

A smooth initial setup reduces time-to-value for your entire organization. Resolving common setup questions early prevents blocked onboarding and ensures that data, alerts, and modules are available when your team needs them.

Prerequisites

  • Account owner role in Turbo360.
  • Access to your organization's Azure subscription with sufficient permissions to create and configure a service principal.
  • Microsoft Azure portal access at https://portal.azure.com.

Required permissions

  • Connecting an Azure subscription: Account owner role in Turbo360 + Contributor or Owner role on the Azure subscription.
  • Service principal creation: Azure Active Directory application registration permissions (Application Administrator or Global Administrator in Azure AD).

Dependencies

  • An active Azure subscription
  • Turbo360 organization created and accessible

How it works

Turbo360 connects to Azure through a service principal — an Azure Active Directory application registration with a client secret or certificate. The service principal is granted scoped permissions on your Azure subscription, allowing Turbo360 to read cost, resource, and configuration data without requiring your personal Azure credentials. Once connected, modules become active and begin ingesting data from your subscription.

Steps

To complete initial setup:

  1. Sign in to Turbo360 as an Account owner.
  2. Navigate to Settings > Service principals.
  3. Follow the prompts to add a new service principal.
  4. Assign the required Azure roles to the service principal on the target subscription.
  5. Return to Turbo360 and validate the connection using the Validate option.
  6. Once validated, navigate to each module you have licensed and complete the module-specific initial configuration.
  7. Invite users and assign them to the appropriate modules and roles.

Configuration

SettingTypeDefaultRequiredDescription
Tenant IDTextYesAzure Active Directory tenant ID for your organization.
Client IDTextYesApplication (client) ID of the registered service principal.
Client secretSecretYesSecret value generated for the service principal. Stored encrypted.
Subscription IDTextYesAzure subscription ID to connect to Turbo360.
Service principal display nameTextService principal nameNoFriendly name shown in the Turbo360 portal for this service principal.

Permission behavior

With Account owner role: Full access to service principal configuration

With standard user role: Service principals page is not visible.

Example scenario

A platform engineer is setting up Turbo360 for a new Azure subscription her team manages. She signs in as Account owner, opens Settings > Service principals, registers a new service principal in Azure AD, assigns the Reader and Cost Management Reader roles on the subscription, and completes validation in Turbo360. She then opens Cost Analyzer, which immediately begins ingesting cost data. Within 24 hours, historical cost data is available on the dashboard.

Limitations

  • Service principal client secrets expire according to the expiry period set in Azure AD. Turbo360 does not automatically renew secrets — you must update them before expiry to avoid data ingestion interruptions.
  • Azure data ingestion is subject to Azure Cost Management export delays; cost data may lag by up to 24–48 hours from actual usage.

Troubleshooting

  1. The service principal validation fails with an authentication error.
    Verify that the Tenant ID, Client ID, and Client Secret entered in Turbo360 exactly match the values in the Azure portal for the registered application. Re-generate the client secret if it has been rotated or expired.

  2. No cost data appears in Cost Analyzer after connecting a subscription.
    Cost data ingestion can take up to 24 hours after the initial connection. If no data appears after 24 hours, confirm that the service principal has the Cost Management Reader role on the subscription, and that Cost Management exports are not blocked by an Azure policy.

  3. Users I invited have not received their invitation emails.
    Check that your organization's email server is not blocking mail from Turbo360's sending domain. Ask users to check spam and junk folders. Resend the invitation from Settings > Users.

  4. Module configuration is unavailable after service principal validation.
    Ensure your license includes the module you are trying to configure. Navigate to Settings > License consumption to confirm module entitlements. If the module is licensed but still unavailable, contact Turbo360 support.

FAQs

  1. How long does initial data ingestion take after connecting an Azure subscription?
    Cost and resource data typically appears within 24 hours of a successful subscription connection. Some historical data may take longer depending on the volume in your subscription.

  2. Can I connect multiple Azure subscriptions to a single Turbo360 organization?
    Yes. You can connect multiple Azure subscriptions to a single Turbo360 organization.

  3. Do I need to create a new service principal, or can I reuse an existing one?
    You can reuse an existing service principal provided it has the required Azure role assignments and an active client secret. Turbo360 does not require exclusive use of the service principal — it just needs valid credentials and scoped permissions.


Was this article helpful?