When deploying a FortiGate-VM on public cloud, you determine the license type (PAYG or BYOL) during deployment. The license type is fixed for the VM's lifetime. The image that you use to deploy the FortiGate-VM on the public cloud marketplace predetermines the license type.
Migrating a FortiGate-VM instance from one license type to another requires a new deployment. You cannot simply switch license types on the same VM instance. However, you can migrate the configuration between two VMs running as different license types. There are also FortiOS feature differences between PAYG and BYOL license types. For example, a FortiGate-VM PAYG instance is packaged with Unified Threat Management protection and does not support VDOMs, whereas a FortiGate-VM BYOL instance supports greater protection levels and features depending on its contract.
- Connect to the FortiOS GUI or CLI and back up the configuration. See Configuration backups.
- Deploy a new FortiGate-VM instance with the desired license type. You can deploy the instance using one of the following methods:
- Azure marketplace
- Azure CLI
- Deploying FortiGate-VM using Azure PowerShell
- ARM templates
- Terraform templates
If deploying a BYOL instance, you must purchase a new license from a Fortinet reseller. You can apply the license after deployment via the FortiOS GUI or bootstrap the license and configuration during initial bootup using custom data as described in Bootstrapping the FortiGate CLI and BYOL license at initial bootup using user data.
- Restore the configuration on the FortiGate-VM instance that you deployed in step 2. As with the license, you can inject the configuration during initial bootup. Alternatively, you can restore the configuration in the FortiOS GUI as described in Configuration backups.
- If you deployed a PAYG instance in step 2, register the license. To receive support for a PAYG license, you must register the license as described in Creating a support account.