About Deployment Models

You can configure your FortiSandbox VM on Azure using either an Advanced or Basic deployment model. Before proceeding with deployment, please choose the right deployment model for your needs.

Choosing the Basic deployment model
Choosing the Advanced deployment model

Choosing the FortiSandbox VM Basic deployment model

The FortiSandbox Basic deployment model is the fastest and easiest way to deploy a FortiSandbox VM on Azure. Basic deployment takes advantage of the Azure Setup Wizard to guide you through the setup process with step-by-step instructions. Deployment takes approximately 10 minutes to complete.

Advantages:

Single Wizard page where you can enter all of the information required for launching a FortiSandbox VM.
Only simple information is required: resource group name, VM name, VM region, VM size, username, your SSH key or user password.
The setup wizard automatically creates and deploys the following resources: storage account, virtual network, network interface, public IP address, and the virtual machine instance.

Limitations:

The FortiSandbox VM is only created with one network interface.
- Some HA features require at least two network interfaces.*
- It is possible to add a second network interface, however, it requires a shutdown of the VM on the portal, followed by the manual creation and attaching of the new network interface.

Basic deployment can only support sandboxing analysis using Windows Cloud VMs.
Basic deployment models cannot run custom Windows VMs for analysis.

Choosing the FortiSandbox VM Advanced deployment model

To use advanced features of the FortiSandbox VM, including custom VMs and HA features, you can select the Advanced deployment model. Advanced deployment requires you to manually create all of the resources needed. It is recommended only for individuals with a good understanding of Azure and practical experience working with the cloud. Deployment takes approximately one hour to complete.

Advantages:

Gives you full control to customize the resources required to deploy the VM.
Advanced deployment supports the use custom Windows VMs.
Advanced deployment supports HA features.*

Limitations:

Requires advanced knowledge of deploying VMs in the Azure infrastructure.
The detailed guide must be followed carefully to ensure successful deployment.
All components must be deployed manually on the Azure portal.
Longer deployment times.

*Ha features: Currently, only clustering is supported on Azure. High Availability mode is not currently supported.

About Deployment Models

You can configure your FortiSandbox VM on Azure using either an Advanced or Basic deployment model. Before proceeding with deployment, please choose the right deployment model for your needs.

Choosing the FortiSandbox VM Basic deployment model

Advantages:

Single Wizard page where you can enter all of the information required for launching a FortiSandbox VM.

Only simple information is required: resource group name, VM name, VM region, VM size, username, your SSH key or user password.

The setup wizard automatically creates and deploys the following resources: storage account, virtual network, network interface, public IP address, and the virtual machine instance.

Limitations:

The FortiSandbox VM is only created with one network interface.

Some HA features require at least two network interfaces.*
It is possible to add a second network interface, however, it requires a shutdown of the VM on the portal, followed by the manual creation and attaching of the new network interface.

Basic deployment can only support sandboxing analysis using Windows Cloud VMs.

Basic deployment models cannot run custom Windows VMs for analysis.

Choosing the FortiSandbox VM Advanced deployment model

Advantages:

Gives you full control to customize the resources required to deploy the VM.

Advanced deployment supports the use custom Windows VMs.

Advanced deployment supports HA features.*

Limitations:

Requires advanced knowledge of deploying VMs in the Azure infrastructure.

The detailed guide must be followed carefully to ensure successful deployment.

All components must be deployed manually on the Azure portal.

Longer deployment times.

*Ha features: Currently, only clustering is supported on Azure. High Availability mode is not currently supported.