FortiGate VM64 Hyper-V

Deploy Fortinet FortiGate-VM security inside Microsoft Hyper-V infrastructure without introducing a separate physical firewall into every virtualized security boundary. Fortinet identifies Microsoft Hyper-V as a supported FortiGate-VM hypervisor, while its VM image naming uses the FG-VM64/FGT_VM64 family for x86-64 virtual deployments and the Hyper-V-specific HV designation. For Tanzania buyers, the practical purchasing question is not simply whether the image runs on Hyper-V; it is how the licensed FortiGate-VM tier, allocated compute, virtual switching, interfaces, inspection services, VPN load and resilience design fit the actual workload.

What is FortiGate VM64 Hyper-V?

FortiGate VM64 Hyper-V refers to the x86-64 FortiGate virtual appliance build for Microsoft Hyper-V. Fortinet documentation has used names such as FG-VM64-HV and FortiGate-VM64-HV for this platform. The virtual appliance runs FortiOS and allows security controls to be positioned within a virtual network architecture. This is useful when workloads live on Hyper-V hosts and traffic needs to be inspected between external networks, internal server networks, application tiers, management zones, branch VPNs or other defined trust boundaries.

The term VM64 should not be treated as a promise of one fixed commercial capacity. Fortinet’s current FortiGate-VM portfolio is licensed in tiers with different vCPU allowances and purchasing models. Current product material lists VM01, VM02, VM04, VM08, VM16, VM32 and unlimited tiers, while deployment image naming can still contain VM64. For procurement, FourTeck therefore recommends matching the current Fortinet license entitlement to the intended workload rather than assuming the filename itself defines the licensed performance tier.

A Hyper-V deployment also needs correct virtual networking. External, internal and private virtual switches, VLAN design, interface mapping and routing determine which traffic actually traverses the firewall. High availability introduces additional design requirements. Fortinet’s Hyper-V administration guidance documents FortiGate-VM HA and Live Migration scenarios, so organizations planning resilience should define host topology, heartbeat connectivity, virtual MAC behavior and migration requirements before production rollout.

FortiGate VM64 Hyper-V features and deployment value

Hyper-V deployment planning

Start by drawing the traffic flows that the firewall must control. Identify internet-facing networks, server VLANs, management networks, application tiers, backup networks and branch or remote-user connectivity. Each required security boundary should map cleanly to virtual switching and FortiGate interfaces. Avoid building a topology in which important traffic bypasses the firewall because two virtual machines share a switch or route that never crosses a FortiGate interface.

Compute allocation should follow the licensed FortiGate-VM tier and expected inspection workload. Internet bandwidth alone is not enough for sizing. Consider encrypted traffic, IPS, application control, web security, VPN concurrency, session counts, logging, routing and growth. The Hyper-V hosts themselves also need sufficient reserve capacity so a busy firewall VM is not starved by competing workloads.

For production deployments, document interface-to-vSwitch mappings, VLAN IDs, IP addressing, default routes, management access, DNS/NTP, administrative roles, backup procedures and upgrade plans. If high availability is required, design both FortiGate HA and the underlying Hyper-V host resilience as related but distinct layers. Test failover with realistic traffic before declaring the service production-ready.

Related FourTeck Tanzania solutions

A virtual firewall is only one layer of the infrastructure. Review FourTeck Tanzania integrated IT solutions for coordinated planning across security, servers and networking. The site’s firewall and VPN guidance explains why firewall sizing should include inspection and VPN demand; where an anchor cannot be preserved by WordPress, use the main Tanzania solution page as the verified destination. Hyper-V projects also depend on IT services and lifecycle planning, while the verified Tanzania contact page is the place to provide host, bandwidth, VPN and licensing requirements. Buyers with cross-border requirements can also reference FourTeck Uganda, FourTeck Kenya, FourTeck UAE, FourTeck Ghana and FourTeck Nigeria when coordinating regional technology standards.

FortiGate VM64 Hyper-V Tanzania

Organizations evaluating FortiGate VM64 Hyper-V in Tanzania commonly have one of three starting points: an established Microsoft virtualization estate that needs stronger network segmentation, a server-consolidation project where security should remain virtual, or a branch/data-centre design that needs VPN and policy enforcement without adding another physical appliance for each logical boundary. In all three cases, begin with architecture rather than a license code. Record the Hyper-V version, host CPU and memory resources, number of hosts, virtual switches, VLANs, internet circuits, internal networks and workloads that need protection.

