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.

Configuring private networking

  • 2 minute(s) read
Prev Next

Overview

This article describes how to configure private networking for a Turbo360 private hosted instance after the initial deployment. It covers the prerequisites, the end-to-end configuration process, and links to the detailed steps for each configuration task.

Business value

Private networking configuration locks down all application traffic to your Azure virtual network, preventing the web app, function apps, SQL database, and storage account from being accessible over the public internet. Completing this configuration is required for organizations with enterprise network security policies that prohibit public-facing PaaS resources.

How it works

Private networking is applied on top of an existing Turbo360 private hosting deployment. The configuration process involves stopping the application, attaching VNet integration and private endpoints to each infrastructure component, updating DNS entries, and restarting the apps. Once complete, all application traffic flows exclusively within your virtual network.

Prerequisites

Background reading

Design and setup

  • You have identified and created the subnets you want to connect the private endpoints to.

  • You have identified and created the subnet for VNet integration with your App Service outbound traffic. This subnet must have a delegation to Microsoft.Web/serverFarms.

Steps

Use the following steps to configure private networking on a deployed Turbo360 private instance. Complete Phase 1 before beginning Phase 2.

Phase 1: Standard Turbo360 private hosting deployment

Phase 1 confirms that the standard deployment is healthy before private networking is applied.

  1. Set up the deployment virtual machine and managed identity permissions as per the documentation.

  2. Deploy the Turbo360 application using the installer as described on the Deployment page.

  3. Verify that the application pages load correctly from the website.

Phase 2: Private networking configuration

Phase 2 applies VNet integration, private endpoints, DNS, and environment variable updates to isolate all application traffic within your virtual network.

  1. Stop the web application and function apps.

  2. If the storage account is V1, upgrade it to V2 to allow private endpoints (more info).

  3. Manually configure VNet integration on the App Service.

  4. Manually configure private endpoints for the SQL database.
    Note: this setting is on the logical server, not the individual database.

  5. Manually configure private endpoints for the storage accounts.

  6. Manually configure private endpoints for the App Service resources (function apps and web app).

  7. Manually configure private link for App Insights and Log Analytics.

  8. Add the DNS entries for the private endpoint resources.

  9. Update environment variables on the web app.

  10. Update environment variables on the function apps.

  11. Start all function apps.

  12. Start the web app.

  13. Open the Turbo360 page and verify the application is working.

Troubleshooting

If you encounter issues or want to perform sanity checks after completing the configuration steps, refer to the troubleshooting page. Common issues after private networking configuration include DNS resolution failures, connection timeouts due to missing private endpoints, and app startup failures caused by missing or incorrect environment variables.