Fortinet FortiAuthenticator Cloud in Dubai, UAE
FortiAuthenticator Cloud is Fortinet’s cloud-delivered Identity and Access Management as a Service offering for organizations that want centralized authentication, stronger user verification and identity federation across hybrid business environments. It can help IT teams apply multi-factor authentication, passwordless FIDO methods, adaptive authentication, SAML and OIDC single sign-on, user identification and certificate services without introducing another dedicated authentication appliance at each site. For UAE organizations building a zero-trust access model, protecting remote users, securing administrator access or simplifying identity services across Fortinet infrastructure, the platform provides a subscription-based route to centralized control.
Request QuoteAsk for Configuration Support
Quick Product Information
Fortinet
FortiAuthenticator Cloud
Cloud-delivered IDaaS / IAM service
Fortinet-hosted cloud service
Authentication, MFA, SSO, user identification and certificate management
FIDO, OAuth2, OIDC, SAML; integration options include RADIUS and LDAP
Subscription by end-user band
100–499, 500–1,999, 2,000–9,999 and 10,000+ users
Current listed user-band subscriptions include FortiCare Premium support
Not a hardware warranty item; subscription/support terms apply
Configuration and supplier-status dependent
Share user count, integrations, term and authentication requirements
Fast Decision Snapshot for IT and Procurement Teams
FortiAuthenticator Cloud is most relevant when an organization needs centralized identity services across a hybrid environment and prefers a Fortinet-hosted service rather than deploying another physical appliance. It is not a simple one-size license: procurement should match the correct user band, validate authentication flows and confirm which related Fortinet services are required for the planned design.
Organizations centralizing user authentication for cloud, on-premises and remote-access services.
A cloud-hosted identity layer that can reduce the need to maintain dedicated authentication infrastructure locally.
Licensed user count, identity sources, applications, SSO protocols, MFA methods and subscription term.
Hybrid work, VPN access, administrator authentication, cloud applications and Fortinet Security Fabric environments.
New FortiAuthenticator Cloud licenses no longer automatically include FortiIdentity Cloud quotas; confirm whether a separate entitlement is needed.
License-band review, quotation support, renewal planning and configuration discussion for UAE business requirements.
Product Overview
Modern organizations rarely keep every user, application and workload inside one office network. Employees may authenticate to cloud applications, VPN services, administrative portals, internal systems and business platforms from different locations and device types. That creates an identity problem: security teams need to verify who a user is, apply appropriate authentication controls and provide practical access without forcing every application team to build a separate authentication process. FortiAuthenticator Cloud is designed to address this problem as a centrally managed, cloud-delivered identity and access service.
Fortinet describes the service as Identity and Access Management as a Service. Its functions include passwordless FIDO authentication, multi-factor authentication, adaptive authentication, OAuth2 authorization, OpenID Connect, SAML, user identification and certificate management. It can also work with established identity sources and authentication environments through mechanisms such as Active Directory-related identification, RADIUS, LDAP and SAML integration. The purpose is not simply to add a second authentication prompt. The broader value is to create a consistent identity layer that can support access decisions across multiple services while integrating closely with Fortinet environments.
For businesses already using FortiGate or other Fortinet products, that integration can be especially relevant. Fortinet states that the cloud service is natively integrated with the Fortinet Security Fabric and supports identity-driven access scenarios, including local and remote FortiGate users. At the same time, buyers should plan the deployment around their actual identity architecture rather than assuming every application will connect in the same way. Some services may use SAML, some OIDC, some RADIUS, and others may depend on directories, APIs or certificate workflows.
The subscription model is user-based. Current Fortinet documentation lists bands for 100–499, 500–1,999, 2,000–9,999 and 10,000 or more FortiAuthenticator Cloud end-users. This makes user-count accuracy an important procurement input. UAE buyers should also check current subscription duration, renewal dates, any co-terming requirement and whether separate FortiIdentity Cloud licensing is needed for their design. FourTeck.com can help translate those technical details into a clearer bill of materials and quotation request so procurement teams are not ordering solely by a familiar product name.
Key Business Benefits
◆ Centralized authentication control
A centralized identity layer helps reduce fragmented authentication practices across applications, remote-access services and network resources. Rather than managing independent identity logic in every system, IT teams can build a more consistent approach to user verification and authorization. That consistency matters when staff move between offices, cloud services and remote environments, because access rules can be designed around identity instead of only around network location.
◆ Stronger user verification
Multi-factor and adaptive authentication can add protection beyond passwords, which is valuable for VPN access, privileged administration and access to sensitive applications. Fortinet also supports passwordless FIDO methods, giving organizations another path for modern authentication programs. The business benefit is stronger confidence in the identity behind a login while still allowing the security team to select methods appropriate to user groups and application risk.
◆ SSO for hybrid applications
SAML and OIDC-based federation can help organizations provide single sign-on across compatible cloud and on-premises services. A well-designed SSO environment can reduce repeated logins, simplify the user experience and give IT a clearer place to manage identity relationships. Buyers should still inventory applications before purchase, because protocol support and application integration details determine how much of the environment can be brought into the planned sign-on model.
◆ Cloud-delivered operational model
Fortinet hosts the service, reducing the need to deploy and maintain a dedicated authentication appliance for this specific cloud service. That can be useful for organizations with distributed branches or limited local infrastructure teams. Cloud delivery does not remove the need for identity architecture, integration planning or operational ownership, but it can shift attention from appliance maintenance toward policy, onboarding, authentication design and lifecycle management.
◆ Integration with existing identity sources
Businesses rarely start with a blank directory. FortiAuthenticator Cloud can integrate with existing identity information and external authentication systems, allowing organizations to reuse established sources rather than rebuilding every account. This can make migration more practical, but the exact directory, synchronization, federation and network requirements should be reviewed before deployment so the new service fits current workflows without creating parallel identity silos.
◆ Scalable user-band procurement
Licensing is structured around end-user bands, which gives procurement teams a clear starting point for sizing. The practical task is to count the population that must be licensed today and anticipate growth over the subscription term. Organizations near a band boundary should discuss expansion plans before ordering, because acquisitions, new branches, contractors or additional protected applications can change the required population and future renewal position.
◆ Better fit for zero-trust programs
Zero-trust initiatives depend on reliable identity, not just perimeter location. By combining user identification, stronger authentication and identity-aware integration, the service can support a move toward more deliberate access decisions. Buyers should view it as one element of a wider security architecture that may also include endpoint posture, network segmentation, application controls, privileged-access management and security monitoring.
Product Highlights That Matter Before You Buy
Supports modern methods including passwordless FIDO, OAuth2, OIDC and SAML-based authentication workflows.
Fortinet lists multiple MFA options, including FortiToken Mobile, email and SMS, with adaptive authentication capabilities.
Can identify users through multiple sources and communicate identity information for identity-based policy use in supported Fortinet environments.
Provides certificate-management capabilities for organizations that need certificates as part of secure access and identity workflows.
Designed for close use with the Fortinet Security Fabric, including authentication scenarios involving FortiGate and other supported products.
Fortinet states that the managed service is hosted in Fortinet data centers and monitored continuously.
The key purchasing point is that feature availability does not eliminate integration dependencies. A SAML-capable application still needs the correct federation configuration. RADIUS-based access requires network reachability and proper client definitions. Directory integration requires a review of identity sources, groups and lifecycle processes. Certificate workflows need naming, trust and renewal planning. For that reason, a good FortiAuthenticator Cloud project starts with an application and identity inventory rather than with a license quantity alone.
Buyers should also note a current licensing change documented by Fortinet: after FortiIdentity Cloud 4.1.0, new FortiAuthenticator Cloud licenses are decoupled from FortiIdentity Cloud and no longer automatically include FortiIdentity Cloud quotas. Organizations planning features that depend on FortiIdentity Cloud should confirm whether a separate license is required. Existing entitlements purchased before the change continue according to their applicable terms until expiry. This distinction is important for renewal and migration planning.
Technical Specifications and Licensing Reference
| Item | Verified Product Detail |
|---|---|
| Brand | Fortinet |
| Product | FortiAuthenticator Cloud, formerly known as FortiTrust Identity |
| Service Type | Identity and Access Management as a Service (IDaaS) |
| Hosting | Fortinet-hosted cloud service; no dedicated onsite appliance is required for this deployment model |
| Authentication | Passwordless FIDO, OAuth2 authorization, OIDC and SAML; MFA and adaptive authentication are supported capabilities |
| Identity Sources / Integration | Supports multiple user-identification sources and interoperability with RADIUS, LDAP and SAML authentication systems; exact integration is configuration dependent |
| Single Sign-On | Identity federation for compatible cloud and on-premises applications using modern authentication protocols |
| Certificate Management | Certificate creation/signing and certificate-management functions are supported |
| User Band SKU: 100–499 | FC2-10-ACCLD-511-02-DD |
| User Band SKU: 500–1,999 | FC3-10-ACCLD-511-02-DD |
| User Band SKU: 2,000–9,999 | FC4-10-ACCLD-511-02-DD |
| User Band SKU: 10,000+ | FC5-10-ACCLD-511-02-DD |
| License Term | Current Fortinet documentation describes the service as subscription-based and notes one-year license validity; specific purchasable term/SKU should be confirmed at quotation |
| Support | Current user-band SKU descriptions include FortiCare Premium support |
| Expansion | Co-termed licensing can be used to add users to an existing FortiAuthenticator Cloud license |
| FortiIdentity Cloud | New FortiAuthenticator Cloud licenses after FortiIdentity Cloud 4.1.0 do not automatically include FortiIdentity Cloud quotas; separate licensing may be required |
| Availability | Based on selected license, term, user band, supplier status and country |
Choosing the correct configuration starts with the licensed population rather than the number of devices. Count the end users who require the service, then map how they will authenticate: VPN, administrator access, wireless or network access, cloud application SSO, internal application SSO, certificate-based access or other supported workflows. Confirm the directory or identity source that owns each population. Next, verify the protocols each target system supports and identify any dependencies such as FortiToken Mobile, SMS credits, certificates, network reachability or a separate FortiIdentity Cloud subscription. Finally, align the subscription term with budgeting and renewal cycles. This process reduces the risk of buying an appropriate user band but missing a technical dependency that prevents the intended deployment.
Configuration and Buyer Guidance
A cloud identity service touches many systems, so procurement should involve both the security team and the people who manage applications, directories and remote access. Before requesting a quote, prepare a simple deployment worksheet. It should state how many users need licensing today, expected growth during the subscription period, which applications require SSO, which users need MFA, whether passwordless authentication is in scope, and how contractors or guest identities are handled. This produces a more accurate licensing discussion than a request based only on employee headcount.
How many end users?
Identify the licensed population and growth forecast. Organizations close to a band boundary should discuss the next band and co-terming options.
Which identity sources?
Document Active Directory, LDAP sources, cloud identity providers, local accounts and any other systems that hold authoritative user data.
Which applications and protocols?
List SAML, OIDC, OAuth2, RADIUS, LDAP and certificate-dependent systems so compatibility can be assessed before rollout.
Which authentication methods?
Define where MFA, adaptive authentication, passwordless FIDO, FortiToken Mobile, email or SMS methods are expected to be used.
What is the migration plan?
If replacing an existing identity service, identify current RADIUS clients, SSO integrations, certificates, enrollment processes and fallback methods.
What related subscriptions?
Confirm whether FortiIdentity Cloud, SMS credits, token-related entitlements or other services are separately required for the desired design.
Share this information with FourTeck.com along with the preferred term, billing requirements and deployment location. The team can use it to help narrow the appropriate licensing band and prepare a more relevant quotation discussion. For technically complex migrations, buyers should also plan a pilot or staged rollout, especially where authentication is business-critical. Identity systems can affect VPN access, application login and administrator workflows, so change windows, rollback procedures and emergency-access accounts should be part of the implementation plan.
Ideal Business Use Cases
Hybrid workforce authentication
Businesses with employees working from offices, homes and customer sites can use centralized authentication controls to apply consistent identity verification to compatible remote-access and application services. The design should distinguish employees, contractors, administrators and service accounts so policies reflect risk rather than treating every login identically.
FortiGate VPN and administrator access
Organizations using FortiGate can incorporate strong authentication into local and remote user scenarios, including VPN and administrative access. This is useful where a password-only login would create unacceptable risk. User groups, token method, emergency access and remote-access policy should be validated before migration.
Cloud application single sign-on
Teams supporting many SaaS applications can use SAML or OIDC federation where compatible applications support those standards. This can improve user experience and give identity teams a more consistent control point. Buyers should inventory each application’s federation capability and licensing requirements rather than assuming all SaaS platforms behave the same way.
Identity-aware network policy
For environments that need user identity to influence network policy, FortiAuthenticator Cloud can identify users through supported sources and pass identity information into compatible Fortinet systems. This can help policy designers move beyond IP-address-only controls, although successful operation depends on accurate identity mapping and well-defined groups.
Passwordless access initiatives
Security teams evaluating FIDO-based passwordless authentication can use the platform as part of a broader modernization program. Passwordless does not mean policyless: device enrollment, account recovery, fallback methods, user training and application compatibility still require planning. A staged rollout to a controlled user group is usually easier to manage than an immediate organization-wide change.
Certificate-supported access
Organizations that use certificates for secure access can benefit from centralized certificate management functions. This may be relevant to VPN, network access, devices or other supported workflows. Buyers should document certificate lifetimes, trust chains, renewal procedures and ownership so certificate operations do not become an unplanned administrative burden.
These use cases can exist in the same organization, but they should not all be activated at once without design work. A practical project often starts with a high-value requirement such as VPN MFA, then expands into SSO, adaptive controls or certificate use after administrators are familiar with the platform. That staged approach can also reveal whether the licensed user population or related service dependencies need adjustment before a wider rollout.
FortiAuthenticator Cloud Authentication and Access Control
The strongest reason to evaluate this platform is its role as a central authentication service for a mixed business environment. User verification is often fragmented: a VPN may use one source, an internal application another, and cloud applications may each have separate accounts. Fragmentation increases administrative effort and makes it harder to apply consistent controls when employees change roles, leave the company or need elevated access. A centralized authentication layer can reduce that inconsistency by tying access to known identities and approved authentication methods.
Fortinet supports several modern methods. Multi-factor authentication can require a second factor beyond the primary credential, while adaptive authentication can introduce decisions based on context and policy. Passwordless FIDO offers another route for organizations that want to reduce dependence on reusable passwords. SAML and OIDC support identity federation for compatible applications, and OAuth2-related functions support modern authorization scenarios. These technologies serve different purposes, so the buyer should not treat them as interchangeable checkboxes. The correct method depends on the application, user population and threat model.
A VPN administrator might prioritize MFA reliability and recovery procedures. A SaaS application owner may care more about SSO and group mapping. A privileged administrator may need stricter authentication than a general user. A help desk may need clear procedures for lost phones, new devices and account recovery. When these operational questions are addressed during design, stronger authentication is less likely to create disruptive support issues after go-live.
For procurement teams, the implication is simple: the subscription should be selected with an authentication architecture in mind. Share the intended use cases with FourTeck.com instead of requesting only a user-band price. That allows configuration discussions to include the required authentication methods, related token services, integration protocol and rollout approach. It also helps avoid a common mistake in identity projects: licensing enough users but overlooking the surrounding operational requirements that determine whether those users can authenticate successfully.
FortiAuthenticator Cloud SSO and Hybrid Identity Integration
Single sign-on is often discussed as a convenience feature, but for a business it is also an identity-governance issue. When every application has its own authentication system, users accumulate passwords, administrators repeat onboarding tasks and deprovisioning becomes harder to audit. Federation allows a compatible application to trust an identity provider rather than maintaining a separate authentication process. FortiAuthenticator Cloud supports SAML and OIDC, which are widely used for enterprise federation and modern cloud applications.
The buyer’s first task is to classify applications. Identify which use SAML, which use OIDC, which depend on RADIUS or LDAP, and which cannot be federated without an upgrade or different license. Then document the attributes and groups each application needs. An application may require an email address, department code, role or other claim to make authorization decisions after authentication. A technically successful SSO connection can still create access problems if the wrong attributes are mapped.
Hybrid environments add another layer. Existing directories and identity systems may remain authoritative for users even while authentication services move to the cloud. FortiAuthenticator Cloud can integrate with established sources and external identity systems rather than requiring an immediate directory replacement. This can support phased modernization, but administrators should define where accounts are created, where group membership is managed and which system is responsible for disabling access when a user leaves.
For UAE organizations with multiple offices or a mix of cloud and on-premises applications, this integration flexibility can make a cloud IAM project more realistic. However, network reachability, firewall rules, certificates, DNS, time synchronization and application-side federation settings still matter. Before quotation, identify the top applications that must work on day one. FourTeck.com can then help frame the licensing request around a real deployment scope, while the customer’s technical team can validate each integration against current Fortinet and application documentation.
FortiAuthenticator Cloud Licensing, Scale and Lifecycle Planning
Identity services grow with the organization. A company may start with one remote-access use case and later protect more applications, administrators, contractors and branch users. Fortinet therefore licenses FortiAuthenticator Cloud by end-user bands. Current documentation lists four bands: 100–499, 500–1,999, 2,000–9,999 and 10,000 or more. The exact orderable SKU depends on the band and duration component. Co-termed licenses can also be used to add users to an existing subscription.
Sizing should be based on the population that will actually consume the service, not only on the number of full-time employees. Contractors, temporary staff, external administrators or other identities may need consideration depending on the deployment. At the same time, not every account in a directory necessarily represents a licensed active user in the same way. Buyers should confirm Fortinet’s current licensing definitions for their scenario and keep a documented count that procurement and security teams can reconcile at renewal.
Renewal planning is particularly important because authentication is a business-critical service. Fortinet documentation notes that the service is subscription based and that licenses must be activated within the applicable period. Organizations should record registration codes, entitlement ownership, renewal dates and the internal team responsible for acting before expiry. A renewal should also be treated as a design checkpoint: user count may have changed, application coverage may have expanded, and related services may now be required.
One of the most important current lifecycle points is the separation from FortiIdentity Cloud. New FortiAuthenticator Cloud licenses after the FortiIdentity Cloud 4.1.0 change no longer include FortiIdentity Cloud quotas automatically. Buyers planning identity features across both services must therefore confirm the bill of materials rather than relying on older bundle assumptions. FourTeck.com can help procurement teams review the requested user band, current SKU family, related services and renewal timing so the quote reflects the current product structure.
What Should You Know Before Choosing This Cloud Identity Service?
The questions below reflect the practical decisions security teams and procurement departments need to resolve before they can turn a product name into a workable authentication design and an accurate subscription request.
Is it suitable for a business that already uses FortiGate?
Yes, it can be a strong fit because Fortinet designs the service to integrate with the Fortinet Security Fabric and supports authentication scenarios involving FortiGate users, including remote access and administrator use. The exact setup still depends on FortiGate configuration, user sources, authentication method and policy requirements, so buyers should document the current firewall and VPN design before rollout.
Which user band should we select?
Select the band that covers the FortiAuthenticator Cloud end-user population for the planned service. Fortinet currently lists 100–499, 500–1,999, 2,000–9,999 and 10,000+ bands. Count users who will participate in the deployment and include expected growth. If you are close to a boundary, discuss future users and co-terming before the first purchase.
Can it work with our existing directory?
It is designed to integrate with existing identity information and supports interoperability with systems such as LDAP, RADIUS and SAML environments. Fortinet also documents user identification from sources that include Active Directory-related methods. Compatibility should be confirmed for the exact directory architecture, network path, group structure and identity synchronization method used by your organization.
Do we need FortiIdentity Cloud as well?
Not automatically, and buyers should not assume it is bundled. Fortinet documents that new FortiAuthenticator Cloud licenses are decoupled from FortiIdentity Cloud after the FortiIdentity Cloud 4.1.0 change. If your design needs FortiIdentity Cloud functions or quotas, a separate entitlement may be required. Confirm this explicitly during licensing review.
Can we use passwordless authentication?
Yes. Passwordless FIDO is a documented capability. A successful passwordless project also needs enrollment, compatible authenticators or devices, application support, recovery procedures and a plan for users who cannot complete the preferred method. Procurement should therefore discuss the authentication design and user-experience requirements, not just confirm that FIDO appears on the feature list.
What should we check when replacing an older authentication service?
Inventory every RADIUS client, SAML service provider, OIDC application, certificate dependency, VPN policy and fallback login before migration. Also document emergency administrator access and account-recovery procedures. The replacement project should be staged so critical systems can be tested individually and rolled back if necessary rather than changing all authentication paths in one maintenance window.
Which related services or credits may be required?
That depends on the chosen authentication methods. FortiToken-related options, SMS usage, separate FortiIdentity Cloud licensing and application-side requirements can affect the final design. If SMS is planned, discuss how credits are purchased and monitored. If mobile push or token codes are planned, confirm the appropriate Fortinet token workflow and current licensing terms.
How should we plan for future growth?
Forecast user growth, additional applications, new branches and contractor populations over the subscription period. Fortinet supports co-termed licensing for adding users to an existing license, which can help align additional capacity with the current renewal date. Organizations should still review band boundaries early so expansion does not become an urgent licensing task during a business rollout.
What information gives FourTeck a better quotation brief?
Provide the current and projected user count, required term, existing Fortinet products, identity sources, target applications, VPN requirements, desired MFA methods, SSO protocols, passwordless plans, certificate needs and any current FortiIdentity Cloud entitlement. Also include the billing entity and deployment country. These details make it easier to identify the correct subscription family and related items.
Business Requirements to Match Before You Buy
For businesses moving MFA to a managed cloud service
A suitable fit when the goal is to centralize stronger authentication without maintaining a dedicated onsite authentication appliance. Confirm user band, factor choice, VPN/application integrations and recovery procedures before ordering.
For teams standardizing SSO across mixed applications
Useful where target applications support SAML or OIDC federation. Buyers should prepare an application list and required user attributes so each integration can be validated instead of assuming universal SSO compatibility.
For Fortinet-based remote access projects
A practical option for organizations already using FortiGate and looking to strengthen remote user or administrator authentication. Confirm the existing FortiGate version, VPN design, directory source and desired token method.
For buyers replacing legacy identity infrastructure
Plan a staged migration. Inventory RADIUS clients, federated applications, certificates, emergency accounts and user-enrollment procedures before switching production authentication to the cloud service.
For organizations expecting headcount growth
Check the current user band against the growth forecast. Co-termed licenses can add users to an existing entitlement, but band planning in advance is easier than reacting when a rollout reaches its licensed capacity.
For procurement comparing current and older bundles
Confirm the latest FortiAuthenticator Cloud structure rather than relying on historical FortiTrust Identity assumptions. In particular, determine whether a separate FortiIdentity Cloud subscription is required for the intended solution.
What Buyers Should Check Before Purchase
Identity projects often fail at the edges rather than at the headline feature. The product may support MFA, SSO and federation, yet a deployment can still be delayed by an inaccurate user count, an unsupported legacy application, missing SMS planning, untested emergency access or confusion about which subscription owns a particular feature. Before quotation, buyers should review the complete authentication journey from user enrollment to login, recovery, deprovisioning and renewal.
Correct license band
Count the users who will consume the service and identify growth. Match the request to the current Fortinet band and duration rather than copying an older SKU from a previous quote.
Compatibility check
Validate directories, RADIUS clients, SAML applications, OIDC applications, certificates and Fortinet product versions. A feature in the service still requires compatible endpoints and correct configuration.
Subscription and support
Confirm the current subscription term, FortiCare support inclusion, activation requirements and renewal date. Record entitlement ownership so renewal does not depend on one administrator’s mailbox.
Related service dependencies
Check whether FortiIdentity Cloud, SMS credits, token-related licensing or application-side subscriptions are required. New FortiAuthenticator Cloud licenses should not be assumed to include FortiIdentity Cloud quotas.
Migration and rollback
For replacements, document the existing authentication flows and maintain tested break-glass access. Roll out in stages so critical VPN, administrator and application logins can be validated before wider migration.
Long-term operational cost
Consider subscription renewals, user growth, SMS consumption where applicable, administrative effort and any related services. The lowest initial license quantity may not represent the most practical lifecycle plan.
Bulk or multi-entity deployment
Large groups should define whether users belong to one identity realm, multiple business units or separate environments. Administrative ownership and user grouping can affect how the service is operated even when licensing is centrally purchased.
Quote preparation
Provide user count, term, current Fortinet estate, target applications, identity sources, authentication methods, migration status and any renewal reference. Better input produces a more precise licensing discussion.
FourTeck.com can help buyers review these commercial and technical inputs before a quotation is finalized. The objective is to reduce the chance of selecting the wrong user band, overlooking a related service, or discovering during deployment that an important application uses a different authentication protocol than expected. The final architecture remains configuration dependent, and complex deployments should be validated against the current Fortinet administration guides and release notes.
UAE Availability and Service Support
FourTeck.com supports Fortinet software and cloud-service inquiries for businesses in Dubai and across the UAE. For FortiAuthenticator Cloud, the main procurement task is identifying the correct current subscription rather than checking a physical appliance specification. Availability can vary by user band, term, supplier status, entitlement type and order quantity, so the sales process should start with a licensing brief.
FourTeck can assist with quotation preparation, user-band selection, configuration discussion, renewal planning and commercial coordination. Buyers can also ask for guidance on which technical details should be confirmed with their implementation team, including identity sources, SSO protocols, VPN integration, authentication methods, token-related requirements and separate FortiIdentity Cloud needs. Where a project involves migration from an older deployment, sharing the existing SKU or entitlement reference can help clarify whether the request is a new subscription, renewal, expansion or co-termed addition.
Because this is a cloud service, there is no physical server shipment to size or rack for the core service. However, the customer’s network and application environment still needs the connectivity and configuration required for authentication flows. Warranty handling is therefore different from a hardware purchase: the relevant commercial discussion concerns subscription entitlement and the applicable FortiCare support included with the ordered license. Current terms should be confirmed on the quotation.
Business Coverage Across the Emirates
Businesses in Dubai, Abu Dhabi, Sharjah and Ajman can contact FourTeck.com for subscription availability, license-band guidance and quote assistance. The same purchasing questions apply whether the deployment supports one office, a distributed workforce or a multi-site environment: define the licensed user population, current identity sources, target applications, desired authentication controls and renewal requirements. Delivery coordination for a cloud entitlement typically centers on ordering, registration details and subscription activation rather than physical logistics. Project timelines should therefore include procurement approval, entitlement registration, technical configuration and a controlled rollout window.
Regional Availability for GCC and Africa Projects
FourTeck.com also supports business technology inquiries for selected regional markets. Organizations operating across the UAE, Saudi Arabia, Qatar, Oman, Kuwait and Bahrain may need a common identity-access design but different purchasing, billing or support arrangements by country. Similarly, project teams supporting Kenya, Uganda and other Africa-region operations may want to standardize authentication methods while sourcing through the appropriate regional channel.
For multi-country projects, prepare one technical requirement document and then separate commercial requirements by legal entity, billing location, user population and deployment schedule. This makes it easier to determine whether the same licensing band is appropriate across the group or whether subscriptions need to be structured differently. Availability, registration, tax treatment, support handling and delivery of subscription entitlements can vary by country and supplier status, so none should be assumed until confirmed.
Regional buyers can use FourTeck.com for the main Dubai-based inquiry channel, or explore FourTeck Kenya, FourTeck Uganda, FourTeck Africa and FourTeck Kuwait where relevant. A shared technical specification across regions can simplify comparison and reduce inconsistent identity policies between business units.
Other Fortinet Options Buyers May Consider
FortiAuthenticator Cloud is one part of a broader Fortinet identity and access portfolio. The right adjacent product depends on whether the requirement is cloud-hosted authentication, token-based MFA, an appliance/VM deployment, privileged access or network security enforcement. The cards below are useful starting points for building a complete requirement, not automatic substitutes.
FortiAuthenticator
Consider the broader FortiAuthenticator appliance/VM family when deployment control, standalone architecture or non-cloud form factors are part of the requirement.
FortiToken Mobile
Relevant where mobile token codes or push-based authentication are part of the chosen MFA user experience.
FortiPAM
Suitable for organizations whose requirement extends beyond general user authentication into privileged-account and privileged-access management.
FortiGate Firewalls
A related choice when identity-aware authentication is being designed alongside secure internet access, VPN, segmentation or branch firewall requirements.
Before choosing an alternative or companion product, define the problem first. A team that needs passwordless SSO for cloud applications has a different requirement from a team that needs privileged session control or an onsite authentication appliance. FourTeck.com can help buyers map those requirements to the relevant Fortinet product families and request the correct quotation path.
Why Business Buyers Contact FourTeck.com
Cloud software procurement can look simple because there is no hardware configuration, but identity products are highly dependent on licensing structure and integration design. FourTeck.com approaches the purchase as a business requirement rather than only as a part-number transaction. That means the sales conversation can include the user population, subscription term, current Fortinet estate, renewal situation, applications being protected and the authentication methods the organization plans to deploy.
Help identifying the appropriate user band and current SKU family based on the requirement provided.
Support for converting user count, term and related requirements into a clearer commercial request.
Buyer-focused review of identity sources, SSO protocols, MFA methods, FortiGate use and related service dependencies.
Assistance distinguishing new purchase, renewal, expansion and co-termed additions based on the available entitlement information.
A Dubai-based inquiry route for business buyers needing commercial coordination across UAE requirements.
Guidance when the project also requires FortiToken, FortiGate, FortiPAM or another Fortinet identity/security component.
FourTeck.com does not need to turn every inquiry into the same bundle. An organization using only SAML SSO has a different bill of materials from one using VPN MFA, SMS, mobile tokens and certificate workflows. By sharing the actual deployment goals, buyers give the team enough context to avoid generic quoting and identify questions that should be resolved before purchase.
Frequently Asked Questions
What is FortiAuthenticator Cloud used for?
It is a Fortinet-hosted Identity and Access Management as a Service platform used to centralize authentication and identity-related controls across compatible cloud and on-premises environments. Documented capabilities include MFA, adaptive authentication, passwordless FIDO methods, SAML and OIDC federation, user identification and certificate management. Organizations commonly evaluate it for stronger remote access, SSO, identity-aware security and centralized user-verification requirements.
Is the service available for UAE business requirements?
FourTeck.com can support UAE inquiries and quotation requests. Availability is not presented as guaranteed stock because this is a subscription entitlement whose commercial availability depends on the selected user band, term, supplier status and ordering conditions. Share the required user count, term and deployment details so the team can check the current licensing option and prepare the appropriate quote process.
How is FortiAuthenticator Cloud licensed?
Fortinet licenses the service by FortiAuthenticator Cloud end-user bands. Current documentation lists bands covering 100–499, 500–1,999, 2,000–9,999 and 10,000 or more users. Exact orderable SKU and duration should be confirmed when requesting a quotation. Co-termed licenses can be used to add users to an existing subscription, which can help align expansion with the current renewal cycle.
Does it support multi-factor and passwordless authentication?
Yes. Fortinet documents multi-factor authentication, adaptive authentication and passwordless FIDO capabilities. The platform also supports FortiToken Mobile, email and SMS MFA options in documented service specifications. The correct authentication method depends on user experience, application compatibility, device availability, risk level and recovery procedures. Related tokens, credits or services should be confirmed as part of the implementation design.
Can FourTeck.com help choose the correct configuration?
Yes. For a useful configuration discussion, provide the licensed user population, Fortinet products already deployed, identity sources, target applications, VPN requirements, desired MFA methods, SSO protocols and any existing FortiAuthenticator or FortiIdentity Cloud entitlement. FourTeck can help turn those details into a better-defined licensing request and highlight related items that may need to be confirmed before ordering.
Does a new license include FortiIdentity Cloud?
Buyers should not assume that it does. Fortinet documents that new FortiAuthenticator Cloud licenses are decoupled from FortiIdentity Cloud after FortiIdentity Cloud 4.1.0, so new licenses no longer automatically include FortiIdentity Cloud quotas. If your planned design uses FortiIdentity Cloud capabilities, confirm the required separate entitlement during the quote and architecture review.
Can it provide SSO for cloud applications?
It supports identity federation using SAML and OIDC for compatible applications and services. Whether a specific application can use the planned SSO flow depends on that application’s federation support, required attributes and configuration. Buyers should provide a list of priority applications and their supported protocols so the rollout can be designed around verified integrations rather than a generic assumption that all applications support the same SSO method.
What happens when the organization adds more users?
Review the licensed band and current active population before expanding the rollout. Fortinet documents co-termed licensing for adding FortiAuthenticator Cloud users to an existing license. This can align added users with the existing entitlement, but procurement should confirm the current SKU and commercial terms. Planning growth early is especially important for organizations approaching the top of a licensed user band.
What should we prepare before deployment?
Prepare an identity and application inventory, network-connectivity requirements, authentication methods, user groups, certificates where relevant, enrollment procedures, account-recovery process, emergency-access plan and staged migration schedule. If replacing an existing service, include all RADIUS clients, SSO applications and VPN dependencies. Authentication is business critical, so a pilot group and rollback plan are advisable for complex deployments.
How do I request a FortiAuthenticator Cloud quote?
Contact FourTeck.com and share the user count, required subscription term, current Fortinet products, target applications, directory environment, MFA method, SSO requirements and country of deployment. If you are renewing or expanding, include the existing SKU or entitlement reference if available. That information helps the team identify whether the request is a new subscription, renewal, co-termed expansion or a broader identity solution requirement.
Need Help Planning the Right Identity Subscription?
Send FourTeck.com your user count, subscription term, current Fortinet environment, identity sources, target applications and authentication goals. The team can help review the commercial requirement, check current licensing options and prepare a UAE quotation request without assuming a one-size configuration.