For a Tanzanian business running ERP, file services, databases, web applications or directory services as VMs, FortiGate-VM can become a controlled gateway between server segments and user networks. The design can also separate management traffic from production workloads. This is particularly useful when administrators want explicit policy between application tiers instead of relying only on broad LAN trust. The value comes from traffic actually traversing the virtual firewall, so routing and virtual-switch design must be validated carefully.

Procurement teams should request a quotation with the intended security services, approximate inspected throughput, VPN requirements and expected growth. Ask for the current Fortinet VM licensing option rather than assuming an older VM64 license description remains commercially current. If subscriptions are required for the selected security services, include their term and renewal plan in total-cost evaluation. Also specify whether centralized logging or management is part of the project.

For deployment, include a rollback plan and configuration backup. Test management access, DNS, time synchronization, routing, NAT, security policies, VPNs and logging before migrating critical traffic. Tanzania deployments with multiple offices can use the virtual firewall as part of a repeatable branch-security standard, but each site may still need different bandwidth, redundancy and local access design. FourTeck Tanzania can use these inputs to prepare a more meaningful product and implementation discussion rather than quoting from the model name alone.

FortiGate VM64 Hyper-V Dar es Salaam

Dar es Salaam organizations often operate the largest concentration of users, servers and internet-facing services within a Tanzanian business. A Hyper-V cluster in a head office or data-centre environment may host finance systems, line-of-business applications, identity services and shared infrastructure. FortiGate VM64 Hyper-V can be positioned so those virtual workloads are separated from user, guest, management and external networks by explicit FortiOS policies.

A useful design workshop should map which applications communicate, which services need inbound publication and which administrators require management access. This avoids creating a firewall rule base that simply allows broad network-to-network access. Where dual internet links are available, routing and failover objectives should be documented separately from server-network segmentation. If remote branches connect to Dar es Salaam, include tunnel count, expected traffic and business-critical applications in sizing.

Hyper-V resilience also deserves attention. If workloads move between hosts, confirm how the firewall placement and virtual networking continue to preserve the intended traffic path. Fortinet documents HA and Live Migration scenarios for Hyper-V, but the production design should be validated against the organization’s exact FortiOS release and Microsoft environment. Maintenance windows should include controlled failover tests rather than assuming virtualization alone makes the security layer highly available.

For a Dar es Salaam quotation, provide host details, network diagrams if available, ISP bandwidth, number of protected VLANs, VPN requirements, desired security services and whether migration from a physical or different virtual firewall is involved. This allows the conversation to cover licensing, deployment and cutover instead of treating FortiGate-VM as an isolated software purchase.

FortiGate VM64 Hyper-V Mwanza

For Mwanza businesses, FortiGate VM64 Hyper-V can suit a regional server environment where Microsoft virtualization already consolidates business applications. The first design question is whether the firewall will protect internet access, internal server zones, branch VPN traffic, or all three. Those roles produce different interface, routing and availability requirements. A compact virtual environment may need only a few clearly defined zones, while a regional hub can require separate networks for users, servers, management, backups and public services.

When connectivity is operationally important, plan for what happens during an ISP interruption and during a Hyper-V host maintenance event. A second internet path does not automatically provide application continuity; routes, health checks, NAT and VPN behavior must be designed. Likewise, a second virtualization host does not automatically preserve firewall service unless the VM placement, storage, switching and FortiGate availability design support the intended recovery process.

Sizing should reflect enabled inspection. If the environment will use IPS, application controls, encrypted traffic inspection or substantial VPN traffic, include these workloads in the requirement. Avoid selecting a license tier only from raw link speed. A security gateway that performs well during ordinary browsing can face very different demand during backups, software updates, remote-access peaks or inter-site replication.

Mwanza procurement requests are more actionable when they include the number of Hyper-V hosts, current firewall model if any, internet capacity, server VLANs, approximate users, remote sites and desired subscription term. With those details, FourTeck can help frame a FortiGate-VM requirement that fits the existing virtual infrastructure and leaves a documented path for expansion.

FortiGate VM64 Hyper-V Arusha

