Fortinet FortiToken Cloud in Africa
FortiToken Cloud, now offered under the FortiIdentity Cloud name, gives organisations a centrally managed way to strengthen login security, control access to business resources and move beyond password-only protection. It is designed for security teams that need practical multi-factor authentication across Fortinet environments and compatible applications without placing another authentication appliance at every branch. FourTeck helps buyers understand the current licensing model, confirm whether a request is for a new deployment or an existing subscription transition, review user quantities, and prepare the right regional quotation.
🔒 Multiple Authentication Methods
◆ License Sizing Guidance
↗ Africa Quote Support
Request Quote
Check Africa Availability
Quick Product Information
Fortinet
FortiToken Cloud
FortiIdentity Cloud
Cloud identity and access management subscription
MFA, passwordless access, identity provider and application access control
FortiGate environments, hybrid workforces, multi-branch organisations and compatible applications
Annual, per-user subscription; selected model dependent
Current license and transition options must be confirmed
Africa with wider regional enquiry coordination
User quota, realms, integrations, SMS usage and support term are configuration dependent
Product Overview
Modern business systems often hold valuable financial records, customer information, operational data and remote administration functions behind a simple username and password. That approach becomes increasingly difficult to defend when employees work from different locations, contractors require limited access, administrators connect to security infrastructure remotely, or the same identity is used across several applications. FortiToken Cloud was created to help organisations add a stronger proof of identity to the login process and manage that protection from a central cloud service. Fortinet has since expanded and renamed the service FortiIdentity Cloud, combining multi-factor authentication with broader identity and access management capabilities.
The platform can support different authentication experiences rather than forcing every user into a single method. A business may use FortiToken Mobile for one-time passwords or push approval, email or SMS codes for selected workflows, physical tokens for users who cannot rely on smartphones, and FIDO2 passkeys for phishing-resistant passwordless access. The exact methods, integrations and entitlement depend on the current subscription and deployment design. This flexibility matters because a field technician, finance manager, remote executive and data-centre administrator may have different devices, risk levels and connectivity conditions.
Central management is especially valuable for organisations with several FortiGate devices or a mixed application environment. Instead of treating every branch as a separate authentication island, the security team can work toward consistent user enrolment, policy assignment, reporting and subscription visibility. FortiIdentity Cloud also provides identity provider and proxy capabilities for SAML and OpenID Connect applications, allowing the service to participate in broader single sign-on and access-control designs. It can therefore be considered not only as a token platform but as a cloud-managed identity layer for approved business resources.
For Africa buyers, the central question is no longer simply “How many tokens do we need?” The correct purchase depends on whether the organisation is renewing an existing FortiToken Cloud service, moving to current FortiIdentity Cloud licensing, adding users to an active account, deploying new FortiGate authentication, or integrating third-party applications. FourTeck supports the buying process by reviewing user numbers, current Fortinet assets, required authentication methods, subscription timing, SMS expectations and rollout goals. This prevents a quotation based only on an old product name and helps the buyer obtain a license path that matches the actual security requirement.
Key Business Benefits
The value of cloud-managed authentication is measured by how effectively it reduces access risk while remaining manageable for users and administrators. The following benefits connect the platform’s capabilities to practical business outcomes.
🔒 Stronger Login Assurance
Requiring another factor reduces dependence on passwords that may be guessed, reused, phished or exposed. The organisation can ask users to prove possession of a mobile device, hardware token or passkey before access is granted, creating a more dependable identity check for remote connections and sensitive applications.
◆ Central Administration
A cloud portal gives security teams a common place to manage users, authentication methods, connected applications and subscription usage. This can reduce the operational burden created by separate branch-by-branch processes and gives administrators a clearer view when staff join, leave, change roles or need token replacement.
✓ Flexible User Experience
Different users can be matched with suitable methods, including mobile OTP, push confirmation, email or SMS codes, supported hardware tokens and FIDO2 passkeys. A thoughtful method mix helps the business improve security without creating unnecessary friction for employees who have different devices, locations or accessibility needs.
↗ Scalable Subscription Model
Current FortiIdentity Cloud licenses use annual user quotas and can be expanded as the organisation grows. Proper sizing lets a buyer begin with an appropriate tier, plan for new staff or branches, and avoid purchasing on a device count that does not reflect the number of people who will actually consume the service.
⚙ Simplified Deployment Planning
Because the core service is cloud managed, businesses can avoid deploying a dedicated local authentication appliance for every location. The project still requires careful integration and policy work, but infrastructure planning can be simpler for distributed organisations that want central control and consistent authentication.
● Better Policy Consistency
Central identity controls help teams define who can access a resource, which factor is required and how login context should influence the decision. Consistent policies are useful for businesses operating multiple offices, outsourced support arrangements or hybrid environments where access cannot be protected by the office perimeter alone.
✓ Improved Procurement Control
The annual quota model encourages buyers to document active users, expected growth, SMS consumption and renewal dates. This turns authentication from an informal collection of tokens into a managed business service with clearer ownership, budgeting and lifecycle planning.
Product Highlights
Administrators can manage authentication and access functions through a web interface rather than relying only on isolated local token assignments.
Supported designs may use FortiToken Mobile, push approval, OTP, email, SMS, hardware devices and phishing-resistant FIDO2 passkeys.
Identity provider and proxy capabilities can support SAML and OIDC applications, with SCIM integration available for suitable identity workflows.
The service is designed to work with FortiGate and other supported Fortinet products, helping businesses extend strong authentication into network and security operations.
One of the most important highlights is the service’s broader role beyond generating one-time codes. Buyers may still recognise the FortiToken Cloud name because it was strongly associated with central token management. The current FortiIdentity Cloud platform extends that concept with identity provider functions, single sign-on support and contextual access policies. This makes it relevant to projects where the business wants a coherent access layer rather than a collection of unrelated second-factor tools.
The platform also supports a practical progression from conventional MFA to passwordless methods. A business can maintain mobile OTP or push approval for many users while introducing FIDO2 passkeys for administrators, executives or applications that require stronger resistance to phishing. The correct design depends on user devices, browser and application support, recovery processes, and the organisation’s tolerance for helpdesk overhead.
Licensing is another technical highlight that requires attention. Current annual subscriptions are based on user quotas rather than a simple one-time token count. Available tiers cover different user ranges, and included SMS credits are linked to the subscribed users. SMS credit consumption varies by destination country, so a project that plans to use SMS heavily should estimate regional usage instead of assuming that every message consumes the same amount. FourTeck can help translate these operational details into a clearer bill of materials and renewal plan.
Technical Specifications and Service Characteristics
| Area | FortiToken Cloud / FortiIdentity Cloud Detail | Buyer Note |
|---|---|---|
| Brand | Fortinet | Confirm registration under the intended FortiCloud account. |
| Current Product Name | FortiIdentity Cloud, formerly FortiToken Cloud | Legacy and current requests may use different license SKUs. |
| Service Type | Cloud identity and access management subscription | No dedicated authentication hardware is required for the cloud service itself. |
| License Model | Annual per-user quota, configuration dependent | Current licensing begins at the applicable minimum user tier and scales by quota. |
| Current User Ranges | 25–499, 500–1,999, 2,000–9,999, and 10,000+ user tiers | Final SKU selection depends on the required quantity and account status. |
| Authentication Methods | Mobile OTP, push approval, email OTP, SMS OTP, supported hardware tokens and FIDO2 passkeys | Method availability depends on configuration and connected resource. |
| Identity Functions | Local IdP, IdP proxy, single sign-on and adaptive authentication capabilities | Application and federation design should be validated before purchase. |
| Standards and Integration | SAML, OIDC, SCIM and supported Fortinet integrations | Confirm the exact application, protocol and identity source. |
| Fortinet Compatibility | FortiGate, FortiAuthenticator and other supported products or applications | Relevant assets should normally be associated with the correct FortiCloud account. |
| SMS Entitlement | Current annual plans include an allocation linked to user quota; extra credit packs are available | Actual credit use varies by destination country or region. |
| Management | Web-based cloud portal with usage and subscription visibility | Administrative roles and operational ownership should be planned. |
| Support | Support entitlement varies by active license and current Fortinet terms | FourTeck can help buyers review the quoted support level. |
| Availability | Subject to current licensing, migration path, region and order quantity | Request confirmation before planning activation dates. |
How to choose the correct subscription
Start with the number of named end users who will authenticate through the service, not only the number of firewalls or applications. Then identify each protected resource, the authentication experience required, the current FortiCloud account structure and the planned subscription start date. A company with 120 employees may need fewer than 120 licenses if only selected teams use the protected applications, while a contractor-heavy environment may need more careful quota planning because users are regularly created, removed and replaced.
Buyers should also estimate the proportion of authentications that will use SMS. Mobile push, app-generated OTP and FIDO2 may reduce recurring SMS usage, but the choice must suit device availability and user conditions. If the business already owns FortiToken Cloud licenses, share the current serial number, expiry date, user quota and connected Fortinet products so that the correct renewal or FortiIdentity Cloud transition route can be checked.
Configuration and Buyer Guidance
A successful authentication project starts with identity and workflow information, not only a part number. The buyer should map who needs access, what those users will access, how they connect and what should happen when a device is lost or a user cannot complete the usual authentication step. This creates a design that is secure during normal operation and recoverable during real support incidents.
How many active users?
Count employees, administrators, contractors and external users who will consume the service. Separate current need from expected growth so the quotation can balance immediate cost with expansion requirements.
Which resources need protection?
List FortiGate VPN access, administrative portals, SaaS applications, internal web systems and other connected resources. Each may use a different integration method or policy.
Which factors suit the workforce?
Review smartphone availability, mobile data conditions, email access, SMS reliability, hardware-token requirements and browser support for passkeys. Avoid selecting a method that users cannot consistently complete.
What identity source is used?
Document whether users come from a Fortinet environment, cloud directory, local directory or another identity provider. Federation and provisioning requirements affect the implementation plan.
How will recovery work?
Plan token replacement, lost phones, changed numbers, emergency access and administrator recovery. A secure service can still cause disruption if support procedures are undefined.
Who owns renewal?
Assign responsibility for quota monitoring, expiry alerts, purchase approval and renewal timing. Authentication should not become a last-minute procurement emergency.
For an existing deployment, provide the current FortiToken Cloud subscription details and explain whether the goal is to add users, renew service, replace an expiring license or migrate to the current product. For a new project, provide a simple access matrix showing user groups, protected applications, required factors and administrative owners. FourTeck can use this information to help narrow the appropriate subscription tier and identify additional items such as SMS credit packs, hardware tokens, FortiGate licensing, implementation assistance or related identity services.
Ideal Business Use Cases
Fortinet FortiToken Cloud is relevant wherever access must be verified more reliably than a password alone. The best use cases are those with a clear resource, defined user group and manageable enrolment process. It should be introduced as part of an access-control plan rather than as an isolated application installed without policy ownership.
Secure Remote Access
Remote employees, administrators and support partners can be required to complete a second factor before reaching VPN resources. This is valuable when login attempts originate outside the office network and passwords may be exposed through phishing or reused credentials.
Multi-Branch FortiGate Environments
Businesses operating several firewalls can benefit from a more central approach to user authentication and token administration. The design can support consistent access rules while still allowing each branch to protect its own local resources.
Privileged Administrator Protection
Network, cloud and security administrators have access that can change policies or expose sensitive systems. Strong authentication, carefully controlled recovery and phishing-resistant methods can reduce the risk associated with these high-impact accounts.
Application Single Sign-On
Organisations with compatible SAML or OIDC applications can use identity provider functions to simplify access while applying central authentication rules. This may reduce separate passwords and improve control over which users are allowed into each resource.
Contractor and Project Access
Temporary users often need controlled access for a defined period. A central service can support enrolment and removal workflows, provided the business sets clear ownership, expiry dates and least-privilege policies.
Hybrid Workforce Identity
When employees work from offices, homes, customer sites and mobile locations, network position is no longer a reliable sign of trust. Context-aware access and multiple factor choices help the organisation apply stronger identity verification across changing work patterns.
Other suitable environments include schools protecting administrative portals, healthcare organisations securing remote support accounts, financial teams controlling access to sensitive applications, managed service providers administering customer infrastructure, and regional enterprises standardising authentication across subsidiaries. The project should always account for privacy obligations, user training, recovery procedures and the operational impact of the chosen factor. FourTeck can help relate the product capability to the buyer’s actual access scenario before the order is prepared.
FortiToken Cloud Centralised MFA Management
Centralised management is one of the most practical reasons to consider a cloud identity service. A decentralised token deployment can become difficult to maintain when each firewall or application has its own user list, enrolment process and recovery method. Administrators may not know which accounts remain active, who owns a token, whether a former contractor still has access, or when a subscription requires attention. A shared management layer helps the security team apply common operating procedures and improve visibility across the environment.
The cloud portal supports administration from authorised locations with an internet connection. This is useful for regional IT teams that support multiple offices but do not have staff at every branch. User enrolment, token assignment, application configuration and usage review can be handled through a consistent interface. Daily usage information and subscription notifications can also assist with capacity and renewal planning. These functions do not remove the need for internal governance; they make it easier to execute that governance when responsibilities are clearly assigned.
A good management design separates day-to-day helpdesk duties from high-risk administrative changes. Support staff may need to assist with mobile activation or replace a lost device, while only security administrators should change federation settings, policies or connected applications. The organisation should define administrative roles, audit expectations and emergency access before onboarding a large user population. It should also decide how user records are created and removed, especially when staff data comes from another directory or provisioning system.
For buyers, central management affects both subscription sizing and implementation effort. A quotation should consider not only the number of users but also the number of realms, applications, Fortinet devices, administrator roles and identity sources. FourTeck can help collect this information and distinguish a straightforward FortiGate MFA project from a broader identity-provider deployment. That distinction matters because the same product family can support both simple and advanced use cases, but the project plan, skills and testing requirements will be different.
FortiToken Cloud Authentication Choice and User Experience
Authentication security works only when users can complete it reliably and support teams can recover it safely. Fortinet’s platform supports several methods because no single factor is ideal for every role or environment. Mobile push can offer a convenient approval experience for smartphone users. App-generated OTP can continue to work when the mobile device has no network connection after activation. Email or SMS codes may suit specific onboarding or fallback scenarios, while hardware tokens can support users who cannot use personal phones. FIDO2 passkeys can provide stronger protection against phishing for compatible applications and devices.
The buyer should avoid choosing solely by convenience. SMS delivery can depend on mobile coverage, roaming, destination routing and available credits. Email codes depend on access to the email account that may itself be part of the login problem. Push approval can be misused if users approve prompts without checking context. Hardware tokens require physical distribution and replacement planning. Passkeys require compatible endpoints, browsers and recovery processes. A balanced design matches the factor to the risk and gives the helpdesk a secure way to handle exceptions.
User communication is part of deployment. Employees should know why the service is being introduced, how to enrol, what a legitimate prompt looks like, how to report unexpected requests and what to do when changing phones. Administrators should test common failure cases before rollout, including lost devices, expired activation messages, wrong phone numbers, users without smartphones and travel to areas with limited connectivity. Small pilot groups can reveal practical issues that are difficult to identify from a technical configuration checklist alone.
FourTeck can help buyers identify the planned factor mix during quotation so that licensing, SMS credits, compatible tokens and rollout support are considered together. This avoids a common procurement gap where the subscription is purchased but the business has not decided how real users will authenticate. A clear user-experience plan improves adoption, reduces support calls and helps the security team enforce stronger access without creating unnecessary disruption.
FortiToken Cloud Integration, Federation and Growth
The current FortiIdentity Cloud service can operate as more than a second-factor provider. Local identity provider and identity provider proxy capabilities allow it to participate in SAML and OpenID Connect application access. SCIM support can help with suitable user provisioning workflows, while adaptive policies can consider login context. These functions are useful when a business wants to connect several applications to a central identity layer, but they require careful planning around domains, certificates, redirect URLs, identity claims and user lifecycle processes.
Integration should begin with a list of applications and the protocol each one supports. Some applications may work directly with SAML, others with OIDC, and older systems may need a different approach. The buyer should identify which system is the authoritative source of user data, which attributes are required by each application and how group membership will control access. Test accounts should be used before production migration so that sign-in, logout, account disablement and recovery can be validated without locking out essential users.
Growth planning also matters. Current licenses are stackable and can be co-termed, allowing additional user capacity to align with an existing subscription expiry in appropriate cases. That can simplify renewal administration for a growing organisation, but the exact commercial treatment depends on the active account and current licensing rules. Buyers should maintain a forecast for workforce growth, new branches, planned applications and contractor programmes rather than waiting until the available quota is exhausted.
Businesses replacing an existing FortiToken Cloud subscription should provide the current serial number, expiry date, user count and connected resources. New buyers should provide the planned identity source, application list and rollout schedule. FourTeck can then help determine whether the request is a straightforward annual user license, an expansion, an SMS credit requirement or a wider deployment that may benefit from implementation assistance. This makes the quotation more accurate and gives technical teams a clearer path from purchase to production use.
What Buyers Should Check Before Purchase
Before requesting a quote, buyers should confirm the required configuration, usage environment, compatibility needs, support expectations and subscription timing. The FortiToken Cloud name may refer to an existing service that needs renewal or to a new requirement that should now be quoted under FortiIdentity Cloud. FourTeck can help review these details so the selected license matches the business requirement instead of choosing only by a familiar product name.
Configuration Fit
Confirm the active user count, expected growth, required authentication methods and subscription term. State whether users are employees, contractors, customers or administrators because lifecycle and risk requirements may differ.
Compatibility Check
List FortiGate models, FortiAuthenticator systems, FortiCloud accounts, identity directories and applications that will connect. Include software versions where available so integration assumptions can be reviewed.
Availability and Support
Confirm whether the requirement is new, renewal, expansion or migration. Share the desired activation date and current expiry date. Support and transition options can vary with the active subscription and chosen SKU.
Quote Preparation
Provide user quantity, company country, protected resources, preferred factors, FortiCloud account status, existing serial numbers and required delivery timing. This reduces back-and-forth during licensing review.
SMS Planning
Estimate how many users will rely on SMS and where their numbers are registered. Credit use can vary by country, and additional credit packs may be needed for SMS-heavy workflows.
Deployment Readiness
Decide who will administer the service, how users will be enrolled, how helpdesk recovery will work and which pilot group will test the deployment before broad rollout.
Renewal and Long-Term Cost
Budget for annual user subscriptions, possible SMS credits, compatible hardware tokens, deployment services and internal administration. Record the renewal owner and approval lead time.
Alternative Route
Where an existing product, application or user workflow is not compatible, ask FourTeck to review FortiAuthenticator, device-managed FortiToken, FortiGate-native options or another suitable identity design.
Bulk and project orders should include a phased rollout plan. Large organisations may need separate user realms, multiple administrators, application migration stages and a temporary overlap with existing authentication. Providing this information early helps FourTeck prepare a more useful quotation and identify technical questions before the subscription clock begins.
Africa Availability and Service Support
FourTeck supports cloud identity and authentication enquiries across Africa with assistance for product clarification, license sizing, quotation preparation, renewal planning and deployment coordination. Availability can vary according to whether the buyer needs a legacy FortiToken Cloud transition, a current FortiIdentity Cloud subscription, additional user quota, SMS credits, compatible tokens or related Fortinet products. The correct commercial route should be confirmed before an activation date is promised.
Regional buyers can share their required number of users, current FortiCloud account details, existing Fortinet serial numbers, protected applications and preferred authentication methods. FourTeck can help organise that information for a licensing review and indicate where configuration-dependent choices remain. This is particularly useful for businesses that receive a technical request from an IT team but need procurement-friendly guidance before approving the purchase.
Delivery coordination for a cloud subscription mainly concerns electronic licensing, account registration and project timing. Hardware tokens or related appliances may involve separate logistics. Warranty guidance applies to any physical items in the solution, while subscription support depends on the active Fortinet entitlement. Buyers should request confirmation for their exact country, user quantity and timeline rather than relying on a generic availability statement.
Africa Country and Regional Coverage
Businesses across Africa, including Kenya, Uganda, Nigeria, Ghana, Tanzania, Rwanda, Ethiopia, South Africa, Zambia, Botswana, Senegal and nearby regional markets can contact FourTeck for product availability, licensing guidance and quotation assistance. The team can help buyers review suitable user tiers, renewal requirements, authentication methods, deployment considerations and related Fortinet products based on the actual business use.
Country context matters most when the solution will use SMS authentication, when physical tokens require shipment, or when project implementation involves several branches. Mobile network conditions, destination-based SMS credit consumption, customs arrangements for hardware and local support expectations can affect the final plan. The subscription itself is cloud delivered, but successful adoption still depends on user readiness, identity integration and a realistic rollout schedule.
FourTeck does not treat country names as separate versions of the same product. A single product requirement can serve a regional organisation while the quotation accounts for the locations, user groups and operational conditions involved. Buyers with a multi-country deployment should provide a user breakdown by region, identify where SMS will be used and state whether administrators will manage all locations centrally.
GCC, Middle East and Africa Availability
FourTeck Africa can support product enquiries for organisations across Africa while also guiding regional technology requirements through selected FourTeck platforms serving GCC and Middle East markets. Businesses with operations in the UAE, Saudi Arabia, Qatar, Oman, Bahrain and African countries may need a single identity design that protects users across several legal entities, branches and application environments.
Availability, license registration, support handling and deployment coordination can vary by country, subscription type, selected configuration and order quantity. A regional project should document the FortiCloud account owner, billing entity, user distribution, administrator model and required activation date. Where SMS authentication is planned, the project should also estimate country-based usage because message credits can be consumed differently by destination.
Buyers can use the FourTeck Africa platform for African enquiries, review regional support through FourTeck UAE, or consult the relevant country platform such as FourTeck Kenya and FourTeck Uganda. The goal is to coordinate the enquiry through the most suitable regional channel without making unsupported claims about local inventory or activation timing.
Other Options Buyers May Consider
The best identity solution depends on where authentication will be validated, how many devices or applications are involved and whether the buyer prefers a cloud service or customer-managed platform. The following related options can help buyers frame the discussion with FourTeck.
FortiIdentity Cloud
The current name and licensing route for organisations seeking cloud-managed Fortinet identity, MFA, SSO and access-control capabilities.
FortiAuthenticator
A suitable discussion point for organisations that need a dedicated authentication platform, central identity services or customer-managed deployment options.
FortiToken Mobile
Mobile token licensing may suit device-managed FortiGate or FortiAuthenticator deployments where the organisation does not require the full cloud identity service.
FortiGate Security Appliances
FortiGate platforms can provide native authentication functions and are a common protected resource in Fortinet MFA projects.
FIDO2 Security Keys
Physical FIDO2 keys may be considered for phishing-resistant access, privileged users or staff who need a hardware-backed authentication method.
Cybersecurity Deployment Services
Implementation assistance can help with policy design, application integration, user enrolment, pilot testing and operational handover.
These options are not direct substitutes in every case. FortiAuthenticator may be preferred when the organisation wants a managed appliance or virtual platform under its own control. Device-managed FortiToken Mobile can be suitable for simpler deployments, while FortiIdentity Cloud is better aligned with central cloud administration and broader application access functions. FourTeck can help compare the operational model rather than making a decision only on the visible license cost.
Why Buyers Choose FourTeck
Authentication subscriptions can appear simple on a quotation, yet the commercial line item may hide important questions about user quota, current product naming, account registration, SMS use, compatible systems and renewal timing. FourTeck approaches the requirement as a business technology purchase that must connect procurement information with the technical deployment.
Guidance on the relationship between the requested FortiToken Cloud name and the current FortiIdentity Cloud offer.
Help identifying user quantities, authentication methods, connected resources and related license requirements.
A procurement-friendly process for turning the technical requirement into a clearer request for current pricing and availability.
Consideration of enrolment, integration, pilot testing, recovery, administrator roles and rollout timing.
Support for enquiries involving Africa locations, regional offices, electronic licensing and related hardware logistics.
Attention to renewal ownership, quota growth, migration planning and support entitlement rather than only the initial order.
FourTeck supports small and medium businesses, enterprise procurement teams, system integrators, institutions and regional project buyers. The team can help match the request to a suitable product route and identify where more technical confirmation is needed. This is useful when a buyer has received an abbreviated request such as “FortiToken Cloud for 100 users” but does not yet know whether the environment needs a renewal, migration, new FortiIdentity Cloud license, additional SMS credits or implementation services.
The approach remains factual. Availability is confirmed during the quotation process, support depends on the selected entitlement, and final compatibility depends on the actual environment. Buyers receive practical guidance without unsupported promises about inventory, immediate activation or universal integration.
Frequently Asked Questions
What is FortiToken Cloud used for?
It is used to strengthen access security by adding multi-factor authentication and central identity controls for supported Fortinet systems and business applications. The service can help protect VPN access, administrator logins, application sign-on and other resources that should not rely on a password alone. Fortinet now uses the FortiIdentity Cloud name for the current service.
Is FortiToken Cloud still the current product name?
Fortinet currently calls the service FortiIdentity Cloud. Existing customers and older procurement records may still use the FortiToken Cloud name. A quotation should confirm whether the requirement is for renewal, expansion, migration or a new subscription, because the current license SKUs and user tiers may differ from older FortiToken Cloud offers.
Which authentication methods can the service support?
Supported designs can include FortiToken Mobile OTP, push approval, email OTP, SMS OTP, compatible hardware tokens and FIDO2 passkeys. The best method depends on the protected application, user devices, security risk, network availability and support process. Buyers should define the planned factor mix before finalising the subscription and rollout plan.
Can FourTeck help select the correct user license?
Yes. FourTeck can help buyers review active users, expected growth, subscription status, current Fortinet assets, SMS use and application integrations. This information helps determine the appropriate current licensing route. Final SKU selection and commercial terms remain subject to the current Fortinet offer and the buyer’s account details.
Does it work with FortiGate?
Fortinet provides out-of-the-box MFA integration with FortiGate, making the service relevant for VPN and other supported access scenarios. The exact design depends on the FortiGate configuration, software version, FortiCloud account and authentication workflow. Buyers should share their firewall model and intended use so compatibility can be reviewed.
Are SMS credits included?
Current annual FortiIdentity Cloud subscriptions include an SMS credit allocation linked to the user quota, and additional SMS credit packs are available. Credit consumption can vary according to the country or region of the destination number. A buyer planning frequent SMS authentication should estimate usage and consider alternative methods where appropriate.
Is the subscription available across Africa?
FourTeck supports enquiries across Africa, but availability and activation timing must be confirmed for the selected license, quantity and account. Electronic subscription delivery may be combined with separate logistics if hardware tokens or appliances are required. Buyers should provide the deployment country and desired start date when requesting a quote.
What information is needed for a quotation?
Provide the number of users, existing FortiToken Cloud or FortiIdentity Cloud serial details, expiry date, FortiCloud account status, protected applications, FortiGate or FortiAuthenticator models, preferred authentication methods, expected SMS use, deployment country and required activation date. New projects should also describe the identity source and rollout schedule.
Can businesses request bulk or multi-country licensing?
Yes, organisations can submit a project requirement covering large user quantities or several operating locations. The request should include user distribution, billing entity, FortiCloud account ownership, administrator structure, SMS countries and rollout phases. FourTeck can help coordinate the enquiry and identify the current tier or expansion path that should be reviewed.
What happens when the subscription approaches expiry?
The organisation should begin renewal planning early, confirm the active user quota, identify growth and verify whether the account is moving from older FortiToken Cloud licensing to current FortiIdentity Cloud SKUs. Assign an internal renewal owner and allow time for commercial approval, license registration and any required migration testing.
Need Help Choosing the Right Cloud Identity License?
FourTeck can help you review current product naming, user quota, authentication methods, Fortinet compatibility, renewal status, SMS requirements and regional deployment details. Share your existing subscription information or new project scope to receive a configuration-aware quotation.
Reviews
There are no reviews yet.