FortiAuthenticator Cloud Identity Service in Africa

Give employees, administrators and approved external users a stronger way to reach business systems without building a separate authentication appliance for every location. This cloud-delivered service centralises identity checks, multi-factor authentication, single sign-on, adaptive access and certificate-related functions for hybrid environments. FourTeck helps buyers turn the service name into a practical licensing, integration and deployment plan based on user count, applications, directory design, remote-access needs and the current Fortinet product lifecycle.

Quick Product Information

Product Overview

Modern businesses rarely operate behind one office wall. Employees sign in from branch locations, homes, mobile networks and customer sites. Administrators reach firewalls, servers and cloud services from privileged consoles. Contractors may need temporary access to a specific application, while customers and partners may interact with portals that sit outside the traditional company network. In this environment, a password alone is a weak control and separate authentication tools for every system create cost, inconsistency and support pressure.

FortiAuthenticator Cloud Identity Service is designed to provide a central cloud-based identity layer for these mixed access patterns. It is built on the FortiAuthenticator engine and delivers authentication capabilities as a subscription service. The platform can support central user authentication, multi-factor authentication, adaptive authentication, passwordless FIDO2 methods, single sign-on, identity-provider and proxy functions, certificate management and integration with cloud or on-premises applications. This makes it relevant to organisations that already use FortiGate and the wider Fortinet Security Fabric, as well as businesses that need standards-based application access through technologies such as SAML and OpenID Connect.

The cloud model removes the need to purchase a dedicated authentication appliance for each deployment. That does not mean the project is automatic. Directory integration, user import, access policies, application connectors, token choice, administrator roles, recovery procedures and testing still need careful planning. The service is licensed by end user and is delivered as a single instance for each FortiCloud account rather than as a general multi-tenant platform. Existing on-premises FortiAuthenticator configurations cannot simply be transferred automatically; administrators must recreate the required configuration when moving between the appliance and cloud offerings.

For Africa buyers, the main value is not only access to a cloud subscription. It is the ability to receive practical guidance before committing to user quantities and integration work. FourTeck can help review the number of users, business applications, FortiGate remote-access design, directory sources, authentication methods, subscription term, current order codes and migration implications. This reduces the risk of purchasing a license band that does not match the real identity architecture or overlooking separate token and successor-service requirements.

Key Business Benefits

These benefits become meaningful when they are connected to business processes. A platform may support MFA, but the organisation still needs rules for lost tokens, emergency access, contractor expiry, privileged users, inactive accounts and failed sign-ins. It may support SSO, but each application must be checked for protocol compatibility and correct attribute mapping. FourTeck helps buyers address both the subscription and the practical controls that make the service useful after activation.

Product Highlights

The service is licensed annually by the number of end users. Current documented bands cover 100–499 users, 500–1,999 users, 2,000–9,999 users and 10,000 or more users. FortiCare Premium support is included in the listed cloud subscription descriptions. Additional users can be added through co-termed licensing so expiry dates can be aligned rather than creating a collection of unrelated renewal dates.

Important boundaries should be understood before purchase. FortiToken licenses are not included in the FortiAuthenticator Cloud subscription. Current documentation also explains that FortiIdentity Cloud has been decoupled from this service, so separate FortiIdentity Cloud licensing is required for designs that depend on that token service. Hardware tokens, mobile-token licenses and SMS-related requirements must therefore be included separately where needed.

The current ACCLD order codes are also moving through a lifecycle transition. Fortinet has published an end-of-order date of 30 September 2026 and points customers toward FortiIdentity Cloud order codes. A quotation should therefore confirm the requested term, whether the order is new or an extension, the required user band, the commercial cut-off and the intended long-term migration path. FourTeck will treat this lifecycle review as part of the buying discussion rather than presenting the legacy subscription as an open-ended product.

Technical Specifications and Licensing

The correct configuration is primarily a licensing and integration decision rather than a hardware-sizing exercise. Count every person who will use the service, not only the number of offices or devices. Separate employees, administrators, contractors, service accounts and external users so that the licensed population and authentication method can be mapped accurately. Then document each access target: FortiGate VPN, firewall administration, wireless access, internal applications, cloud applications and third-party portals. This list determines which protocols, tokens, connectors and policy rules are required. Buyers should also confirm the identity source, whether users are local or directory-based, the expected authentication volume, the need for SSO, and the recovery process when a user loses a token or changes a device. The lifecycle date makes this review more important because a new order must also fit the organisation’s migration timetable.

Configuration and Buyer Guidance

A useful quotation begins with an access map. List who needs access, what they need to reach, where they normally sign in, and what level of risk is attached to that access. A finance user opening an approved cloud application may need a different authentication policy from a network engineer administering a firewall. A contractor may need time-limited access, while an executive may need a simple but strongly verified mobile workflow. These differences influence token selection, policy design, support procedures and the user count placed on the order.

