FortiAuthenticator 800F in Dubai, UAE
Built for organizations that need a dedicated identity control point, this 1RU Fortinet appliance centralizes authentication, access policy integration, multi-factor authentication, certificate services and single sign-on functions. It is particularly relevant when the security team must connect existing directories, Fortinet infrastructure and standards-based third-party systems without creating separate identity silos. FourTeck.com can help buyers define the correct user licensing, token requirements, availability, support coverage and deployment approach before a purchase request is finalized.
Request QuoteAsk for Configuration Support
Quick Product Information
Fortinet
FAC-800F
Hardware identity and access management appliance
1RU rack-mountable appliance
8,000 local + remote users
18,000 local + remote users
4 × GE RJ-45 + 2 × SFP
2 × 2 TB HDD in RAID 1
Dual 300W redundant auto-ranging supplies
MFA, SSO, RADIUS, TACACS+, CA, 802.1X, federation
Configuration and supplier dependent
Confirm users, tokens, HA, directories and support term
Buyer Snapshot: Is This the Right Platform?
This model sits in the higher-capacity part of the FortiAuthenticator hardware range and is intended for organizations that want centralized identity services on a physical appliance rather than relying only on a small branch device or a virtual deployment. The quickest way to judge fit is to compare the expected identity count, authentication flows, directory sources, network access methods and continuity requirement with the appliance limits and licensing model.
Enterprises, larger campus environments, multi-site businesses and security teams consolidating authentication services.
A dedicated platform for identity validation, MFA, SSO, certificate workflows and standards-based AAA services.
Base and future user count, FortiToken needs, user-license upgrades, support coverage and HA design.
Confirm Active Directory, LDAP, RADIUS, SAML, OIDC, certificate and Fortinet Security Fabric requirements.
Plan rack depth, redundant power feeds, management access, interface assignment, backups and maintenance windows.
Requirement review, configuration matching, quote preparation, sourcing coordination and warranty guidance.
Product Overview
Modern business networks often have several identity sources and several access points at the same time. Employees sign in to wired and wireless networks, administrators access infrastructure, remote users connect through VPNs, cloud applications rely on federation, and security policies increasingly need to understand who a user is rather than only which IP address is active. A dedicated FortiAuthenticator appliance brings these functions into a central identity layer so that authentication decisions and identity information can be managed more consistently.
The FAC-800F combines identity and access management functions with a hardware platform designed for larger deployments. Fortinet lists a base capacity of 8,000 local and remote users with an upper limit of 18,000. It can handle RADIUS and TACACS+ services, support 802.1X access control, integrate with directory systems, provide multi-factor authentication with FortiToken options, operate as a SAML identity provider or proxy, support OIDC use cases, provide certificate authority functions, and feed identity information into FortiGate policy workflows through Fortinet Single Sign-On. These capabilities make it relevant to organizations that are trying to reduce fragmented authentication systems while keeping standards-based interoperability.
From a procurement perspective, the important point is that this is not simply a box with a fixed user experience. The final design depends on licensing, authentication methods, token quantity, directory architecture, certificate requirements, redundancy, network segmentation and the firmware branch selected by the organization. Some functions can require associated licenses, compatible Fortinet components or external services. That means the correct purchase should be based on an identity architecture rather than only the appliance model number.
For UAE organizations planning an identity modernization project, FourTeck.com can help turn the technical requirement into a clearer bill of materials. Buyers can share current user counts, anticipated growth, number of authentication sources, VPN and network access methods, existing FortiGate deployments, desired MFA method and support expectations. The objective is to confirm the platform and related items before quotation, reducing the risk of ordering insufficient user capacity, missing tokens, overlooking HA requirements or discovering integration constraints late in the project.
Key Business Benefits
◆ Centralized identity decisions
Bringing authentication and identity services into one managed platform helps security teams reduce the operational burden of maintaining separate access-control systems for network, VPN and application use. Centralization also makes it easier to apply consistent authentication methods and understand which directory or identity source is authoritative for each use case.
◆ Stronger authentication options
Support for FortiToken, OTP methods, certificates and FIDO2 gives organizations multiple ways to strengthen user verification. This flexibility is valuable when different departments have different risk profiles, when administrators need stronger controls than ordinary users, or when passwordless access is being introduced in stages.
◆ Standards-based integration
RADIUS, TACACS+, LDAP, SAML, OIDC and certificate standards allow the platform to participate in mixed environments. Buyers are therefore not limited to a single access method, although every integration should still be tested against the exact application, firmware version and identity workflow planned for production.
◆ Capacity for larger deployments
The hardware platform starts at 8,000 users and can be licensed upward to the model’s published upper limit. That gives procurement teams a path to plan beyond the initial rollout while keeping expansion within a known appliance family. Growth should be budgeted alongside token counts, support renewals and high-availability needs.
◆ Identity-aware network policy
Fortinet Single Sign-On can share user and group context with FortiGate devices so network policy can use identity information instead of relying only on network addresses. For organizations already using Fortinet security infrastructure, this can improve policy clarity and reduce repeated authentication prompts in suitable workflows.
◆ Appliance resilience
RAID 1 local storage, a TPM and dual redundant power supplies support a more resilient physical deployment. Fortinet also supports active-passive high availability and configuration synchronization, allowing organizations with stricter continuity objectives to design redundancy beyond the hardware components inside a single chassis.
Product Highlights
RADIUS and TACACS+ support allows centralized authentication, authorization and accounting for compatible network and administrative access workflows.
FortiToken methods, email or SMS OTP options, client certificates and FIDO2 can be used according to the organization’s authentication design and licensing.
SAML identity provider and proxy functions, OIDC support and Fortinet SSO services help connect internal and cloud-facing access requirements.
The appliance can operate as a certificate authority and support certificate lifecycle tasks including issuance, signing and revocation for compatible use cases.
Acting as a RADIUS server, the system can support wired, wireless and VPN authentication designs where user credentials, device certificates or both are validated.
The 1RU chassis combines six network interfaces, mirrored local storage and redundant power in a form factor suitable for enterprise racks and data-room deployments.
These highlights should be interpreted as platform capabilities rather than a promise that every feature will be enabled in every deployment. Firmware version, user licensing, token licensing, external identity systems and connected Fortinet products can affect the final implementation. A buyer replacing an older appliance should also review supported migration paths and current release documentation before scheduling a cutover.
Technical Specifications
| Specification | FAC-800F Details |
|---|---|
| Brand | Fortinet |
| Model | FAC-800F |
| Product category | Identity and access management appliance |
| Local + remote users | 8,000 base / 18,000 upper limit |
| FortiTokens | 16,000 platform value; token licenses purchased separately as applicable |
| RADIUS clients / NAS devices | 2,666 base / 6,000 upper limit |
| User groups | 800 |
| CA certificates | 50 |
| User certificates | 40,000 |
| 10/100/1000 RJ-45 interfaces | 4 |
| SFP interfaces | 2 |
| Local storage | 2 × 2 TB HDD, RAID 1 |
| TPM | Yes |
| Power supply | Dual (1+1) 300W redundant auto-ranging, 100–240V |
| Average / maximum power consumption | 154W / 196.04W |
| Dimensions | 44 × 438 × 701.2 mm |
| Weight | 15.0 kg |
| Form factor | 1RU rack mountable |
| Operating temperature | 0°C to 40°C |
| Humidity | 5% to 95% non-condensing |
| Management | CLI, direct console DB9 CLI, HTTPS |
| High availability | Active-passive HA and configuration synchronization HA |
| Selected supported standards | RADIUS, LDAP, X.509, EAP-TLS, SCEP, OAuth, OIDC, SAML 2.0 and related standards |
| Warranty / support | Confirm FortiCare and warranty terms for the quoted supply |
When choosing a configuration, start with the number of identities that will actually authenticate through the platform, then add expected growth rather than sizing only for today. Separate ordinary users, privileged administrators, guest users and service accounts where their workflows differ. Next, document the authentication methods: RADIUS for network access, TACACS+ for infrastructure administration, SAML or OIDC for applications, certificate-based access, Fortinet SSO, and any external directories. This makes it easier to identify licensing, token and integration requirements. Buyers should also decide whether a single appliance meets the continuity objective or whether an HA pair is appropriate. Rack depth, redundant PDU feeds, backup policy, management network placement and upgrade windows should be confirmed before installation.
Configuration and Buyer Guidance
Identity appliances are often under-specified because procurement starts with the model and only later asks how many authentication transactions, users, directories and applications will depend on it. A better buying process begins with a short identity inventory. Document how users sign in today, which systems validate credentials, where MFA is required, which network devices send RADIUS or TACACS+ requests, which applications use federation, and whether certificates are already part of the security design.
Count active users and realistic growth. Include remote users and any populations that may become local accounts.
List VPN, wired, wireless, administrative, application SSO and certificate-based use cases.
Confirm Active Directory, LDAP, remote IdP, cloud identity and local user requirements.
Choose between token, OTP, certificate or FIDO2 approaches based on risk and user experience.
If authentication is business-critical, assess an active-passive design and redundant upstream connectivity.
Align FortiCare and maintenance planning with internal operational and compliance requirements.
Before requesting a quote from FourTeck.com, provide the current and three-year user estimate, planned MFA method, approximate number of RADIUS or TACACS+ clients, primary directories, whether FortiGate integration is required, desired HA approach, rack and power environment, and the intended support term. If this is a replacement project, also share the existing model, firmware level and migration window. Those details allow the quotation to reflect the real deployment rather than only the appliance chassis.
Ideal Business Use Cases
Enterprise network authentication
Organizations running 802.1X for wired or wireless access can use the platform as a RADIUS service to validate users, devices or certificates. This is useful where network access should follow identity rather than an open or shared-credential model.
VPN and remote-access MFA
Security teams can strengthen remote access by combining a primary credential with an additional factor. The exact method should be chosen based on user population, token licensing, connectivity and the remote-access platform in use.
Administrative AAA
TACACS+ and RADIUS can centralize authentication for administrators accessing compatible infrastructure. This can improve account control, reduce shared credentials and create a clearer separation between ordinary user access and privileged operational access.
Application federation and SSO
SAML and OIDC functions can support single sign-on and identity federation for compatible applications. This is relevant where users move between internal and cloud services and the organization wants a more consistent authentication experience.
Certificate-driven security
Certificate authority functions can support certificate issuance and lifecycle management for use cases such as VPN, HTTPS, device authentication and EAP-TLS. Certificate policy, key handling and renewal processes should be designed before rollout.
Fortinet Security Fabric identity
Organizations using FortiGate can use Fortinet Single Sign-On to pass user and group context into identity-aware policy decisions. This is especially useful in larger networks where several FortiGate devices need a consistent view of who is logged in.
These use cases can coexist on the same platform, but that does not mean every organization should enable all of them at once. A phased deployment is often easier to govern: begin with the highest-value authentication service, establish monitoring and backup procedures, then add federation, certificate or additional network-access functions as the identity architecture matures. Capacity, change control and support coverage should be reviewed at each phase.
FortiAuthenticator 800F Authentication and MFA Control
Authentication strength needs to match the risk of the resource being protected. A user signing in to a low-risk internal service may not need the same process as an administrator connecting to a firewall or an employee accessing sensitive information from outside the corporate network. This platform gives security teams a central place to combine directory identity with multiple authentication methods, including FortiToken-based factors, one-time passwords, client certificates and FIDO2 where supported by the overall design.
The practical advantage is policy flexibility. Instead of treating MFA as a single universal prompt, organizations can plan different controls for different user groups and access channels. Privileged users may require a stronger factor, remote users may use token-based MFA, certificate-based workflows can support managed devices, and FIDO2 can be introduced for passwordless experiences. Adaptive authentication capabilities can also consider context such as location, device characteristics, time and other login criteria to decide whether to challenge, permit or deny access according to configured policy.
For buyers, the critical planning item is not merely whether MFA exists; it is how many users need each method and what dependencies those methods introduce. FortiToken licenses are separate considerations, SMS may involve external service costs, certificates need lifecycle governance, and passwordless methods require compatible client and application support. During procurement, map the user population to the desired authentication experience. That produces a more accurate bill of materials and avoids paying for capacity that will not be used or, more importantly, discovering after deployment that a required factor was not included.
FortiAuthenticator 800F Federation, SSO and Directory Integration
Most established organizations already have identity systems. The objective of a new authentication appliance is therefore rarely to replace every directory. More often, the requirement is to connect existing identity stores with network access, security policy and application sign-on in a controlled way. Support for LDAP and Active Directory integration allows the platform to use external user and group information, while SAML and OIDC functions support federation with compatible services and applications.
For Fortinet environments, Fortinet Single Sign-On adds another layer of value by gathering user login information and making identity context available to FortiGate. The firewall can then apply policy with knowledge of the authenticated user or group. In larger organizations, that can reduce dependence on purely address-based rules and provide a more understandable link between business identity and network access. The platform also supports several ways of learning user identity, such as directory polling, RADIUS accounting and agent-based methods, which gives architects options when one collection method does not fit every site.
Integration planning still requires careful validation. Buyers should list each application or infrastructure component that will send or consume identity information, document the protocol it supports, confirm certificate trust requirements and identify how user groups are mapped. Federation also introduces dependencies on DNS, certificates, time synchronization and endpoint trust. FourTeck.com can help structure the pre-sales requirement so the quotation is aligned with the integration architecture, but final compatibility should always be checked against the exact software versions and vendor documentation used in the project.
FortiAuthenticator 800F Resilience, Storage and Operational Fit
Identity infrastructure becomes critical very quickly. If users cannot authenticate, a network can be healthy at the packet level and still be unusable for employees or administrators. The hardware design therefore matters beyond headline user capacity. The FAC-800F uses two 2 TB hard drives in RAID 1, includes a TPM, provides four copper Gigabit Ethernet ports plus two SFP interfaces, and ships with dual redundant 300W power supplies. Its 1RU format is designed for standard rack deployment, with front-to-back airflow.
These characteristics help build a resilient appliance, but a resilient service requires more than redundant components. Fortinet supports active-passive high availability and configuration synchronization, so organizations with stricter uptime objectives can consider two appliances. Network paths should also be redundant where required, and management access should be separated appropriately. Backups, configuration change control, certificate key protection, log retention and tested upgrade procedures are equally important parts of the operational design.
Physical planning should not be overlooked. The chassis is approximately 701 mm deep and weighs about 15 kg, so rack depth, rail compatibility and airflow clearance need to be checked. The data room should remain within the supported environmental range, and separate power feeds are preferable when the goal is to benefit from redundant supplies. For a replacement project, schedule the migration around identity-service dependencies rather than only the hardware swap. A staged cutover with tested failback is usually safer than changing all authentication paths at the same time.
What Should You Know Before Choosing This Identity Platform?
The answers below address the practical questions that usually determine whether this appliance is a good fit. They focus on scale, integration, licensing, migration and operating requirements rather than only the hardware specification.
Is this model suitable for an organization with several thousand users?
Yes, when the projected identity count fits the published capacity and the authentication architecture matches the supported services. Fortinet specifies 8,000 local and remote users as the base capacity with an upper limit of 18,000. Buyers should size for growth, not only current headcount, and should include remote users, local accounts and any future populations expected to authenticate through the appliance.
Can it integrate with an existing Active Directory environment?
FortiAuthenticator can integrate with Active Directory and LDAP-based identity stores, allowing organizations to use existing user and group data instead of recreating every account locally. The design should confirm domain topology, service permissions, group mapping, DNS and time synchronization. If several forests, remote directories or cloud identities are involved, document those relationships before quotation so the intended integration can be validated.
How should we plan FortiToken quantities?
Count the users who actually require token-based MFA and separate them by authentication method. Some users may use FortiToken Mobile, others may use hardware tokens, certificates, email or SMS OTP, or FIDO2 depending on policy. The appliance platform value does not remove the need to purchase applicable token licenses. A role-by-role MFA matrix gives procurement a much more accurate quantity.
Can this appliance support network access and application sign-on together?
It can support multiple identity functions on the same platform, including RADIUS-based network access, TACACS+ administration, SAML federation, OIDC and Fortinet SSO. The design must still account for user capacity, protocol requirements, certificates and operational ownership. Combining services can simplify administration, but it also increases the importance of high availability, change control and a documented rollback plan.
What should be checked before replacing an older FortiAuthenticator?
Record the existing model, firmware release, user database, token assignments, certificates, RADIUS and TACACS+ clients, SSO integrations, directory connectors and HA state. Then review the officially supported upgrade or migration path for the target software version. A replacement should include tested backups and a rollback procedure. Do not assume that a configuration from a much older generation can be moved without preparation.
Do we need two appliances?
Not every deployment requires a pair, but organizations that depend on the service for business-critical authentication should evaluate active-passive HA. The decision should consider outage tolerance, maintenance windows, number of dependent systems and whether alternative authentication paths exist. If HA is selected, include rack space, power feeds, network ports and licensing or support implications for both units in the project budget.
Which network ports and optics should be planned?
The hardware provides four 10/100/1000 copper RJ-45 interfaces and two SFP interfaces. Decide how many links are required for production, management, HA or segmented networks, then select compatible SFP modules and cabling where fiber connectivity is planned. Interface count alone does not determine the correct design; upstream switch redundancy, VLAN placement and routing should also be documented.
What information helps FourTeck prepare a more accurate quotation?
Share current users, expected growth, required MFA methods, token quantity, directory sources, number of RADIUS or TACACS+ clients, FortiGate integration requirements, HA preference, desired support term and delivery location. For replacement projects, include the existing appliance and firmware. This allows the quotation to reflect licensing, accessories and support rather than showing only the base hardware.
Should we choose hardware or a virtual FortiAuthenticator deployment?
Choose based on operational standards, scale, data-center strategy and lifecycle preferences. The hardware appliance gives a dedicated physical platform with defined interfaces, storage and redundant power, while virtual deployment can align with existing virtualization or cloud operations. Compare capacity, HA design, backup methods, resource allocation and support before deciding. FourTeck can help clarify hardware procurement if a physical appliance is preferred.
Business Requirements to Match Before You Buy
For a growing identity population
This model is relevant when a business needs a hardware platform that starts at several thousand users and has a published upgrade ceiling. Planning should include expected mergers, new offices, contractors and remote-access growth so that user licensing remains aligned with future requirements.
For centralized MFA rollout
A suitable option when different applications and access channels need stronger authentication under a common policy framework. Buyers should decide which users need tokens, certificates, FIDO2 or other supported factors before ordering licenses.
For identity-aware FortiGate policy
Organizations already using FortiGate can use Fortinet SSO functions to share identity context with security policy. Confirm the number of FortiGate devices, directory source and preferred user-identification method during design.
For 802.1X wired or wireless access
The RADIUS capability supports network access-control projects where users or devices must authenticate before receiving access. Buyers should check switch, wireless, supplicant and certificate compatibility as part of the rollout plan.
For high-availability identity services
Teams that cannot tolerate a single authentication appliance failure should evaluate an HA pair, redundant switching and separate power paths. Resilience is a system design decision, not only a feature of the chassis.
For a controlled migration
Buyers replacing an older appliance should confirm supported firmware migration, token reassignment, certificate handling, user database transfer and maintenance windows before purchase. A documented cutover plan reduces business disruption.
What Buyers Should Check Before Purchase
The safest procurement process is to treat identity infrastructure as a business service rather than an isolated appliance. Before the purchase request is approved, confirm exactly what the platform must authenticate, what systems it must trust and what happens if it is unavailable. This helps avoid common mistakes such as buying only the base chassis, underestimating token requirements or assuming an old configuration can be moved without migration work.
Configuration Fit
Validate current and future users, RADIUS client count, required user groups and certificate quantities. If growth may exceed the base license, include the upgrade path in the budget instead of treating expansion as an unplanned later expense.
Compatibility Check
List directories, FortiGate devices, applications, VPN systems, network switches and wireless controllers that will connect to the platform. Confirm the protocol and software version for each integration.
Licenses and Tokens
Separate appliance user licensing from the authentication factors you intend to deploy. FortiToken Mobile, hardware tokens and other services may have their own licensing or service requirements.
Availability and Warranty
Ask for current supplier availability, lead-time guidance and the exact FortiCare or warranty terms included in the offer. Do not assume that every quotation contains the same support term.
Physical Deployment
Check 1RU rack space, approximately 701 mm chassis depth, power feeds, airflow, management connectivity and SFP requirements. Include optics, patching and rack accessories in the project if needed.
Quote Preparation
Provide user counts, MFA methods, integration list, HA preference, support term and project timeline. A requirement-led quote makes it easier for technical and finance teams to compare options on the same basis.
Long-term cost should include more than the hardware purchase. Consider user-license expansion, token additions, support renewal, secondary appliance requirements, implementation effort, certificate operations and future migration. If the platform is replacing several fragmented authentication services, also account for potential operational simplification. FourTeck.com can help organize these questions before quotation so the commercial offer matches the project scope.
UAE Availability and Service Support
FourTeck.com supports business inquiries for Fortinet identity and security infrastructure from Dubai and across the UAE. For this appliance, the most useful pre-sales step is to confirm the requirement before asking for a final commercial offer. The base hardware, user licensing, authentication-token choices, support term and high-availability design can change the bill of materials considerably, so a clear specification helps prevent quotation revisions later in the buying cycle.
Availability can vary according to distributor or supplier status, order quantity, support bundle and the exact part numbers required for the project. FourTeck does not assume that a particular configuration is physically available until the supply chain has been checked for the requested order. Buyers can request current availability guidance, configuration review, quote assistance, delivery coordination and warranty information for the proposed supply.
For faster quote preparation, send the target user count, future growth estimate, MFA method, FortiToken quantity if known, directories, number of RADIUS or TACACS+ clients, FortiGate integration details, HA requirement, support period and delivery location. If the project has a planned migration date, include that as well. This information lets the commercial and technical discussion focus on the correct solution rather than only a part number.
Coverage for Dubai, Abu Dhabi, Sharjah and Ajman
Businesses in Dubai, Abu Dhabi, Sharjah, Ajman and other UAE locations can contact FourTeck.com for product availability, configuration guidance, quote assistance and delivery coordination. The same requirement-led process applies whether the appliance is for a head office, data center, campus or multi-site security project. Share the intended deployment location together with the technical specification so transport, support expectations and project timing can be reviewed as part of the quotation. Availability and delivery arrangements remain dependent on the selected part numbers, supplier status and order quantity.
Regional Availability Across GCC and Africa
FourTeck.com also supports business technology inquiries for selected projects across the GCC and Africa region. Organizations in Saudi Arabia, Qatar, Oman, Kuwait and Bahrain, as well as buyers working on projects in Kenya, Uganda and other African markets, can submit requirements for regional sourcing review. Availability, export handling, delivery options, warranty processing and support coverage can differ by country, so these points should be confirmed for the destination before an order is placed.
For cross-border projects, provide the destination country, required quantity, requested support term, preferred incoterm if applicable, project timeline and whether the equipment will be deployed in one site or distributed across several locations. Identity products also need a consistent licensing and support plan across sites, particularly when the project uses a common directory, shared MFA policy or centralized Fortinet security architecture.
FourTeck can coordinate the inquiry through its regional channels where appropriate, but country-specific commercial terms and supply conditions should be confirmed in the quotation. This approach is especially useful for procurement teams standardizing security infrastructure across several business locations while keeping the technical configuration consistent.
Other Options Buyers May Consider
Identity projects often involve a family of products rather than one isolated appliance. The right alternative depends on user scale, deployment model, authentication method and whether the project is expanding an existing Fortinet environment. The options below are useful starting points for a broader requirement discussion.
FortiAuthenticator 300F
Consider for a smaller hardware deployment where the 800F capacity is more than the project requires.
FortiAuthenticator 3000F
Suitable for organizations evaluating a significantly larger hardware platform and higher identity scale.
FortiToken Mobile
Relevant when the project uses token-based MFA for employees, administrators or remote users.
FortiGate Security Appliances
Useful when identity services are part of a wider Fortinet firewall and identity-aware policy deployment.
FortiAuthenticator Virtual Machine
Consider when the organization prefers to run identity services on existing virtualization or cloud infrastructure instead of dedicated hardware.
A smaller appliance is not automatically the better value, and a larger appliance is not automatically safer. Match the platform to the user population, RADIUS client count, certificate scale, HA requirement and expected growth. For projects already standardized on virtual infrastructure, compare the operational advantages of a VM deployment against the predictability of dedicated hardware. FourTeck can help organize these alternatives into a like-for-like quotation.
Why Business Buyers Contact FourTeck.com
Enterprise identity purchases are rarely complete when the request simply says “one appliance.” FourTeck.com approaches the inquiry by helping buyers identify the surrounding requirements that affect the final order: user licensing, token quantities, support term, high availability, optics, delivery location and any related Fortinet infrastructure. This is useful for both technical teams and procurement teams because it turns an ambiguous part-number request into a clearer commercial scope.
Review user scale, authentication methods and related items before quotation.
Prepare a commercial request that reflects the intended deployment instead of only the chassis.
Coordinate supply and delivery requirements once product availability is confirmed.
Clarify the support and warranty terms attached to the selected offer.
Identify token, firewall or alternative model requirements where they are part of the project.
Support business buyers working with multiple quantities, sites or phased rollout plans.
FourTeck does not replace the role of the customer’s security architect or Fortinet product documentation. Instead, the pre-sales process is designed to make sure the supply request contains the information needed for an accurate quotation. Buyers with an existing bill of materials can submit it directly; buyers still defining the requirement can provide the planned use case and ask for configuration assistance.
Frequently Asked Questions
What is this appliance mainly used for?
It is used to centralize identity and access management services such as user authentication, multi-factor authentication, single sign-on, RADIUS, TACACS+, 802.1X, certificate services and federation. It can also share identity information with FortiGate through Fortinet Single Sign-On. The exact functions enabled in production depend on the organization’s architecture, software version and licensing.
How many users does the FAC-800F support?
Fortinet publishes a base capacity of 8,000 local and remote users and an upper limit of 18,000 for this model. Buyers should use the projected authentication population rather than only employee headcount when sizing. User-license upgrades, token requirements and other limits should be reviewed against the current ordering guide before the purchase is finalized.
Can FourTeck help with the correct configuration?
Yes. FourTeck.com can help structure the quotation around user count, MFA method, token quantities, directory integration, RADIUS or TACACS+ clients, FortiGate requirements, high availability and support term. Final technical validation should still be performed against the exact deployment design and Fortinet documentation, particularly for migrations or complex federation projects.
Is the product available in the UAE?
FourTeck.com accepts UAE inquiries and can check current sourcing options for the requested configuration. Availability can vary based on supplier status, support bundle, user-license requirements, quantity and related accessories. A quotation request should therefore include the complete requirement so that the availability check covers the appliance and any associated items rather than only the base hardware.
Does the appliance include FortiToken licenses?
Token licensing should be treated as a separate line item unless the specific bundle being quoted explicitly includes it. The number and type of tokens depend on the authentication method selected for each user group. Buyers should define how many users require FortiToken Mobile, hardware tokens or other factors before asking for the final bill of materials.
Can it be deployed in high availability?
Fortinet supports active-passive high availability and configuration synchronization for FortiAuthenticator. Organizations that rely on the service for critical network, VPN or administrative authentication should evaluate an HA design. A second appliance also means additional rack, power, network and support considerations, so the complete resilience requirement should be included in the quotation.
What warranty or support should be requested?
Ask the quotation to state the exact FortiCare or warranty coverage, service term and any renewal requirements. Support expectations vary by organization, especially when authentication is part of a critical security service. FourTeck can provide warranty guidance for the proposed supply, but buyers should confirm the final support entitlement before approving the order.
What should be included in a bulk or project request?
Include quantity, deployment sites, required user licensing, token quantities, HA pairs, support term, preferred delivery schedule and any optics or rack accessories. If several sites share the same identity architecture, note whether the appliances are independent or part of a centralized design. This helps the quotation reflect both technical consistency and project logistics.
How do I request a quotation?
Use the FourTeck.com contact page and provide the appliance model, user count, MFA method, token requirement, identity sources, HA preference, support term, quantity and delivery location. If you already have a Fortinet bill of materials, send the part numbers as supplied by your technical team. FourTeck can then review the request and prepare current availability and commercial guidance.
Need Help Building the Right Identity Configuration?
Send FourTeck.com your user count, MFA plan, directory environment, HA requirement and support preference. We can help organize the supply requirement, check current availability and prepare a quotation for the configuration you actually need.