Arusha organizations in hospitality, professional services, education and multi-site operations may use Hyper-V to consolidate local applications while depending heavily on cloud and remote connectivity. FortiGate VM64 Hyper-V provides a way to enforce policy close to those virtual workloads. A sound design can isolate administrative systems from guest or general-user networks and create controlled paths for services that must communicate across zones.

For environments serving visitors or multiple business units, segmentation should be intentional. Guest traffic should not inherit access to server networks simply because it shares physical switching infrastructure. Hyper-V virtual switches and VLANs can feed distinct FortiGate interfaces or logical zones, with FortiOS policies determining permitted flows. Document exceptions so future administrators understand why access exists.

Remote support and branch connectivity are also common considerations. Define whether VPN users need full network access or only selected applications, and whether branch tunnels should reach every server subnet. Least-privilege routing and policy can reduce unnecessary exposure. If the business operates around the clock, plan upgrades, backups and failover so security maintenance does not become an unexpected outage.

An Arusha buyer should include business-critical applications, operating hours, internet links, current Hyper-V topology, remote users and branch count in the quotation request. Where the environment has seasonal peaks, estimate the higher usage period rather than the quietest month. This produces better sizing and a clearer licensing discussion for FortiGate-VM security services.

FortiGate VM64 Hyper-V Dodoma

Dodoma deployments may involve administrative offices, institutions, enterprises and service organizations that need controlled access to virtualized applications. FortiGate VM64 Hyper-V can provide a policy boundary within Microsoft Hyper-V, but successful deployment depends on understanding which systems are critical and which network paths must remain available during maintenance or failure.

Start with an application dependency map. Identity, DNS, databases, application servers and management tools often communicate in ways that are not obvious from a simple VLAN diagram. Before enforcing tighter segmentation, capture those dependencies and convert them into deliberate firewall policies. This makes the security posture more maintainable than adding broad temporary rules after cutover.

Where sensitive administrative workloads are involved, management access deserves a dedicated plan. Restrict the FortiGate administrative interface to approved networks, use appropriate administrator roles and maintain configuration backups. Logging should be sized and retained according to operational and organizational requirements. If a separate FortiAnalyzer or other logging destination is planned, include connectivity and storage expectations in the architecture.

For procurement in Dodoma, provide the intended FortiOS features, Hyper-V host count, virtual network layout, bandwidth, VPN needs and availability target. FourTeck can then discuss the current licensing path and deployment scope without making assumptions about capacity from the VM64 label alone. A well-defined requirement also helps distinguish a straightforward VM license purchase from a larger migration and security-policy project.

FortiGate VM64 Hyper-V UAE

UAE organizations using Microsoft Hyper-V can apply the same FortiGate-VM architecture principles across private-cloud, data-centre and branch environments. For companies that also operate in Tanzania, a common FortiOS policy framework can simplify administration, but regional sites should still be sized for their own internet capacity, workloads and availability needs. Standardization should define naming, security zones, logging and change control rather than force identical resource allocations everywhere.

Data-centre deployments may require multiple virtual networks and strict separation between production, development, management and externally published services. Map each flow before creating policies. If workloads are migrated between Hyper-V hosts, verify that the destination host has equivalent virtual switching and that the firewall architecture continues to enforce the same path. High availability should be tested during both firewall and host-level events.

Licensing deserves current vendor confirmation because Fortinet’s commercial VM tiers and subscription options evolve independently from the VM64 image naming convention. Define the number of vCPUs intended for the licensed tier, security subscriptions, management and logging requirements, and support term. For multi-country procurement, maintain an entitlement inventory so renewals and VM registrations remain traceable.

Organizations coordinating UAE and Tanzania infrastructure can use FourTeck’s regional network to align architecture discussions while keeping each deployment’s technical bill of materials specific. The goal is consistent security operations: documented interfaces, predictable policy naming, controlled VPN design, tested backups and an upgrade process that administrators can repeat across sites.

FortiGate VM64 Hyper-V Uganda

Uganda businesses with centralized Hyper-V infrastructure can deploy FortiGate-VM to secure virtual servers, internet paths and branch connectivity. For organizations linked to Tanzanian operations, the virtual format can support a repeatable firewall design without requiring identical physical appliances at every virtualized hub. The critical requirement is to keep licensing and topology aligned with each site’s actual demand.

Before procurement, identify protected networks and the expected traffic between them. A server environment with several application tiers can benefit from explicit segmentation, while a simpler office may primarily need a secure internet gateway and VPN termination. These use cases should not be sized from the same checklist. VPN encryption, inspection services and session patterns can materially affect compute demand.

