Infrastructure requirements

Overview

This article lists the Azure infrastructure prerequisites for deploying Turbo360 as a private hosted instance. Review and prepare all requirements before running the Turbo360 installer to avoid provisioning failures or post-deployment configuration gaps.

Business value

Meeting infrastructure requirements before deployment eliminates mid-install failures caused by missing quotas, insufficient permissions, or unsupported resource configurations. This reduces deployment time and avoids repeated installer runs.

Prerequisites

• An active Azure subscription in a supported Azure environment (Global Cloud, China Cloud, or US Government)
• Access to create resource groups and assign IAM roles in the target subscription
• A service principal with Owner, User Access Administrator, or RBAC Administrator role, plus Contributor on the target resource group
• The Turbo360 installer tool, downloaded from the Turbo360 portal

Required permissions

The service principal used during deployment must hold at least one of the following roles at the subscription or resource group level:

• Owner
• User Access Administrator
• Role-Based Access Control (RBAC) Administrator

In addition, the service principal must have the Contributor role on the target resource group.

For Managed Identity authentication, a user-assigned Managed Identity must be created and associated with a Virtual Machine in the subscription before running the installer.

How it works

The Turbo360 installer provisions a fixed set of Azure resources into a single resource group in your subscription. All resources are created in the region you specify during installation. The installer validates connectivity and permissions before provisioning begins.

Resource authentication between components (web app to SQL, web app to storage) uses either connection string credentials or a user-assigned Managed Identity, depending on the authentication mode you select.

Configuration

Compute and hosting

Data and storage

Monitoring

BAM push model (additional requirements)

If you use Business Activity Monitoring (BAM) in push model mode, the following additional resources are required:

These resources are in addition to the core deployment. BAM pull model uses existing Log Analytics and Application Insights data sources and does not require additional infrastructure.

Managed Identity authentication (additional requirements)

Network requirements

See VNet configuration during deployment for VNET setup during installation.

Example scenario

A platform engineer preparing a private deployment verifies that the target subscription has sufficient quota for one Standard App Service Plan, three Function Apps, one Web App, one SQL database (S2), and one Storage Account in the West Europe region. They create a service principal with User Access Administrator and Contributor roles on the resource group, create a user-assigned Managed Identity and associate it with a Virtual Machine, then proceed to run the Turbo360 installer with Managed Identity authentication.

Limitations

• Deployment is supported only in Azure Global Cloud, Azure China Cloud, and Azure US Government. Other sovereign cloud or on-premises environments are not supported.
• Only one Turbo360 private instance can be deployed per resource group.
• VNET integration requires an App Service Plan at Premium tier or higher. Standard tier does not support private endpoints or outbound VNET routing.
• BAM push model requires additional Azure resources beyond the core deployment and must be planned for separately.
• Resource quotas are enforced at the subscription and region level. Insufficient quota causes deployment failures that the installer cannot resolve automatically.

Troubleshooting

1. Installer fails with a quota error during provisioning
   Cause: The target Azure subscription or region does not have sufficient quota for one or more resource types.
   Fix: In the Azure portal, navigate to Subscriptions > your subscription > Usage + quotas and request increases for App Service, SQL, or Storage as needed, then re-run the installer.

2. Service principal permission error during deployment
   Cause: The service principal is missing a required IAM role at the subscription or resource group level.
   Fix: Assign Owner, User Access Administrator, or RBAC Administrator to the service principal, and Contributor to the target resource group, then retry.

3. Managed Identity not recognised by the installer
   Cause: The user-assigned Managed Identity has not been associated with the Virtual Machine before running the installer.
   Fix: In the Azure portal, open the Virtual Machine > Security > Identity and assign the Managed Identity, then restart the installer.

4. VNET integration unavailable after deployment
   Cause: The App Service Plan was provisioned at Standard tier, which does not support VNET integration.
   Fix: Scale the App Service Plan to Premium tier in the Azure portal, then configure VNET integration. Contact Turbo360 support for assistance with post-deployment network configuration.

5. Outbound connectivity fails during deployment
   Cause: Network policies in the subscription block outbound internet access from App Service resources.
   Fix: Temporarily allow outbound access on ports 443 and 80 from the App Service subnet during deployment. Restrict access again after installation completes.

FAQs

1. Can I use pre-existing Azure resources instead of letting the installer create them?
   Yes. The installer supports supplying existing resource names. For Managed Identity deployments using pre-existing resources, the user-assigned Managed Identity must already be associated with the Function Apps and Web App before running the installer.

2. Is there a minimum SQL tier requirement?
   Yes. Azure SQL Standard S2 or higher is required. Lower tiers may not provide sufficient DTUs for Turbo360 data processing workloads, particularly when Cost Analyzer and BAM are both active.

3. Do I need to size the App Service Plan for expected load before deployment?
   The installer creates a Standard or Premium App Service Plan by default. You can scale the plan up or down after deployment based on observed usage. For production environments with multiple concurrent users, Premium P1v3 or higher is recommended.

Related articles

• Private hosting architecture
• Deployment
• VNet configuration during deployment
• Network configuration