We performed a comparison between Fortinet FortiToken and Microsoft Entra ID based on real PeerSpot user reviews.
Find out in this report how the two Authentication Systems solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."The product provides secure access to our internal server."
"The solution is pretty solid."
"The integrated Fortinet security with the app that allows you to easily do the two-factor authentication is most valuable."
"The solution is simple and similar to Google Authenticator. It follows time-based authentication. We use it for hardware and software in one environment. The tool offers simple and fast authentication for SSL."
"I believe FortiToken is the simplest to implement."
"Its ease of use is most valuable. It is simple to use and can be deployed out-of-the-box. It is quite a mature product with all the required features."
"FortiToken is available in a soft or hard token factor, so there's some flexibility in that. Beyond that, I would say it is a stable solution that has worked for us."
"I love the push-button authentication on FortiToken Mobile. It's also great that the soft token automatically reloads the OTP at intervals, so I always have a fresh code to enter."
"The performance is good."
"If you want to replicate a website at the frontend in Azure, it's very easy to do it globally."
"The most valuable feature is that it is very easy to implement, you don't need a lot of effort to set up the solution. This is the most advantageous point, that you can do anything on Azure without taking too much time."
"It's a quite comprehensive solution and it scales quite well within our required scale as well, which is very useful."
"Active Directory itself is the best feature it has. It also gives us a single pane of glass for managing user access."
"We can have an audit and we can easily audit logs."
"The single sign-on of the solution is the most valuable aspect."
"Conditional Access is a helpful feature because it allows us to provide better security for our users."
"Fortinet support has some room for improvement. It has taken a long time to resolve some issues or find a workaround."
"It needs a lot of coupling with their other Fortinet products. To implement FortiToken, I most probably need to couple it with FortiAuthenticator for full implementation. An RSA token can be used with many devices, whereas Fortinet FortiToken is always linked to only one FortiGate device. If I want to reuse the token across five or six FortiGates, I would have to get the FortiAuthenticator product. I can't use one token to connect to different FortiGates, and I need to get another product to enable this functionality. They should also improve the support for their mobile client. There should be a more detailed roadmap for the operating systems being supported. Some of our users were using an old iOS iPhone, and they were forced to get a newer phone because FortiToken didn't support that version of iOS. Similarly, there may be a version of Android that is not supported, so the users need to change the phone. This was one of the reasons why our deployment took longer."
"The solution comes with two firewalls as a bundle. In that bundle, most of the individual users can be assigned to mobile users. However, in cases of technical difficulties, users may accidentally remove the mobile application. In normal scenarios, we get back to the activation key and assign it again."
"It could be integrated better if you could have your FortiToken, and the license would allow you to work across multiple FortiGate solutions."
"I would like to see if FortiToken can integrate with Office 365 mail to support the same two-factor authentication experience that I have with ESET. With ESET, when a user logs in, they are easily directed to the ESET authentication page, where they are prompted to enter their OTP after supplying their username and password. I understand from support that FortiToken cannot do this with email integration. That's why I opted for ESET."
"The tool could be a little cheaper."
"I would like to see complete OAuth support. Also, if they can support it from a SaaS (Software as a Service) or cloud platform, that would be great."
"Its reporting should be better. The reporting feature is missing. I don't have any reporting of who has done what, what has failed, and what didn't work."
"Reading documentation could be simplified. Technical support could also be faster."
"One thing that bothers me about Azure AD is that I can't specify login hours. I have to use an on-premises instance of Active Directory if I want to specify the hours during which a user can log in. For example, if I want to restrict login to only be possible during working hours, to prevent overtime payments or to prevent lawsuits, I can't do this using only Azure AD."
"The synchronization with the local Active Directory and synchronization with all of the users on the local and cloud could be better."
"We have a custom solution now running to tie all those Azure ADs together. We use the B2B functionality for that. Improvements are already on the roadmap for Azure AD in that area. I think they will make it easier to work together between two different tenants in Azure AD, because normally one tenant is a security boundary. For example, company one has a tenant and company two has a tenant, and then you can do B2B collaboration between those, but it is still quite limited. For our use case, it is enough currently. However, if we want to extend the collaboration even further, then we need an easier way to collaborate between two tenants, but I think that is already on the roadmap of Azure AD anyway."
"One area where it can improve is connectivity with other systems. Not all systems are connected and you have to do coding to establish a point of connectivity. It supports certain vendors and it supports certain protocols. It is limited in many other aspects at the attribute level."
"When it comes to identity governance, the governance features in Azure AD are very focused on Microsoft products. I would like to see those governance and life cycle management features offered for non-Microsoft products connected to Azure AD."
"I believe it can also be integrated into other Microsoft products, as well as more integrations with other solutions."
"A couple of years ago, I experienced some difficulty in implementing the solutions, the services of Azure AD. In one instance, I was not able to configure Azure AD for a registration. This was two or three years ago. However, currently, the documentation is very clear and there are no loopholes or anything that could hinder even a simple IT administrator to implement these services."
Fortinet FortiToken is ranked 4th in Authentication Systems with 21 reviews while Microsoft Entra ID is ranked 1st in Authentication Systems with 190 reviews. Fortinet FortiToken is rated 8.4, while Microsoft Entra ID is rated 8.6. The top reviewer of Fortinet FortiToken writes "A stable and scalable solution that provides an affordable and perpetual license". On the other hand, the top reviewer of Microsoft Entra ID writes "Saves us time and money and features Conditional Access policies, SSPR, and MFA". Fortinet FortiToken is most compared with Fortinet FortiAuthenticator, Cisco Duo, Yubico YubiKey, RSA SecurID and Cisco ISE (Identity Services Engine), whereas Microsoft Entra ID is most compared with Microsoft Intune, Google Cloud Identity, CyberArk Privileged Access Manager, Ping Identity Platform and Fortinet FortiAuthenticator. See our Fortinet FortiToken vs. Microsoft Entra ID report.
See our list of best Authentication Systems vendors.
We monitor all Authentication Systems reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