Availability planning should include the Hyper-V layer, storage and switching. If the FortiGate VM is a critical path for server access, document how service is restored if a host fails. Organizations using clustering or migration should validate the supported Fortinet and Microsoft design for their software versions. Back up the FortiGate configuration before major changes and test restore procedures.

A Uganda quotation request should specify host resources, FortiOS version target if constrained by standards, security services, internet bandwidth, VPN count and support term. This information makes it possible to discuss an appropriate current FortiGate-VM tier rather than treating FG-VM64-HV as a fixed performance appliance.

FortiGate VM64 Hyper-V Kampala

Kampala offices and data-centre environments may host a dense mix of business applications on Hyper-V. FortiGate VM64 Hyper-V can provide security policy between these workloads and user, internet, partner or branch networks. The architecture is particularly useful when a business wants security boundaries to follow virtual infrastructure rather than hairpinning every flow through distant physical equipment.

Design the virtual switches with clear purpose. Label external, server, management and other networks consistently, and map FortiGate interfaces so troubleshooting is straightforward. Where VLAN trunks are used, document allowed VLANs and the corresponding FortiOS interfaces. Misaligned switch and firewall configuration can create bypass paths or outages that are difficult to diagnose.

Kampala environments with many remote users should quantify concurrent VPN use and the applications carried through tunnels. Video, file transfer and database access create different traffic profiles. If branch connectivity is important, include failover expectations and routing behavior when an ISP link changes. Logging and monitoring should provide enough visibility to confirm that the intended path is being used.

For procurement, send the network diagram, bandwidth, VM host specifications and desired Fortinet security services where available. If these are not yet documented, start with user count, server count, branches and critical applications. FourTeck can then help turn operational requirements into a clearer licensing and deployment scope.

FortiGate VM64 Hyper-V Arua

Arua deployments may prioritize efficient use of existing server infrastructure and dependable branch connectivity. When Hyper-V already hosts local applications, FortiGate VM64 Hyper-V can add a virtual security boundary without requiring a separate physical firewall for each internal zone. This can be useful for separating servers, administration and user networks while keeping the design within the virtualization platform.

Connectivity resilience should be based on realistic local options. If only one primary circuit is available, document recovery procedures and prioritize critical services. If multiple links exist, define whether the requirement is failover, load distribution or policy-based use. VPN tunnels may need to re-establish across alternate paths, so test behavior rather than assuming automatic continuity.

Resource planning should leave headroom on the Hyper-V host. Security inspection is a production workload and should not compete unpredictably with application VMs. Monitor CPU, memory and network utilization after deployment and compare it with peak periods. If growth is expected, choose a licensing and infrastructure path that can accommodate planned expansion.

For an Arua quotation, include the number of sites, protected servers, internet links, VPN users and security functions required. This allows a current FortiGate-VM entitlement to be matched to the environment while avoiding unsupported assumptions about stock, throughput or licensing based only on the VM64 name.

FortiGate VM64 Hyper-V Mbarara

Mbarara organizations can use FortiGate VM64 Hyper-V where Microsoft virtualization supports business applications and network security needs to be integrated into that environment. A typical design might place server workloads behind the virtual firewall, separate management access and establish secure tunnels to headquarters or cloud-connected services.

The best deployment begins with traffic classification. Identify which systems require unrestricted outbound access, which should be tightly limited and which need inbound connections. Use that map to build policies with clear names and purposes. Avoid creating broad rules simply to accelerate migration; temporary exceptions often become permanent and make later audits harder.

If the site relies on VPN to reach central applications, include tunnel traffic in sizing and resilience planning. Determine what happens when the WAN changes, the firewall reboots or a Hyper-V host is serviced. Configuration backups and documented recovery steps are especially important where specialist assistance may not be immediately on site.

Mbarara buyers should request licensing guidance with the planned vCPU allocation, FortiGuard security requirements, support period and expected growth. The quotation should distinguish software entitlement from implementation work such as migration, policy creation, VPN setup, testing and documentation. This makes project scope easier to compare and approve.

FortiGate VM64 Hyper-V Gulu

