---
title: "Best practices"
slug: "private-hosting-best-practices"
updated: 2026-09-18T05:57:01Z
published: 2026-09-18T05:57:01Z
canonical: "docs.turbo360.com/private-hosting-best-practices"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.turbo360.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Best practices

## Overview

This article covers best practices for running a Turbo360 private hosted instance reliably in Microsoft Azure. It focuses on high availability configuration for the Azure services that underpin the private environment, and on custom domain setup for the web application.

### Business value

Because Turbo360 monitors and manages your Azure environment, keeping the private instance highly available is critical. Configuring the underlying Azure services for redundancy ensures that monitoring, alerting, and automation continue to operate even during zone-level or regional failures.

## High availability

The Turbo360 private instance runs entirely on Microsoft Azure. The following Azure services host the private environment:

- **App Service:** web apps and function apps
- **SQL:** primary data and configuration storage
- **Storage account:** application artifacts
- **Service Bus:** BAM event processing (if Business Activity Monitoring is enabled)

Each service has its own availability configuration, described below.

### 1. App Service

Web apps and function apps are hosted under a single App Service plan, as the private instance is a single-tenant application. To make the App Service plan highly available, use Azure's [Zone redundancy](https://docs.microsoft.com/en-us/azure/app-service/how-to-zone-redundancy) feature.

The Turbo360 App Service plan is created in the Standard tier by default. To enable Zone redundancy, you must deploy a new Premium-tier plan using an ARM template. The template format and deployment instructions are available [here](https://docs.microsoft.com/en-us/azure/app-service/how-to-zone-redundancy#how-to-deploy-a-zone-redundant-app-service).

Once configured, web apps and function apps remain accessible even if an Azure availability zone fails.

### 2. SQL

All Turbo360 data and configuration is stored in an Azure SQL database. Azure SQL includes a built-in [point-in-time restore and backup mechanism](https://docs.microsoft.com/en-us/azure/azure-sql/managed-instance/point-in-time-restore?tabs=azure-portal) that retains backups for the last 7 days.

For protection against zone-level failures, enable [geo-replication and failover](https://docs.microsoft.com/en-us/azure/azure-sql/database/active-geo-replication-configure-portal?tabs=portal) on the database.

### 3. Storage account

Turbo360 web app and function app artifacts are stored as blobs and files in an Azure Storage account. The storage account created by Turbo360 has [Geo-redundant storage (GRS)](https://docs.microsoft.com/en-us/azure/storage/common/storage-initiate-account-failover?tabs=azure-portal) enabled by default, which maintains availability in the event of a regional failure.

### 4. Service Bus

If you are using Business Activity Monitoring (BAM), a Service Bus namespace is deployed in your Azure subscription to transfer unprocessed event data between services.

Turbo360 deploys the Service Bus namespace in the Basic tier by default. To use [geo-recovery](https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-geo-dr?WT.mc_id=Portal-Microsoft_Azure_ServiceBus) for regional disaster protection, upgrade to the Premium tier.

## Custom domains

Azure Web Apps are provisioned with an auto-generated domain name by default. You can configure a [custom domain](https://docs.microsoft.com/en-us/azure/app-service/app-service-web-tutorial-custom-domain?tabs=cname) for the Turbo360 frontend web app to align with your organization's domain conventions.

## Related articles

- [License management](https://docs.turbo360.com/docs/private-hosting-license-management)
- [Upgrade](https://docs.turbo360.com/docs/upgrade)