Overview
This page is a starting point for all migration and upgrade scenarios in Turbo360. Use it to identify which guide applies to your situation and navigate to the detailed steps.
Turbo360 migration scenarios cover two situations: upgrading a privately hosted instance to a newer version, and migrating the authentication library used by a privately hosted instance.
Business value
Having a clear migration path reduces the risk of misconfiguration during upgrades, ensures breaking changes are applied in the correct order, and helps teams plan maintenance windows with confidence.
How it works
Each guide below describes what changes, who is affected, what prerequisite steps are needed, and where to find the full instructions. Review the summary for your scenario, confirm the prerequisites apply, then follow the link to the detailed guide.
Upgrade guides
Private hosting upgrade
Applies to: Organizations running Turbo360 on their own Azure infrastructure (privately hosted instances).
What it covers: Upgrading a privately hosted Turbo360 instance to a newer version using the Turbo360 installer. The guide includes the upgrade procedure, how to check for available versions from within the application, and a full record of breaking changes for every version that requires manual intervention before or after the installer runs.
Key breaking changes documented:
| Version | Change |
|---|---|
| 4.9.0 | All Function Apps must be set to 64-bit platform after upgrade |
| 4.2.0 | FUNCTIONS_WORKER_RUNTIME must be updated to dotnet-isolated on all Function Apps; Chart Generator requires an additional FUNCTIONS_EXTENSION_VERSION setting |
| 3.6.0 | New license model — license must be deactivated and reactivated once |
| 3.4.0 | Rebranding from Serverless360 to Turbo360 — WEBSITE_RUN_FROM_PACKAGE app setting must be updated |
| 2.0.0 | Single Web App architecture — backend Web App configuration must be copied to frontend Web App before upgrading |
| 1.7.0 | Function Apps must be manually upgraded to runtime version 4.x |
Prerequisites: Latest Turbo360 installer, access to Azure portal, SQL and Storage connection strings from the Web App environment variables. VNet-enabled instances must be upgraded from within the VNet.
See Upgrade for full steps.
Microsoft Entra ID authentication migration (ADAL to MSAL)
Applies to: Privately hosted Turbo360 instances upgrading from the ADAL-based version to the current MSAL-based version. SaaS-hosted customers are not affected.
What it covers: Turbo360 migrated its Microsoft Entra ID authentication integration from the deprecated ADAL (Azure Active Directory Authentication Library) to MSAL (Microsoft Authentication Library). This migration introduces a multi-tenant App Registration pattern — the same approach used by the SaaS version of Turbo360. The guide explains the new authentication architecture, why the change was made, and the two one-time setup steps required for privately hosted instances.
Two required setup steps:
- Turbo360 registers your privately hosted instance URL as a redirect URL on the Kovai multi-tenant App Registration. Contact Turbo360 support before the first login attempt on the upgraded instance.
- Your Turbo360 administrator grants API consent on first login. This is a one-time step that allows the application to retrieve users and groups from your Microsoft Entra ID tenant for RBAC configuration.
Prerequisites: Turbo360 administrator role, active Microsoft Entra ID tenant, the privately hosted instance already upgraded to the latest version, a user with Global Administrator or Application Administrator permissions on the Microsoft Entra ID tenant to complete the consent grant.
See Microsoft Entra ID authentication (ADAL to MSAL migration) for full steps.
Choosing the right guide
| Your situation | Guide |
|---|---|
| Upgrading a privately hosted Turbo360 instance to a newer version | Upgrade |
| Privately hosted instance failing after upgrade — login redirect error | Microsoft Entra ID authentication (ADAL to MSAL migration) |
| Switching authentication mode between email and Entra ID | Switch authentication mode |