Gulu sites using Hyper-V can deploy FortiGate-VM as a virtual firewall for local server protection, internet security and inter-site connectivity. The virtual appliance approach can be attractive when rack space is limited or when the organization already operates a standardized virtualization platform. It still requires disciplined network design; virtualization does not remove the need for clear physical uplinks, VLANs and security zones.

For smaller environments, keep the topology understandable. Separate only where there is a meaningful trust or operational boundary, and document why each zone exists. For larger sites, plan naming and addressing so additional networks can be introduced without rewriting the entire policy base. Consistency is especially valuable when a central IT team supports several locations.

Power and host availability should also be considered. A virtual firewall depends on the server, storage and network interfaces beneath it. UPS coverage, host monitoring and backup procedures therefore become part of firewall availability. If the environment needs continuous service, evaluate HA and host-level resilience together and test the combined failure scenarios.

A Gulu procurement brief should include the Hyper-V topology, protected networks, link speeds, VPN requirements and desired support term. If the organization is expanding, include the expected number of future users or sites. That context supports a more appropriate FortiGate-VM licensing discussion and reduces the risk of treating a virtual appliance as a generic downloadable image.

FortiGate VM64 Hyper-V Kenya

Kenya operations using Microsoft Hyper-V can integrate FortiGate-VM into private-cloud and enterprise virtualization designs. For regional companies, the benefit of a common FortiOS platform is operational consistency: similar policy concepts, VPN standards and administrative processes can be applied across Kenya, Tanzania and Uganda while each site retains its own capacity and connectivity design.

A Nairobi data-centre workload, for example, may require substantially more east-west inspection and VPN traffic than a branch environment. Do not standardize on a license tier merely for purchasing convenience if the workloads differ. Instead, standardize the design method: measure bandwidth, identify security services, estimate concurrency, document interfaces and choose the appropriate current entitlement for each deployment.

Migration projects should include a rule-review phase. Moving an existing firewall configuration into a virtual environment is an opportunity to remove obsolete objects, verify routes and tighten administrative access. Test application dependencies in a controlled window and keep rollback options. For new deployments, build monitoring and logging from the beginning rather than adding visibility only after an incident.

Kenya procurement teams coordinating with Tanzania can document license ownership, renewal dates, FortiOS standards and configuration backup locations centrally. FourTeck’s regional sites can support a connected requirements discussion, but product availability, pricing and service scope should be confirmed for the specific project rather than inferred from another market.

FortiGate VM64 Hyper-V Kuwait

Kuwait organizations with Hyper-V infrastructure can use FortiGate-VM to create virtual security boundaries around servers and applications. This is relevant to private-cloud environments, disaster-recovery sites and enterprises that prefer software-defined deployment while retaining FortiOS security policy. The architecture should be designed around traffic flow and licensed services rather than the virtual image filename.

For high-throughput environments, confirm host network capacity as well as firewall licensing. Virtual NICs, physical adapters, vSwitch configuration and upstream switching can all become bottlenecks. Security inspection may also change throughput characteristics, so capacity planning should reflect the enabled feature set and expected encrypted traffic rather than headline link speed alone.

Where uptime requirements are strict, document HA behavior, host maintenance procedures and configuration synchronization. Fortinet provides Hyper-V guidance for FortiGate-VM high availability and Live Migration scenarios, but administrators should follow documentation appropriate to the deployed FortiOS release. Test changes in a maintenance window and retain recoverable configuration backups.

For a Kuwait quotation connected to a wider regional standard, provide the intended VM tier, host platform, VPN requirements, subscriptions and support term. This creates a comparable bill of requirements across countries while allowing each site to be engineered for its actual workload.

FortiGate VM64 Hyper-V Ghana

Ghana enterprises running Microsoft Hyper-V can position FortiGate-VM between virtual workloads and external or internal networks that require controlled access. A virtual firewall can be useful in consolidated server environments because security policy can sit close to the workloads without adding a physical appliance for every segmentation point.

Before implementation, classify networks by trust and function. Production servers, management, backup, user and public-facing services should not automatically share the same access rules. Translate application requirements into explicit policies and document ownership for each exception. This improves troubleshooting and reduces the chance that legacy access remains open indefinitely.

VPN and remote administration should be planned as separate security workflows. Determine who needs access, from where, to which systems and with what authentication controls. Logging should make important administrative and security events reviewable. If central management is part of the strategy, include it in licensing and network design from the outset.

