Dear Handian Sudianto,
In Hyper-V, virtual NICs do not natively support trunk mode in the same way physical switches do. Instead, Hyper-V expects VLAN tagging to be handled at the VM level. For FortiGate VMs, this means the virtual NIC must be configured to pass untagged traffic, while VLAN tagging should be managed within the FortiGate OS itself.
To achieve this, please ensure the VLAN ID is not set in the VM settings, allowing the FortiGate to handle tagging internally. Additionally, confirm that the virtual switch is connected to a physical NIC operating in trunk mode and that the upstream switch allows the relevant VLANs.
If the interface inside FortiGate still fails to receive an IP address, we recommend verifying VLAN configuration on both the FortiGate and the physical switch, and ensuring DHCP is active for the VLAN in question.
I hope this helps. Just kindly tick Accept Answer that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.
Best regards,
Domic Vo