Nested deployments

Starting in FortiSandbox version 4.4.4, only Nested BYOL deployments from the marketplace are supported. Please use the HyperV model image to upgrade going forward.

What is the difference between a nested and non-nested BYOL deployment?

A Nested BYOL Azure FortiSandbox will run guest VMs inside the appliance allowing for more control for those VMs. Nested BYOL also support more types of VMs, including the Default VM, Optional VM, Customized VM and Cloud VM.

A Non-Nested BYOL runs VMs outside the appliance. Non-nested BYOL and PAYG only support Customized VM and Cloud VM.

BYOL deployments before version 4.4.4

BYOL appliances deployed before version 4.4.4 are now referred to as Non-Nested BYOL. These appliances can still be upgraded with the Azure model image.

Deploying a nested BYOL

The deployment process for nested and non-nested BYOL are essentially the same with minor variations, specifically:

• Minimum system requirements
• Deploying FortiSandbox on Azure with the GUI
• Setting up the local VM
• Configuring a HA cluster

Any variations to the process are indicated within the deployment steps.