Ghana buyers coordinating with Tanzania can use a common quotation template containing Hyper-V hosts, bandwidth, zones, VPNs, security services and support period. FourTeck Ghana and FourTeck Tanzania can then be referenced for regional requirements while exact commercial terms are confirmed for each market and project.

FortiGate VM64 Hyper-V Nigeria

Nigeria organizations may operate large virtualized environments with substantial application, branch and remote-user traffic. FortiGate VM64 Hyper-V can be incorporated into these architectures as a FortiOS virtual firewall, but capacity planning must account for the scale and inspection profile of the deployment. A design for a small server cluster should not be extrapolated to a large multi-site hub without measurement.

Begin with traffic baselines and growth assumptions. Identify peak internet use, east-west server traffic, VPN demand and security services. Confirm how many virtual interfaces and zones are needed and how they connect to physical uplinks. For environments with multiple Hyper-V hosts, ensure virtual networking is consistent across the cluster so migrations do not silently change the security path.

Operational processes matter as much as initial deployment. Establish configuration backups, change approval, firmware review, license renewal tracking and log monitoring. If multiple FortiGate instances are deployed, consistent object naming and policy conventions can reduce administrative errors. High availability should be tested with representative sessions and VPN traffic.

Nigeria procurement requests should identify whether the requirement is a new deployment, replacement or expansion. Include the current firewall if applicable, Hyper-V architecture, bandwidth, protected applications, VPN concurrency and subscription needs. This helps align the current Fortinet VM license tier and implementation effort with the real environment.

FortiGate VM64 Hyper-V Seychelles

Seychelles organizations with compact data-centre or server-room footprints can benefit from virtualizing security functions alongside Hyper-V workloads, provided availability and resource dependencies are understood. FortiGate VM64 Hyper-V can secure server segments and VPN connectivity without requiring a separate physical appliance for each virtual boundary, which may simplify infrastructure where space and hardware logistics are considerations.

The trade-off is dependency on the virtualization stack. If the host, storage or networking layer fails, the virtual firewall can be affected alongside the applications it protects. Design backups, host resilience and recovery procedures accordingly. For critical services, evaluate whether FortiGate HA, multiple hosts or another architecture is appropriate and test the chosen design before relying on it.

Connectivity planning should consider primary and backup internet options, especially for cloud applications and inter-island or international dependencies. If VPN is essential, document how tunnels recover after link changes. Keep management access controlled and ensure time, DNS and logging services remain available during normal failover conditions.

A Seychelles quotation should describe the Hyper-V environment, application criticality, internet links, VPNs and security services. For regional organizations with Tanzania operations, the same documentation format can be reused so license ownership, renewal dates and configuration standards remain easy to manage across locations.

FortiGate VM64 Hyper-V licensing and quotation checklist

Fortinet’s current FortiGate-VM portfolio uses licensed VM tiers and subscription choices. Because product packaging changes over time, request a current entitlement recommendation for the planned vCPU allocation and feature set. Do not infer a commercial license simply from an FG-VM64-HV image filename.

• Microsoft Hyper-V and Windows Server version.
• Number and specification of Hyper-V hosts.
• Planned vCPU and memory allocation within the licensed entitlement.
• Internet bandwidth and expected inspected throughput.
• Number of virtual networks, VLANs and FortiGate interfaces.
• Site-to-site and remote-access VPN requirements.
• Security services to be enabled and desired subscription term.
• High-availability, Live Migration and recovery objectives.
• Logging, reporting and centralized management requirements.
• Existing firewall configuration or migration scope.

FortiGate VM64 Hyper-V FAQs

Decision recap

Choose FortiGate VM64 Hyper-V when a FortiOS virtual firewall fits a Microsoft Hyper-V security architecture and the organization is prepared to design virtual networking, licensing, availability and operations as one system. Verify the current Fortinet VM entitlement, allocate resources within that license, map every protected traffic path, and test failover and recovery. For Tanzania projects, include enough technical context in the enquiry to distinguish license supply from migration, configuration and support work.

Consult FourTeck Tanzania

Send your Hyper-V host specification, current network diagram, bandwidth, VPN requirements and expected security services. FourTeck can use those details to discuss an appropriate current FortiGate-VM licensing and deployment scope. Pricing, availability, subscription terms and implementation scope should be confirmed at quotation time.

Request a FortiGate-VM Quote