The buyer should also define who will operate the service after deployment. Responsibilities include adding and disabling users, approving token replacement, monitoring failed authentication, updating application certificates, handling leavers, managing administrators and maintaining recovery contacts. A cloud platform reduces infrastructure work but does not remove identity governance. FourTeck can help turn these operating questions into a clearer scope for licensing, professional services and internal ownership.

Ideal Business Use Cases

The service is particularly relevant where the organisation already has a mixed access environment and wants one identity layer rather than several unrelated point solutions. Banks may use stronger verification for staff and administrators. Hospitals may protect clinical and business applications while supporting mobile teams. Universities can address staff, student and administrator access patterns. Logistics, retail and hospitality groups can create consistent authentication across dispersed branches. Public-sector and non-government organisations may use central controls to support audit requirements and safer remote work. In every case, the exact fit depends on application support, directory design, user volumes and the organisation’s willingness to maintain identity policies after deployment.

FortiAuthenticator Cloud Identity Service: Central Authentication and MFA

Central authentication matters because a business cannot manage access well when every application keeps its own isolated user list and every branch applies different sign-in rules. The service provides a common point for validating identities and applying multi-factor controls across compatible resources. This helps IT teams build a more consistent approach to remote users, administrators and application access without deploying a separate identity appliance in each site.

MFA should be designed according to risk. High-value administrators may require a phishing-resistant FIDO2 method. General employees may use mobile tokens or push-based approval. Some environments may need hardware tokens for users who cannot carry smartphones. Other applications may only support a specific protocol or challenge flow. The subscription alone does not supply every token method, so a complete bill of materials must include the required FortiToken, hardware-token or FortiIdentity Cloud entitlement.

A successful MFA rollout also depends on user operations. The organisation needs procedures for enrolment, replacement devices, lost tokens, emergency bypass, failed authentication, time synchronisation, helpdesk verification and leavers. Pilot testing should cover ordinary users and privileged accounts, including the conditions under which access is denied. FourTeck can help buyers separate platform licensing from token licensing and define the questions that an implementation team must answer before the service is placed in production.

FortiAuthenticator Cloud Identity Service: SSO and Federation

Single sign-on can improve productivity by reducing repeated prompts across approved applications, but convenience should not be confused with weaker control. In a well-designed federation model, users authenticate through a trusted identity provider, the application receives an approved assertion or token, and access is granted according to mapped groups, claims and policy. FortiAuthenticator Cloud can support identity-provider and proxy functions for compatible applications using standards such as SAML and OpenID Connect.

Before deployment, each application should be checked for supported protocol, service-provider metadata, redirect URLs, signing certificates, required attributes, group mapping, session lifetime and logout behaviour. The identity team should decide whether the platform is the primary identity provider or whether it will broker access from another directory. Test accounts should represent different departments and privilege levels so the business can confirm that users receive only the access intended for their role.

SSO projects often fail because procurement counts licenses without counting applications, owners and configuration effort. Every application has a business owner, a technical integration method and a support process. Certificate expiry and metadata changes can interrupt access even when the subscription remains valid. FourTeck can help buyers prepare an application inventory and separate easy integrations from systems that require custom work, replacement or a different identity approach.

FortiAuthenticator Cloud Identity Service: Cloud Operations and Resilience

A hosted identity platform changes the operational model. The customer does not size a physical appliance or maintain local hardware, but identity remains a critical dependency for VPNs, applications and administrator access. The organisation should monitor service status, maintain current administrative contacts, document recovery access and understand how DNS, certificates and application caches affect authentication during a service event.

Fortinet documentation describes automated disaster-recovery health checks and failover behaviour for the cloud service. That is useful, but buyers should still design business continuity around their own applications. Critical systems may need a documented break-glass account, locally controlled emergency credentials or an approved fallback process. The objective is not to bypass security casually; it is to ensure that a cloud identity interruption does not leave authorised responders unable to restore essential services.

Operations also include backup, change control, administrator separation and configuration records. Because there is no automatic migration between an on-premises appliance and the cloud version, organisations moving platforms should export what can be documented, recreate policies carefully and test every access path. The single-instance-per-FortiCloud-account model should be considered when the company has separate subsidiaries, strict administrative boundaries or service-provider requirements. FourTeck can help identify these design questions before a license is ordered.

What Buyers Should Check Before Purchase

Before requesting a quotation, buyers should confirm whether they are purchasing for a new identity project, extending an existing cloud subscription, replacing an appliance or preparing to move to the current FortiIdentity Cloud path. The answer changes the order code, subscription term, migration effort and long-term cost. Model name alone is not enough because the service uses per-user licensing and several related Fortinet identity products have overlapping names but different entitlements.

