FortiManager Virtual Series in Dubai, UAE
FortiManager Virtual Series gives organisations a software-based way to centralize Fortinet device administration, policy control, configuration workflows and operational governance inside a supported virtual environment. The family is designed for businesses that prefer virtual infrastructure flexibility while retaining the FortiManager management experience and the ability to scale licensing as the managed estate grows.
Start with the management requirement
Before choosing a license, define the number of devices and VDOMs, management domains, target FortiManager release, virtual platform, resiliency requirement and support expectation. These inputs determine whether a 10-, 100- or 1000-device subscription tier, a stackable perpetual model, or another FortiManager deployment option is the better fit.
Runs on supported virtual platforms
Scale devices and VDOMs by license
Choice depends on procurement model
Confirm release notes before deployment
Direct answer for buyers
FortiManager Virtual Series is the virtual-appliance form of FortiManager, used to centrally administer Fortinet networking and security environments from software running on a supported virtualization platform. It suits organisations with distributed FortiGate estates, SD-WAN or branch deployments, virtual-data-centre strategies, and IT teams that want centralized policy and configuration workflows without a dedicated management appliance. Before proceeding, buyers should confirm the exact number of devices and VDOMs, subscription versus perpetual licensing, required ADOMs, hypervisor support for the intended FortiManager version, compute and storage resources, high-availability design, FortiCare level, and any migration requirement from an existing FortiManager deployment.
What FortiManager Virtual Series does
The platform provides a centralized control point for managing Fortinet network and security infrastructure. In practical terms, it can help a network or security operations team organize device configurations, standardize policy packages, coordinate changes, manage large groups of FortiGate devices and support repeatable deployment processes across branches, campuses, data centres and cloud-connected environments. Fortinet positions FortiManager as a management and orchestration platform for FortiGate and the wider FortiOS-based networking ecosystem.
The virtual form factor changes where FortiManager runs, not the fundamental management role it performs. Instead of installing a dedicated FortiManager hardware appliance, the customer allocates virtual infrastructure and deploys the supported FortiManager VM image. This can be useful when the business already operates a mature virtualization environment, wants management resources to live alongside other virtual infrastructure, or prefers a software-defined path for scaling management capacity.
The family should not be understood as one fixed VM with one universal capacity. Licensing and version choices affect the number of devices or VDOMs that can be managed, log allowance, ADOM availability, support and the resources required. The right bill of materials therefore begins with the managed environment, not with a generic VM size.
Who should consider it
FortiManager Virtual Series is particularly relevant to organisations that already rely on virtualized infrastructure and want to centralize Fortinet administration. Multi-site enterprises, managed service environments, retail and hospitality groups, education networks, healthcare organisations, government entities and businesses with distributed FortiGate or Secure SD-WAN deployments may benefit when local device-by-device administration becomes difficult to control consistently.
It is also worth evaluating when an organisation expects its firewall estate to grow. Fortinet’s current VM licensing model supports stackable capacity, allowing the management entitlement to expand rather than forcing a direct move to a larger physical appliance. That flexibility is valuable only when the underlying virtualization resources, operational procedures and license plan are sized correctly.
A physical FortiManager appliance or FortiManager Cloud may be preferable in some projects. For example, a buyer that does not want to operate the supporting hypervisor and VM resources may prefer a cloud-delivered management model, while another buyer may choose dedicated hardware for operational or architectural reasons. FourTeck can help compare these deployment approaches against the actual environment rather than assuming that virtual is always the best option.
Business challenges the virtual series can help address
Inconsistent firewall changes
When administrators manage many devices independently, configuration drift and inconsistent change processes become more likely. Centralized policy packages, templates and controlled workflows can improve repeatability, but the organisation still needs sound governance and testing procedures.
Distributed branch growth
Large branch, SD-WAN and campus environments can create repetitive administration work. FortiManager supports centralized provisioning and management workflows that help teams manage scale more systematically.
Virtual-first infrastructure strategy
Some organisations prefer to run management services on existing virtual infrastructure rather than add another physical appliance. FortiManager VM supports that architecture, subject to release-specific hypervisor, CPU, memory and storage requirements.
License and capacity planning
Management needs can change as new devices or VDOMs are added. Stackable licensing gives a route to expand, while buyers still need to plan ADOMs, support terms, log allowance and renewal alignment.
Core capabilities in a buyer-friendly view
Coordinate configuration and policy administration across supported Fortinet devices from one management platform.
Use templates, scripts, APIs and structured workflows to reduce repetitive manual tasks and make changes more consistent.
Choose subscription tiers or perpetual upgrade increments and expand managed-device capacity as requirements grow.
FortiManager VM supports HA designs; correct licensing, matching platform design and operational planning must be confirmed before implementation.
ADOMs help separate management domains. Subscription VM licensing currently includes five ADOMs, with additional requirements to be planned separately.
FortiManager is designed to manage FortiGate and extends management across FortiOS-based networking components such as FortiSwitch, FortiAP and FortiExtender where supported.
Which FortiManager virtual licensing approach fits?
| Requirement | Suitable direction | Confirm before ordering |
|---|---|---|
| Small managed estate or initial centralization project | Evaluate the 10-device/VDOM subscription tier or suitable perpetual capacity | Actual device/VDOM count, ADOM needs, support, growth plan |
| Mid-size multi-site deployment | 100-device/VDOM subscription tier may be a practical starting point | VDOM counting, log allowance, future branch additions, co-term requirements |
| Large or rapidly growing estate | 1000-device/VDOM subscription or stacked capacity | Platform resources, administrative domains, HA, automation scale |
| Existing perpetual FortiManager VM | Use applicable VM upgrade increments or assess migration to subscription | Current license, support status, target capacity, migration plan |
| Need to avoid operating a VM platform | Compare FortiManager Cloud or another FortiManager deployment type | Data location, operational ownership, feature and licensing requirements |
This matrix is selection guidance, not a quotation. Fortinet licensing, product terms and supported deployment platforms can change, so the exact SKU and current vendor documentation should be confirmed for every order.
Verified FortiManager Virtual Series information
Fortinet’s current FortiManager data sheet and ordering guide distinguish subscription VM-S licensing from perpetual VM licensing. The values below are family-level facts and license increments; they should not be interpreted as one combined VM model specification.
| Brand | Fortinet |
| Product family | FortiManager Virtual Machines / FortiManager-VM |
| Product type | Virtualized centralized network and security management platform |
| Subscription capacity tiers | Stackable 10, 100 and 1000 devices/VDOMs |
| Subscription log allowance | 2, 5 and 10 GB/day respectively for current 10, 100 and 1000 tiers |
| Subscription support | Current subscription SKUs include FortiCare Premium; other support options are license dependent |
| Subscription ADOMs | Five ADOMs included; additional ADOMs require separate planning |
| Perpetual upgrade increments | +10, +100, +1000 and +5000 devices/VDOMs |
| VM stackability | VM SKUs can be stacked up to 100,000 devices/VDOMs according to the current data sheet |
| vCPU guidance | Current data sheet lists 4 vCPU minimum; actual sizing depends on FortiManager version and managed scale |
| Memory and storage | Version dependent. Current platform guides for recent releases increase RAM minimums and require substantial disk allocation; verify the deployment guide for the exact version |
| Network interfaces | Up to 12 vNIC interfaces are documented for supported releases; actual consumable interfaces vary by cloud or hypervisor platform |
| High availability | Supported; cluster design and licensing must be confirmed |
| Hypervisor support | Release dependent; Fortinet directs buyers to the support matrix and release notes for each FortiManager version |
| Availability | Contact FourTeck for current UAE SKU, term and lead-time confirmation |
Licensing, ADOM and platform dependencies to resolve first
Subscription licensing
FortiManager-VM-S uses stackable subscription SKUs for 10, 100 and 1000 managed devices/VDOMs. Current subscription ordering includes FortiCare Premium within the subscription SKU. The term, device quantity and any co-term requirement need to be reflected in the quotation. A VDOM counts as a licensed network device, so an estate with extensive VDOM use may require more entitlement than a simple physical-device count suggests.
Perpetual licensing
Fortinet’s June 2026 ordering guide continues to show the FortiManager perpetual VM path. Existing deployments can expand with +10, +100, +1000 or +5000 device/VDOM upgrade SKUs. Support is handled separately and the correct FortiCare band must be aligned with the managed scale. Customers can also migrate from an existing perpetual VM to a new subscription VM, but that is a project requiring license purchase, installation and data migration planning.
ADOM and architecture planning
Administrative Domains allow separate management partitions for teams, customers, environments or policy scopes. Current subscription VM licensing includes five ADOMs. More complex service-provider, multi-tenant or delegated-management designs may require additional ADOM planning. Buyers should not assume that increasing the device count automatically resolves all ADOM requirements.
A practical deployment and purchase journey
Inventory the estate
Count FortiGate devices, VDOMs and other Fortinet components that need centralized management. Separate current quantity from expected growth over the planned license term.
Choose the operating model
Decide whether the organisation wants subscription VM licensing, an existing perpetual VM path, or a comparison with FortiManager Cloud or dedicated hardware.
Validate the platform
Confirm the target FortiManager release, supported hypervisor, CPU, RAM, disk and network-interface requirements using the matching Fortinet release documentation.
Build the license plan
Map device/VDOM capacity, ADOMs, support level, subscription term, HA, renewal timing and any add-ons into one bill of materials.
Plan implementation
Define whether the project is a new deployment, migration or expansion, and include configuration, testing, backup, change-control and handover activities where required.
Central policy control for distributed Fortinet estates
The most important reason many organisations evaluate FortiManager is the operational difficulty of maintaining consistent firewall configurations as the estate expands. A business may begin with a small number of FortiGate devices and later add branches, remote offices, data-centre firewalls, cloud firewalls or SD-WAN sites. At that point, managing changes directly on each firewall can make it harder to understand whether policies are consistent, whether approved objects are being reused correctly and whether a branch has drifted from its intended configuration.
FortiManager provides centralized policy packages, object management and administrative workflows that let teams structure network-security changes more deliberately. This can support standardized branch templates, controlled deployment of policy changes and a clearer separation between preparation, review and installation of changes. The platform itself does not replace a change-management process. Organisations should still maintain approved maintenance windows, rollback planning, peer review and testing for sensitive configuration changes.
For a virtual deployment, the operational value is paired with infrastructure flexibility. The FortiManager service can reside on supported virtual infrastructure, making it easier to integrate with existing VM backup, monitoring and data-centre procedures where those practices are compatible with Fortinet guidance. Buyers should confirm how the VM will be protected, who owns the underlying hypervisor, how snapshots or backups will be handled, and whether the chosen resilience approach is supported for the intended FortiManager version.
Automation, provisioning and repeatable operations
Central management becomes more valuable when it reduces repetitive work rather than simply moving the same manual tasks into another console. FortiManager supports automation through templates, scripts, APIs, connectors and workflow mechanisms. For organisations deploying large numbers of similar branches, those capabilities can help turn repeatable network and security design standards into reusable operational building blocks.
Zero-touch provisioning is especially relevant to distributed environments. A branch device can be prepared to join a standardized management process instead of requiring an engineer to reproduce every setting manually at each location. The real benefit depends on how well the organisation defines templates, naming conventions, addressing, SD-WAN design, device groups and exception handling. A poorly governed automation process can reproduce an error just as efficiently as a good process reproduces a correct configuration, so controlled design and validation remain essential.
API and scripting capabilities also matter when FortiManager is part of a broader operations toolchain. Enterprises may want ticketing systems, orchestration platforms or internal automation to trigger approved tasks. Fortinet documents integrations with common enterprise platforms and provides REST API support, but the exact integration should be validated against the customer’s FortiManager release and the third-party product version. FourTeck can help scope where centralized management ends and custom integration work begins.
Scalability, administrative separation and resilience
Scalability in FortiManager Virtual Series has more than one dimension. The managed device or VDOM entitlement is the most visible licensing limit, but buyers also need to think about ADOMs, log allowance, virtual hardware resources, concurrent operational activity and the organisation’s administrative model. A service provider with many separate customers, for example, may have different ADOM requirements from an enterprise with the same number of devices in one management domain.
Subscription SKUs are stackable across 10-, 100- and 1000-device/VDOM units, while current Fortinet documentation states that VM SKUs can scale to a high overall device/VDOM limit. That does not mean every underlying VM can be left at its initial CPU, memory and disk allocation while the license grows. Fortinet publishes version-specific deployment guidance and minimum system requirements; those values should be reviewed whenever the managed estate or FortiManager release changes.
High availability is another planning area. FortiManager VM supports HA, but a resilient management design needs more than a checkbox. Buyers should define where both instances run, how the underlying virtual infrastructure handles host or site failures, whether network paths and DNS dependencies are redundant, how backups are maintained, and how administrators will access management during a failure event. Licensing for the HA nodes and the correct deployment procedure should be confirmed in the current Fortinet documentation before purchase.
Ideal business environments and use cases
Multi-branch enterprise
A distributed organisation can use centralized policy, configuration templates and device grouping to make branch management more consistent. This is useful for retail chains, hospitality groups, logistics networks and professional-services companies with similar connectivity patterns across many locations.
Secure SD-WAN operations
FortiManager is commonly evaluated alongside Fortinet Secure SD-WAN when teams need repeatable branch rollout, centralized configuration and consistent policy administration. The exact architecture and feature set depends on FortiGate models and FortiOS/FortiManager versions.
Virtual data centre
Businesses with established VMware, KVM or other supported virtual platforms may prefer to host FortiManager as a VM so the management system fits existing infrastructure operations. Hypervisor support must be checked against the intended release.
Managed or segmented administration
ADOMs can support administrative separation between environments or customers. This is relevant to larger enterprises and service-oriented teams, but ADOM count and delegation design should be planned before licensing.
Integration and operational considerations
FortiManager should be treated as a critical management system rather than as an isolated utility VM. It may control configuration changes across a large security estate, so access control, administrative authentication, backup, monitoring, network reachability and change procedures deserve the same attention as other core infrastructure platforms. Define which management networks the VM will use, how administrators reach it, whether out-of-band access is needed and how the system communicates with managed Fortinet devices.
Version compatibility is especially important. FortiManager and FortiGate support relationships change over time, and a FortiManager upgrade can be part of a broader FortiOS lifecycle plan. Before a major rollout or migration, review the Fortinet compatibility information for the specific FortiManager and FortiOS releases in scope. If the estate contains several firewall generations or firmware branches, the upgrade sequence may need careful staging.
For integration with IT service management, SIEM, automation or internal orchestration platforms, clarify the business workflow first. Some organisations simply need centralized firewall administration; others want API-driven onboarding, ticket-linked change control or reporting integration. These are different scopes. FortiManager offers APIs and integration mechanisms, but implementation effort depends on the third-party platform, authentication method, data model and internal operating process.
Logging also needs to be understood correctly. FortiManager includes log allowances associated with licensing, but organisations that require deeper analytics, long retention, event correlation or dedicated security analytics may also evaluate FortiAnalyzer. The role of FortiManager is centralized management and orchestration; logging architecture should be designed according to operational and compliance needs rather than assuming the management VM is the only logging platform required.
Buyer questions to resolve before requesting a quote
Count both current and planned capacity. Each VDOM is relevant to licensing, so the number can be higher than the number of physical firewalls.
This determines supported hypervisors, minimum resources, compatibility with managed FortiGate versions and available features.
Subscription licensing includes five ADOMs. Multi-tenant or strongly segmented environments may need more.
Compare procurement preference, support handling, renewal planning, expected growth and migration from any existing perpetual VM.
If centralized management is operationally critical, define an HA architecture and confirm the licensing and platform design for both nodes.
Clarify whether the quote should include only licensing or also deployment, migration, configuration, policy onboarding, testing, documentation or support coordination.
Procurement checklist for FortiManager Virtual Series
✓ Confirm the exact subscription or perpetual licensing path.
✓ Record the number of managed devices and VDOMs.
✓ Include forecast growth over the intended license term.
✓ Confirm the number of ADOMs required.
✓ Identify the target FortiManager software release.
✓ Validate the hypervisor or cloud platform against that release.
✓ Size vCPU, RAM, disk and virtual network interfaces correctly.
✓ Decide whether high availability is required.
✓ Confirm FortiCare support level and renewal timing.
✓ Identify any existing perpetual license or migration requirement.
✓ Define configuration, onboarding and policy-migration scope.
✓ Include documentation, testing and handover expectations.
✓ Confirm delivery destination and required license start timing.
✓ Ask FourTeck to validate the final bill of materials before purchase.
The checklist is intentionally broader than a SKU request because most FortiManager VM purchasing errors arise when an organisation focuses only on the initial device count. The deployment platform, ADOM structure, support term and migration plan can be just as important to a successful order.
How FourTeck can assist with sizing and configuration planning
FourTeck can help turn a general request for “FortiManager VM” into a more accurate bill of materials. The first step is to understand the managed environment: firewall count, VDOM usage, branch growth, FortiOS versions, administrative separation, preferred virtualization platform, HA expectation and support term. From there, the relevant FortiManager licensing direction can be narrowed down.
For new deployments, assistance can include requirement clarification, license-tier selection, deployment planning and configuration scope. For existing FortiManager customers, the discussion may focus on adding capacity, aligning renewals, moving from perpetual to subscription licensing, or preparing a controlled platform upgrade. When a project also involves firewall deployment, SD-WAN, configuration migration or broader security changes, those services should be scoped separately so the quotation clearly shows what is included.
You can review related FourTeck technology services or discuss a Fortinet infrastructure requirement through the FourTeck contact team.
Information that helps us quote accurately
Managed Fortinet device list or approximate count
VDOM count and growth estimate
Current FortiManager status, if any
Preferred subscription term or perpetual model
Target FortiManager and FortiOS versions
Virtualization platform and resource availability
Number of ADOMs and administrator groups
HA, migration and implementation requirements
UAE delivery entity and required project timeline
UAE availability and support guidance
FortiManager Virtual Series licensing is supplied according to the selected SKU, term and entitlement rather than as a physical appliance that can be described with a single stock status. Contact FourTeck to confirm current UAE availability for the required subscription or perpetual licensing path. Availability may depend on model or SKU, license term, quantity, vendor processing and regional entitlement rules. For a new project, it is useful to confirm the intended activation timing as well as the procurement date so the subscription term aligns with the deployment schedule.
Implementation support should also be agreed before purchase if it is needed. A license-only quotation is different from a project that includes VM deployment, migration from an existing FortiManager, onboarding of FortiGate devices, ADOM design, policy import, HA configuration, testing and knowledge transfer. FourTeck can help define these items so commercial and technical expectations are clear before the order is placed.
Coverage across Dubai, Abu Dhabi, Sharjah and Ajman
Organisations in Dubai, Abu Dhabi, Sharjah and Ajman can discuss FortiManager Virtual Series requirements with FourTeck as part of a wider UAE technology project. Because the product is virtual and license-driven, the planning conversation usually focuses on the customer’s data-centre or cloud environment, managed Fortinet estate, license size and implementation scope rather than on appliance rack space or physical interfaces. Delivery coordination, license activation planning and professional-service requirements can be aligned after the exact SKU and project requirement are confirmed. For related Fortinet firewall projects, buyers can also review FourTeck’s Fortinet firewall solutions in Dubai and the Fortinet UAE resource.
GCC Availability
FourTeck can assist organisations planning FortiManager Virtual Series projects across GCC markets with requirement review, licensing selection, quotation coordination and deployment-scope discussions. A regional project may involve the United Arab Emirates, Saudi Arabia, Kuwait, Qatar, Bahrain or Oman, but the commercial and technical assumptions should be checked for each destination rather than copied from one country to another. FortiManager VM licensing depends on the chosen subscription or perpetual approach, managed devices and VDOMs, term, support and administrative requirements. Project teams should also confirm where the virtual appliance will run and whether remote or on-site implementation assistance is expected. Product availability, license processing, service visits, vendor lead times and local commercial requirements can vary by country, quantity and project scope. Share the destination country, expected managed-device count, license term, virtualization environment and desired deployment schedule so FourTeck can prepare a more relevant regional quotation. For Kuwait-focused technology coordination, buyers may also review FourTeck Kuwait.
Africa Availability
FortiManager Virtual Series can also be evaluated for organisations coordinating Fortinet management projects in Africa. FourTeck can help teams review device and VDOM counts, subscription terms, perpetual upgrade requirements, ADOM planning, supported virtual platforms, support needs and implementation scope before a quotation is prepared. Regional fulfilment can depend on the destination, license entitlement, quantity, vendor lead time, project schedule and the location of the infrastructure that will host the FortiManager VM. For multi-country deployments, it is important to identify whether one centralized management environment will control devices across several locations and whether administrative separation is required. Buyers should share the destination country, expected deployment schedule, license size and any configuration, migration or support expectations. FourTeck’s Africa technology resource can support broader regional discussions, including selected East African requirements where appropriate. Availability and service coverage should always be confirmed for the specific project rather than assumed from another country.
Related FortiManager and Fortinet options to evaluate
FortiManager Cloud
A cloud-based FortiManager deployment can be considered when the organisation wants centralized management without operating its own FortiManager VM infrastructure. Compare data location, licensing, operational control and feature requirements.
FortiManager hardware appliances
Dedicated FortiManager hardware may suit organisations that prefer an appliance-based management platform. Model selection depends on managed-device scale, storage, resilience and infrastructure policy.
FortiAnalyzer
FortiAnalyzer can complement FortiManager when deeper centralized logging, analytics, reporting and security-event workflows are required. Compatibility and license sizing should be confirmed separately.
FortiGate and Secure SD-WAN projects
FortiManager is often part of a wider FortiGate or Secure SD-WAN architecture. Firewall models, FortiOS versions, branch templates and connectivity design should be scoped as part of the complete project.
Why businesses contact FourTeck for FortiManager planning
The value of a FortiManager quotation is determined by how accurately it reflects the environment. FourTeck focuses the discussion on practical procurement and deployment questions: which license structure matches the estate, how VDOMs affect the count, whether additional ADOMs are required, what virtual platform will host the system, how the FortiManager and FortiOS versions align, and whether deployment or migration services should be included. This helps reduce the risk of ordering only the visible base license while overlooking support, capacity or implementation dependencies.
FourTeck can also help customers compare the virtual series with other FortiManager deployment options when architecture is still open. The aim is to establish a suitable management approach for the actual business environment and then coordinate the quotation. Buyers wanting to understand FourTeck’s broader technology background can visit the FourTeck company overview.
What buyers commonly need to understand before choosing FortiManager VM
A FortiManager VM purchase can look straightforward when search results show a single license code, but real deployments usually involve several layers of decision-making. The first is the distinction between the management software and the infrastructure that runs it. FortiManager Virtual Series does not arrive as a physical management appliance. The customer provides a supported virtual environment and allocates the resources required for the FortiManager release. That is why a buyer should not choose a license simply because the device count looks correct. The hypervisor, FortiManager version, FortiGate compatibility, RAM, disk, vCPU and resilience design also need to match the project.
Why do FortiManager VM prices vary so much online?
Listings may represent different device/VDOM tiers, subscription terms, support bundles, add-ons, currencies or older perpetual SKUs. A 10-device one-year subscription is not comparable with a 100-device five-year subscription, and a FortiAI or support add-on is not the base management entitlement. The correct comparison starts with the exact Fortinet SKU and term.
What does “device/VDOM” mean for licensing?
A VDOM is a virtual domain within a FortiGate. Fortinet counts each VDOM as a licensed network device for FortiManager capacity. A company with 40 physical FortiGates can therefore require more than 40 management entitlements if those appliances use multiple VDOMs. This is one of the most important figures to verify before requesting a quote.
Another frequent question is whether the subscription and perpetual VM models are the same commercially. They are not. Current Fortinet subscription VM-S SKUs bundle the VM entitlement and FortiCare Premium support and are sold in stackable 10-, 100- and 1000-device/VDOM tiers. The perpetual path remains documented for customers who prefer that model or already operate an FMG-VM, with capacity expansion through upgrade SKUs and support handled separately. The better choice depends on the organisation’s procurement preference, existing license position, renewal strategy and growth forecast.
Buyers also search for “FortiManager VM requirements” and often find different RAM values. That happens because requirements have changed between releases. The current data sheet presents family-level VM values, while platform-specific deployment guides provide release-level minimums and examples. Recent FortiManager deployment documentation increases the RAM minimum for newer software branches compared with older releases. Therefore, the only reliable sizing process is to choose the target FortiManager version first, then consult that version’s deployment guide and support matrix. Reusing the resources from an older FortiManager VM can create avoidable upgrade problems.
Subscription, cloud service or self-hosted VM?
FortiManager VM is self-hosted on infrastructure the customer controls. FortiManager Cloud is a cloud-managed service with a different operating model. A buyer who wants maximum control over the virtual appliance, local infrastructure integration or an existing virtual data-centre design may prefer FortiManager VM. A buyer who does not want to manage the underlying FortiManager server may prefer a cloud option. Data-residency policy, operational ownership, connectivity, feature requirements and cost model should be compared before deciding.
The free trial is another area where buyers can misunderstand what is included. Fortinet’s current ordering guide describes a FortiManager VM free trial with three devices/VDOMs and three ADOMs, but trial licensing does not include services or support. A trial can be useful for lab evaluation, administrator familiarization or a proof of concept, but it should not be treated as a substitute for a properly licensed production deployment. When a trial is converted to production, the customer should confirm the appropriate paid capacity, support and migration approach.
High availability also deserves more planning than a simple “yes/no” answer. FortiManager supports HA, but the customer must decide how many FortiManager instances are required, how they will be placed across hosts or sites, how networking and storage dependencies are protected, and how the management service will be accessed during an outage. Fortinet’s ordering guidance indicates that HA involves matching FortiManager platforms. For a virtual deployment, FourTeck can help identify the commercial requirement while the technical design is validated against the target release.
Finally, an accurate quotation should state what is not included. Licensing alone does not automatically include migration, onboarding, policy cleanup, ADOM restructuring, API integration, hypervisor administration or user training. These may be valuable project services, but they should appear as explicit scope items. Buyers can save time by sharing an approximate device/VDOM count, FortiGate models and versions, current FortiManager status, intended hypervisor, required ADOMs, support preference and planned go-live window with the initial inquiry.
Questions that shape the right FortiManager Virtual Series decision
Do we size by physical firewalls or by VDOMs?
Use the licensed device/VDOM count, not only the number of chassis. Fortinet treats each VDOM as one licensed network device. A discovery exercise should therefore export or document active VDOMs and add expected growth. This matters especially in data centres, service-provider environments and segmented enterprises where one FortiGate can host several virtual domains.
Can we start small and expand later?
Yes, the licensing family is designed to support expansion, but the method depends on whether the deployment uses subscription or perpetual licensing. Subscription tiers are stackable, while perpetual deployments use defined upgrade SKUs. Expansion should also trigger a review of VM resources, ADOM requirements and support coverage rather than only adding license capacity.
Which hypervisor should we use?
Use a platform explicitly supported by the intended FortiManager release. Fortinet publishes virtualization support information in release notes and platform administration guides. Do not assume a hypervisor supported by an older FortiManager build is automatically supported by a newer one. The platform decision should also consider backup, HA, networking, monitoring and operational ownership.
Is FortiAnalyzer included or still needed?
FortiManager and FortiAnalyzer are different products. FortiManager focuses on management and orchestration, while FortiAnalyzer provides dedicated logging, analytics and reporting capabilities. FortiManager licenses include defined log allowances, but a business with significant retention, compliance or SOC analytics needs should evaluate FortiAnalyzer separately.
What changes when we migrate from perpetual to subscription?
Fortinet’s current order guide states that customers can purchase a new subscription license, install it on a supported platform and migrate data from the old perpetual VM. That means the project is not merely a license-key replacement. The target VM, software version, backup, migration method, maintenance window and post-migration validation should all be planned.
What should we send FourTeck for a quote?
Provide the managed device and VDOM count, preferred term, current FortiManager license if any, target software release, virtualization platform, number of ADOMs, HA requirement and whether deployment or migration services are needed. If some details are unknown, share the network inventory and FourTeck can help identify the questions that need resolution before the final bill of materials.
Frequently asked questions
What is FortiManager Virtual Series?
It is the virtual-machine form of Fortinet FortiManager, providing centralized management and orchestration for Fortinet network and security deployments on supported virtual infrastructure.
How is FortiManager VM licensed?
Current Fortinet documentation provides subscription VM-S licensing in stackable 10-, 100- and 1000-device/VDOM tiers and also documents a perpetual VM path with capacity upgrade SKUs. The correct model depends on the customer’s requirement and existing license position.
Does each VDOM count toward the license?
Yes. Fortinet states that each VDOM operating on a physical or virtual device counts as one licensed network device for FortiManager capacity planning.
How many ADOMs are included with the subscription VM?
Current Fortinet documentation states that FortiManager VM subscription licenses include five ADOMs. Additional ADOM requirements should be confirmed separately.
What are the VM hardware requirements?
Requirements vary by FortiManager release and managed scale. Fortinet’s data sheet lists a four-vCPU minimum, while current deployment guides specify version-dependent memory and storage minimums. Always validate the exact release before allocating resources.
Can FortiManager Virtual Series run in high availability?
Yes, FortiManager VM supports high availability. The matching platforms, licensing, placement and underlying virtual infrastructure should be designed and confirmed before deployment.
Can an existing perpetual FortiManager VM move to subscription licensing?
Fortinet’s current ordering guide describes a migration path in which a new subscription license is purchased, installed on a supported platform and data is migrated from the older perpetual VM.
Is a FortiManager VM trial available?
The current Fortinet ordering guide describes a free trial with three devices/VDOMs and three ADOMs. Trial licenses do not include services or support and should be used for evaluation rather than assumed production entitlement.
How can I request a FortiManager Virtual Series quote in Dubai?
Send FourTeck your device/VDOM count, desired term, current FortiManager status, target platform, ADOM needs, HA requirement and any deployment or migration scope. FourTeck can then help confirm the current UAE licensing and quotation options.
Build the FortiManager VM requirement before placing the order
A precise FortiManager Virtual Series quote starts with the managed device/VDOM count, licensing model, target release, virtual platform, ADOM requirement and implementation scope. Share those details with FourTeck to confirm the current UAE option and avoid purchasing a license that does not match the operational design.