Product Overview

Identity has become one of the most important control points in business security. A firewall can block unwanted traffic and an application can protect its own data, but both still rely on the assumption that the person signing in is genuine. Password theft, phishing, reused credentials, compromised email accounts and unmanaged administrator access can undermine otherwise strong infrastructure. A cloud identity service addresses this problem by adding stronger verification and consistent access policy before users reach sensitive systems.

FortiIdentity Cloud is designed to provide identity and access management as a service. It supports centrally managed multi-factor authentication for FortiGate environments and other supported applications, while also offering single sign-on and identity federation functions for SAML and OIDC applications. The platform can act as a local identity provider, or it can proxy access to a remote SAML or OIDC provider where the organisation already has an established identity source. This flexibility allows the service to fit into a new deployment, a Fortinet-focused network or a broader hybrid identity design.

The service is particularly relevant to organisations that do not want to deploy, power, patch and maintain a dedicated authentication appliance. Administration takes place through a web interface, giving authorised teams a central place to manage users, authentication methods, realms, integrations and usage. FortiToken Mobile support can simplify the user experience through one-time passwords and push approval, while supported options such as SMS, email OTP, hardware tokens and FIDO2 passkeys allow the authentication method to be matched to risk, user type and device readiness.

For a branch network, the first use case may be protecting remote-access VPN users or FortiGate administrators. For a growing enterprise, the project may include SSO for cloud applications, adaptive policy enforcement, third-party application access and multiple user groups. A managed service provider may need a platform that can scale across many Fortinet products and customer environments. In every case, the correct purchase depends on user count, licence tier, subscription period, SMS usage, application compatibility and deployment ownership.

FourTeck supports buyers by reviewing these practical details before quotation. Instead of treating the product as a generic cloud licence, the buying discussion should document who will authenticate, what they will access, which authentication factors are acceptable, how users will be enrolled, which applications need federation and who will handle renewals. This approach helps security, procurement and finance teams understand the full requirement and reduces the risk of ordering the wrong user tier or overlooking implementation work.

Key Business Benefits

The value of cloud identity management is measured by the business risks it reduces and the operational work it simplifies. The following benefits explain how the service can support daily users, IT teams and security governance.

Product Highlights

The service includes mobile-token capabilities designed to simplify user verification through push approval or one-time passwords. It can also support SMS and email-based authentication where those methods fit the organisation’s policy, although SMS credit use and regional rates should be reviewed carefully. Hardware-token support may be relevant for administrators, users without compatible smartphones or environments that require a separate physical factor.

A major strength is that the service is not limited to one authentication pattern. It can protect FortiGate access, operate as an identity provider for supported applications, proxy federation to another provider and apply adaptive conditions. Exact capabilities depend on the current service version, configured realm, application integration and licence entitlement. Buyers should confirm their priority workflows during scoping rather than assume that every application will behave identically.

Technical Specifications and Licensing Reference

Configuration and Buyer Guidance

A good cloud identity purchase begins with an access map. Procurement should not ask only for a licence name, because the useful design depends on users, applications, authentication methods and operational ownership. The following questions help technical and commercial teams prepare a complete request.

The quote should state the required user quantity, annual term, protected systems, expected SMS consumption, token method, integration scope, support expectation and rollout schedule. Buyers should also clarify whether they need licensing only, guided configuration or a broader deployment service. This information allows FourTeck to review the order codes and prepare a proposal that matches the real identity project.

Ideal Business Use Cases

The service can support several identity scenarios, but each deployment should begin with a defined access risk and a measurable operational goal. The following use cases show where cloud-managed authentication can provide practical value.

Other valid scenarios include securing sensitive finance applications, protecting third-party support access, standardising authentication after a merger and introducing stronger access controls without installing another local appliance. The platform should be selected because it fits the authentication journey, not simply because it is cloud based. FourTeck can help compare the requirement with on-premises FortiAuthenticator and focused FortiToken options where a different model may be more appropriate.

FortiIdentity Cloud — Multi-Factor and Passwordless Authentication

Passwords remain common because they are familiar and widely supported, but they are also copied, reused, phished and shared. Multi-factor authentication adds another test of identity, making a password alone less useful to an attacker. The service supports several authentication approaches, including FortiToken Mobile, mobile one-time passwords, push approval, SMS or email OTP, hardware tokens and FIDO2 passkeys. This range gives security teams the ability to match the factor to the user and the risk.

A remote employee with a managed smartphone may find push approval convenient. A network administrator may need a phishing-resistant passkey or separate token. A user in an area with inconsistent mobile data may rely on a time-based OTP. SMS can be useful in selected situations, but cost and delivery reliability must be considered. The strongest choice is not automatically the most complex method; it is the one that users can operate correctly and the support team can recover safely.

Passwordless authentication can improve security and usability when the target applications, devices and browsers support the required standards. It reduces the need to type a reusable secret and can resist common phishing techniques. However, the rollout still needs registration, device trust, replacement procedures and account recovery. Security teams should begin with a controlled group, test failure conditions and document how users regain access without weakening the policy.

FourTeck can help buyers define user groups, preferred methods, expected token quantities and implementation responsibilities before the licence order is prepared. This makes the commercial request reflect the actual authentication programme rather than a simple per-user count.

FortiIdentity Cloud — Single Sign-On and Identity Federation

Single sign-on is valuable because users often work across many applications during the same day. Separate credentials for every service increase password reuse, support calls and account-removal work. Federation allows an application to trust an identity provider, so approved users can access resources through a consistent sign-in process. The service supports local identity-provider and identity-provider proxy roles for SAML and OIDC scenarios, creating flexibility for organisations with new or existing identity infrastructure.