Long-term usage cost should include more than the per-user subscription. Budget for tokens, professional services, application integration, administrator training, certificate renewal, user support, migration and future platform transition. Bulk and project buyers should also provide a phased rollout plan, because identity services often begin with administrators and remote users before expanding to all applications. FourTeck can use this information to recommend a current quote path, related services or a replacement option instead of forcing the requirement into an unsuitable legacy order code.

Africa Availability and Service Support

FourTeck supports product inquiries across Africa with assistance for license selection, user-band review, current SKU confirmation, migration planning, quote requests, deployment coordination and warranty or support-entitlement guidance. Availability can vary according to the requested subscription term, whether the order is new or an extension, the number of end users, the selected authentication method, supplier status and the Fortinet lifecycle timetable.

Because this is a cloud service, delivery is mainly commercial and digital rather than physical. The buying process still requires accurate company information, FortiCloud account planning, entitlement registration and a defined technical owner. FourTeck can help procurement and IT teams align the quotation with the deployment plan so that activation is not treated as the final step. Integration, user onboarding, token assignment, application configuration and acceptance testing remain part of the project.

For the most useful response, share the required user quantity, intended subscription term, current Fortinet products, directory platform, applications, remote-access design and target start date. FourTeck will review whether the legacy cloud subscription remains appropriate or whether a FortiIdentity Cloud alternative should be quoted.

Contact FourTeck Sales

Africa Country and Regional Coverage

Businesses across Africa, including Kenya, Uganda, Nigeria, Ghana, Tanzania, Rwanda, Ethiopia, South Africa, Zambia, Botswana, Senegal and neighbouring markets, can contact FourTeck for product availability, licensing guidance and quotation support. The same service may be used by a single headquarters, a regional group, a financial institution, a university, a healthcare network, a logistics operation or a multi-country enterprise, but the commercial and technical design should reflect how users and applications are distributed.

Regional buyers should provide the contracting country, billing currency, user quantity, application locations, data and compliance considerations, branch structure and preferred implementation timeline. FourTeck can help coordinate a consistent requirement while recognising that procurement, tax, support handling and deployment responsibilities can differ by market. Country names do not determine the license; the decisive factors are user band, term, identity design, lifecycle status and the current supplier quotation.

GCC, Middle East and Africa Availability

FourTeck Africa can support product inquiries for organisations that operate across Africa and coordinate technology purchasing with offices in the GCC and Middle East. Companies with users or procurement teams in the UAE, Saudi Arabia, Qatar, Oman and Bahrain may need one identity design that protects shared applications, remote-access gateways and administrator accounts across several regions.

A cross-regional project should clarify which entity owns the FortiCloud account, which legal entity purchases the subscription, where administrators are based, how user directories are structured and who handles renewals. The single-instance model and current product transition should be considered carefully when separate subsidiaries require different administrative boundaries. FourTeck can help buyers organise these questions and route regional requirements through the appropriate platform.

Availability, delivery coordination, support entitlement and configuration services may vary by country, user volume, order term and supplier status. Useful regional references include FourTeck Africa, FourTeck Kenya, FourTeck Uganda and FourTeck UAE.

Other Options Buyers May Consider

The right alternative depends on whether the main requirement is cloud identity, on-premises authentication, firewall access, token-based MFA or a wider identity-security programme. The following FourTeck references help buyers explore adjacent options without assuming that every project should use the same product.

FortiIdentity Cloud is the most important current successor discussion because Fortinet has announced the end-of-order milestone for the older ACCLD subscriptions. On-premises FortiAuthenticator remains relevant where the organisation wants local control, appliance or virtual deployment, certificate functions and integration managed within its own infrastructure. FortiToken may be the simpler choice where the immediate goal is only MFA for a defined set of VPN users. FourTeck can help compare these routes by requirement, not by product name alone.

Why Buyers Choose FourTeck

Identity projects combine commercial licensing with technical design. A buyer can purchase the correct brand but still receive the wrong outcome if user quantities, token methods, application protocols or migration work are misunderstood. FourTeck focuses on clarifying the requirement before the quote is finalised.

FourTeck does not assume that a cloud service removes the need for implementation planning. The team can help buyers identify missing accessories, separate license items and migration services before purchase. This is particularly important for organisations that expect token licensing to be included, assume appliance configuration can be imported automatically or overlook the product’s current commercial transition. The result is a more useful quotation and a clearer starting point for the technical team.

Frequently Asked Questions

Need Help Choosing the Right Identity Service?

FourTeck can review current availability, user bands, token requirements, migration scope, lifecycle options and the most suitable Fortinet identity path for your organisation.

Request Quote