We performed a comparison between Azure Active Directory and Fortinet FortiAuthenticator based on our users’ reviews in five categories. After reading all of the collected data, you can find our conclusion below.
Comparison Results: Based on the parameters we compared, users favor Azure Active Directory over Fortinet FortiAuthenticator because it has a free option and users also report an ROI.
"You can make resources. You can import them from Azure or Active Directory and put them in an application. For example, if there is an application that uses a lot of Active Directory groups, you can make the groups available for people. If they need to access that application, you can tell them the resource groups you have for that application. People can do everything by themselves. They do not need anybody else. They can just go to the Omada portal, and they can do it all by themselves. That is terrific."
"The most valuable aspects of Omada Identity for me are the automation capabilities."
"The support for the validity of the resources is valuable. The tool allows resource assignments within a validity period so that the managers do not have to remember to revoke the access once the work is done."
"The most valuable feature of Omada is its API connectivity, which allows seamless integration with various services like SAP, GRC, and Microsoft licenses."
"The teams we work with at Omada provide great insights and support. Overall, it has been a pleasure working with them. That's the part we value the most."
"When we started with identity and access management, we cleaned up and skipped 500 accounts. Therefore, there are a lot of people who are still in our system. Using this tool, we have cleaned up a lot of accounts for ourselves as well as our partners and suppliers. So, we can manage everything now."
"The most valuable functionality of the solution for us is that when employees stop working for the municipality, they are automatically disabled in Active Directory. Omada controls that 100 percent. They are disabled for 30 days, and after that time Omada deletes the Active Directory account. The same type of thing happens when we employ a new person. Their information is automatically imported to Omada and they are equipped with the roles and rights so they can do their jobs."
"I appreciate all the support we receive from Omada."
"The solution's most valuable aspect is that it easy to install. The user experience is very good."
"The initial setup is very easy."
"Features the addition and removal of access as needed for the VPN."
"The feature I value the most is the one-time passwords because it helps to authenticate users so you know the timing of their usage."
"The product is stable and reliable."
"I work a lot with Fortinet products and I call the support often. They are very quick to respond and the support is very good."
"The ease of use is really nice. Using Authenticator, I've been able to actually work better on my authentication due to the fact that I have a single fabric to authenticate control from my firewall and on my access points. Authentication takes place from this area."
"The most valuable feature is the OTP on the mobile phone."
"The most valuable features of Azure ID are the single sign-on and OpenID Connect authentication."
"It's definitely both stable and scalable."
"Privileged Identity Management and Privileged Identity Management make controlling access considerably easier and ensure that authorized access is achieved."
"Conditional Access is a helpful feature because it allows us to provide better security for our users."
"Single sign-on is the reason we use AD."
"Azure Active Directory has been very useful for our company, it is not difficult to use."
"I would say that Azure AD's pricing is very reasonable because of the structure and in terms of the solution."
"The way the laptops are joined is valuable. We can take advantage of that in terms of being able to log in and do things. It is easier to change passwords or set things up."
"The Omada support response time has room for improvement."
"The user interface could be improved. The interface between Omada and the user is mainly text-based."
"Improved traceability would be helpful for administrators. For example, let's say a user's permission is being revoked. We can only see the system that has carried out a particular action but not what triggered it. If an event definition or something has changed in the criteria for the permission being removed or something like that, we don't have immediate access to that information. It takes a little detective work."
"Functionality and usability could be improved."
"I would like to see them expand the functionality of the tool to continue to be competitive with the monsters out there. For example, they could add functionality on the authentication side, functionality that Octa and SailPoint have. But they should do that while maintaining the same simplicity that makes Omada a product of choice today."
"When you do a recalculation of an identity, it's hard to understand what was incorrect before you started the recalculation, and which values are actually updated... all you see are all the new fields that are provisioned, instead of seeing only the fields that are changed."
"The solution should be made more agile for customers to own or configure."
"In our organization, all the data is event-driven, which means that if an attribute is changed in the source system, it can be updated within a few seconds in all end-user systems. There is room for improvement in Omada regarding that. Omada is still batch-based for some processes, so sometimes it can take an hour or even four hours before the execution is run and the update is sent."
"We had issues trying to integrate the keys properly during the initial setup."
"Integration with FortiGate could be more fluid."
"Integration with some other enterprise applications could be improved."
"There are some protocols, such as SHA and SHA-2, that are not supported."
"The product must provide 2FA for applications."
"I would like to see integration and customization capabilities with the end-user portal to solve authentication issues with diverse implementation scenarios."
"Fortinet FortiAuthenticator's initial setup process could be easier."
"There are multiple areas that are in need of improvement. It is not a mature product."
"I think there is room for improvement with actually discussing, and advertising Microsoft as a an authenticator. Many people just get confused and use Google, and I think if Microsoft would make more of an effort to penetrate the market, that would be key."
"Four years ago, we had an issue with Azure AD. We wanted to reverse sync from Azure AD to on-prem Active Directory, but we couldn't achieve this. Azure AD could connect only in one way, for example, from your site to Azure. If you needed to do the reverse and connect from Azure to on-prem, there was no way to achieve it. We asked Microsoft, and they told us that they don't support it."
"The main issue is that because Active Directory is in the cloud, it will inevitably be dependent on internet connectivity."
"Definitely, the price could be lower. When we moved from AWS to Azure, we started paying more."
"The only issue with Azure AD is that it doesn't have control over the wifi network. You have to do something more to have a secure wifi network. To have it working, you need an active directory server on-premises to take care of the networks."
"I think something that is key would be the group policies replication over the cloud, in order to prevent or to avoid relying on the on-premise Active Directory servers and to manage group policies."
"There is no great solution in the cloud for Conditional Access authentication and RADIUS-type authentication."
"I want better integration between Azure AD and the on-prem environment because there are currently limitations that can hamper employee experience. We use a feature called password writeback, that can be challenging to implement in a hybrid environment. Employees can change their passwords using a self-service password reset (SSPR) feature, which reflects from the cloud to the on-prem identity, but not the other way around. Currently, there is no way to reflect passwords from on-prem identities to the cloud."
Fortinet FortiAuthenticator is ranked 5th in Single Sign-On (SSO) with 52 reviews while Microsoft Entra ID is ranked 1st in Single Sign-On (SSO) with 190 reviews. Fortinet FortiAuthenticator is rated 8.0, while Microsoft Entra ID is rated 8.6. The top reviewer of Fortinet FortiAuthenticator writes "A reasonably priced solution that can be scaled toward different functionalities and offers flexible SMS messaging". On the other hand, the top reviewer of Microsoft Entra ID writes "Allows users to authenticate from home and has excellent integrations in a simple, stable solution". Fortinet FortiAuthenticator is most compared with Cisco ISE (Identity Services Engine), Fortinet FortiToken, Fortinet FortiNAC, Cisco Duo and CyberArk Privileged Access Manager, whereas Microsoft Entra ID is most compared with Microsoft Intune, Google Cloud Identity, CyberArk Privileged Access Manager, Cisco Duo and PingFederate. See our Fortinet FortiAuthenticator vs. Microsoft Entra ID report.
See our list of best Single Sign-On (SSO) vendors, best Authentication Systems vendors, and best Identity Management (IM) vendors.
We monitor all Single Sign-On (SSO) 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.