A local IdP design can make the service the authentication authority for supported applications. An IdP proxy design can route authentication to another SAML or OIDC provider while applying the required access flow. This can be useful when different business units, partners or cloud services already depend on separate identity platforms. The architecture must clearly state which provider owns the user record, where groups are managed and how claims are translated.

Federation improves convenience, but it also concentrates dependency. A change to certificates, metadata, group mappings or claims can affect many connected applications. Organisations should maintain expiry calendars, test environments, change approval and emergency access. Application owners need to participate because an identity team cannot validate business workflows alone. Deprovisioning is equally important: a user who leaves the organisation should lose access consistently across connected systems.

Before quotation, buyers should provide the list of applications, federation standards, user groups, current identity provider and intended sign-in journey. FourTeck can use this information to clarify whether licensing, configuration assistance and migration planning should be included in the proposal.

FortiIdentity Cloud — Adaptive Policy and Central Management

Not every authentication event carries the same risk. A user signing in from a familiar environment may present a different risk profile from an administrator attempting access through an unusual device or location. Adaptive authentication allows policy to consider context and require additional verification when conditions justify it. This can improve security without forcing the most demanding sign-in process on every user at every moment.

Adaptive rules should be understandable and testable. Security teams need to define what conditions matter, which actions are triggered and how legitimate users recover when a policy blocks access. Too many rules can create confusing behaviour and help-desk pressure, while rules that are too broad may not reduce risk. A practical deployment begins with a small number of clear controls linked to real business threats.

Central management supports this work by giving administrators an online place to configure MFA, review usage and maintain authentication services. Daily usage information and subscription notifications can help the organisation monitor licence consumption and renewal timing. Cloud administration is especially useful for distributed teams, but access to the management portal itself should be protected with strong administrator controls and limited privileges.

Operational ownership is essential. One team should maintain policies, another may approve access, and the help desk may support enrolment and recovery. FourTeck can help buyers include these responsibilities in the deployment discussion so the service has a sustainable operating model after the initial configuration.

What Buyers Should Check Before Purchase

Before requesting a quote, buyers should confirm the complete access requirement rather than selecting a licence only by product name. The correct order depends on the number of identities, intended authentication factors, application integrations, subscription period and support scope. The checklist below helps procurement and technical teams avoid missing a user tier, renewal responsibility or deployment task.

Buyers comparing cloud and on-premises options should also consider control, internet dependency, integration depth and internal skills. An on-premises FortiAuthenticator appliance may suit organisations that need dedicated local identity services, while FortiToken may fit a narrower MFA requirement. FourTeck can help review these alternatives so the selected approach matches the business environment rather than being chosen only by licence price.

Africa Availability and Service Support

FourTeck supports product inquiries across Africa with assistance for licence selection, user-count review, authentication-method planning, quote preparation, delivery coordination and warranty or support guidance. Availability can vary according to the current supplier position, selected subscription period, required quantity, destination and implementation scope. Buyers should request a current commercial response rather than assume that an online reference reflects the final order.

A useful inquiry should include the number of licensed identities, preferred annual term, protected FortiGate devices or applications, expected authentication methods, approximate SMS use and desired rollout date. It should also state whether the organisation needs licensing only or assistance with configuration, federation, user enrolment, adaptive policy, testing and administrator handover.

FourTeck can help check the appropriate order code and identify related requirements such as hardware tokens, additional SMS credits, on-premises identity alternatives or Fortinet firewall integration. Commercial terms, support entitlement and delivery coordination should be confirmed in writing on the final quotation.

Contact FourTeck Sales

Africa Country and Regional Coverage

GCC, Middle East and Africa Availability

FourTeck Africa can support identity-service inquiries for organisations operating across Africa while coordinating wider regional requirements through selected FourTeck platforms. Businesses with project stakeholders in the UAE, Saudi Arabia, Qatar, Oman and Bahrain may need a common authentication policy for users, administrators and applications across several offices.

Cross-regional planning should standardise user definitions, authentication methods, application ownership, support processes and renewal dates. One region may host the primary applications while another manages security operations or procurement. The service design should account for internet dependency, help-desk coverage, local user communication, data policy and the process for replacing lost devices or tokens.

Availability, delivery options, warranty handling and configuration support can vary by country, supplier status, subscription tier and order quantity. Buyers can review FourTeck Africa, the Kenya support platform, the Uganda service platform and the UAE procurement desk for the most relevant regional contact path.

Other Options Buyers May Consider

Identity security works best when the cloud service, firewall, local authentication platform and reporting tools are selected as one architecture. The following related options may be useful depending on the required control level, deployment model and existing Fortinet environment.

The correct alternative depends on the objective. A focused FortiToken deployment may be enough for a small group of VPN users. A FortiAuthenticator appliance may be better when local RADIUS, certificates or dedicated identity infrastructure are required. A cloud service is attractive where rapid central management and reduced appliance overhead matter. FourTeck can help buyers review these paths without assuming that one model fits every organisation.

Why Buyers Choose FourTeck

A cloud identity licence affects security policy, user experience and recurring cost, so buyers need more than a line item. FourTeck focuses on the practical buying questions that help organisations prepare a workable order and deployment plan.

FourTeck also helps buyers understand when a different product may be more suitable. Cloud identity is not automatically the answer for every environment. Some organisations need local authentication appliances, hardware tokens, privileged access control or broader network access management. A useful supplier should help clarify those differences before the order is approved.

Frequently Asked Questions