Microsoft Entra ID (formerly Microsoft Azure Active Directory or Azure AD) is a cloud-based identity and access management (IAM) solution supporting restricted access to applications with Azure Multi-Factor Authentication (MFA) built-in, single sign-on (SSO), B2B collaboration controls, self-service password, and integration with Microsoft productivity and cloud storage (Office 365, OneDrive, etc) as well as 3rd party services.
$6
per user/per month
SecurID
Score 9.0 out of 10
N/A
SecurID, a company and solution suite from RSA, is an identity and access management suite supporting access management, authentication, and identity governance.
Google Workspace is really pretty much the only other primary competitor. And again, Microsoft has just been the standard for so many years and it was in place at the organization when I was first brought on at the beginning of my tenure. And so it didn't seem logical to switch …
Yeah, so basically that product to be honest, was more of a getting comfortable with cloud identification management. So that was a product I used. It has all the policies for desktops and doing updates and all that central directory identity provisioning stuff for users. Users …
We use DUO as another IDP solution and we also evaluated Okta as a solution. We didn't have a choice to be honest, because Microsoft products, you can't get away with it, but it's built in and a bunch of other providers have it as authentication, so it's great.
We've used other Microsoft products and we've also used some standalone products, like each application you can have its own identity, so we've looked at some of those too, but we try to use the Entra ID as much as possible because it offers a wider range of reliability.
We actually did just the Microsoft Active directory, so we picked the actual. We did just pure active directory. I mean the open LDAP stuff, but it didn't quite work that well.
I think the closest one would be because we recently went through an implementation, but Salesforce has their own version of a signal sign-on product. It's not the same. I'd say that it works, but it doesn't give you as much functionality.
For us, it was a natural evolution of our use of active directory. As we went from on-premises to the cloud, this was an easy extension of our authentication infrastructure. We looked at other products from Oracle, so Oracle ID, Oracle Identity Management. We looked at pink …
We used Google before, but we tried to use it but it didn't. We didn't like it. I'll this is better. It integrates better with our environment that we have right now.
We're Microsoft dedicated. We do however, displace other products that do similar things, so a lot of third party products, so even like Okta. In my opinion, it's just equally as powerful or more powerful of a product and it has a way better price point for customers. I think …
I'd love to tell you about Amazon IM and Google's IM because they suck and they tell you to use Entra ID, factually. They're like, oh cool, set it up with Entra ID. They just know you're going to do it. I don't think you guys have a competitor, to be honest. You just don't.
We're a Microsoft Native shop, so we're looking at Okta's identity tool, SailPoint and a few other competitors of Venture id. And we decided to go with this one because we're already using Active Directory, so just using the native Microsoft Suites kind of just they integrate …
Well, it's natively integrated with all Microsoft Stack, so it comes very handy when you need to, for example, use it for Intune Association, et cetera, so it's very handy.
Previously we had worked with Okta, which was kind of using our replacement for active directory server, and I know that has integrations, but we ended up just going with Entra ID just for the ease of access and without having to stack on an additional third party application …
In our application use case, it's kind of unique and there isn't any like for if there's anything on the identity space, probably Okta. Yeah. But we do both use them and we have integration with Okta and Entra ID, so it works for us very well.
Microsoft Login ID was chosen for its ease of use and availability of access via any device. Unlike the old Active Directory, it has a low learning curve and is very intuitive for analysts who are using it for the first time.
SecurID works with more software/devices than Azure MFA. It also seems to work more smoothly for end-users compared to some of the other options out there. We have not had issues with this app not working and is very reliable/stable. It also allows token codes to be …
Overall MS AAD is good but we have had a few too many reliability issues with the product that have lead to enterprise authentication outages over the last year. The Senior executives have a preference on Securid to be more reliable than MS AAD. SecurID does a better job in …
SecurID is simple and inexpensive. It does what is needed of it, without a lot of bells and whistles. It was the most cost effective solution for our organization, and provided us quick return on our investment with minimal work.
RSA is an industry-standard and most users are comfortable with the process and use of the items. GA offers a phone-based platform and a user-based setup. However, there is some reluctance to use.
We use Entrust IdentifyGuard in a separate environment. While Entrust Identity Guard is a great solution, the scalability of RSA was the reason we chose this product.
And also Google Authenticator that TrustRadius does not have on their database. Both are good but not excellent. SecureID felt like the best option because it is solid and has proven to be the best option for more than 20 years. The other options were confusing and offer things …
RSA SecurID is in a different space than Okta and Ping Identity. In our experience RSA SecurID will protect on site networks and endpoints with RSA advanced authentication. They used two factor authentication to assure auditors and network admins that users that are logging in …
RSA is good for agent-based and RADIUS integration but the move is toward better integration with web-based (API/TLS) integration. RSA has a new product to support this integration but RSA SecureID does not offer this and is antiquated technology but still has it's placed in an …
RSA SecurID and Azure Multi-factor authentication both integrate with authentication on multiple operating systems and SaaS providers. RSA SecurID seems to integrate (at least while I have used it), with more software solutions than Azure Multi-factor authentication though.
RSA SecureID is still widely deployed and the de facto industry standard for 2nd factor authentication. Microsoft Azure offers alternative 2nd factor auth but the price was too high. We are still testing Citrix Netscaler offering with CloudBridge for 2nd factor auth and SMS …
Duo security does not provide an internal solution, which is what we need in our environment to avoid making outside internet connections from our PCI-DSS environment. This is where RSA shines.
For one, a significant factor for us is that it is integrated with HelloID, which gives us, as the IT department, a lot of time back because we don’t need to create user accounts manually. It is great for the roles we have defined, as they can be used repeatedly. A great feature is that guest accounts can be created for external users; we only need to be in a closed area of your domain.
Works well in a large organization with many employees and devices but may not work so well in smaller organizations due to alternatives that are cheaper and are already provided (such as Microsoft's Azure MFA). Using the soft token is easy and convenient. For a large environment, It has allowed us to have a single app used for authentication for all of our various users, and using the soft token is easy and convenient.
It addresses the issue of identity management very well with respect to putting in that multi authentication.
It can also support with respect to we can push these policies into another product that is not Microsoft, but it needs that SSO so we can have one account going into multi different accounts. I think that's the biggest pros and the easy use of Microsoft 365 also is one of those pros also in terms of administration.
RSA SecurID allows me to access network files from remote locations (hotels, other businesses, working from home). This allows me greater productivity and helps me with a work-life balance as I can work later at night or not get so backed up when I'm traveling.
RSA SecurID keeps information secure by limiting access to network files
RSA SecurID is easy to use with a soft token - one less item to carry around in my travel bag
Well, I'm an active ad admin, so there's a lot of features in active directory that Entra ID seems to be just adding now. We're kind of figuring out that the policies are different than Entra ID that they were in active directory and we're finding other products to do that, like Azure policy. Some things I'm used to seeing in identity products or like active directory aren't in Entra iID, but are doing good job of managing stuff that it does so far.
Entra ID is a vital part of our Identity management/administration. With the integrations it has to other Microsoft products, setup and configuration is a breeze. Additionally, Microsoft has been around a long time and have the resources to ensure this product is stable and secure for many years to come. We know it will evolve with time to provide us what we need as technology changes.
Long story short, does the job. Can use company credentials to setup and access the account for SecurID. Easy to setup and implement. Doesn't have a high learning curve.
Very easily usable. It could be easier to use. Implementation was kind of tricky. We do run a hybrid environment, so we're syncing a local active directory instance with Entra ID, so that could be a little tricky. But outside of that, if you're not running a hybrid deployment or a version of Entra ID usually, it's pretty straightforward.
Using it very frequently, it's important that its straight forward and I do not have to go through unnecessary hoops to achieve something seemingly simple. Can setup using the company credentials and do not have to setup up a separate account. Setup was fast and easy. GUI is very straight forward and quick.
Microsoft has offered Azure Active Directory as a solution for a couple of decades now, so they have seen and anticipated almost any issue that an organization may face and can therefore help. The cloud offering of Azure Active Directory offers some additional "self healing" or monitoring services that can minimize the need for a service call. However, as with most large companies supporting a fast growing market, there may be some gaps in service knowledge (and particularly processing) from the front line / tier one staff as they follow a corporate script at first contact.
Their support for onboarding and set-up is quite good. The only issues we tend to have are obtaining new user devices. These need to be planned ahead of time.
Make sure you use a good partner. Our implementation was a bit longer and more problematic than we expected. Our partner got it done, but, in my opinion, some of their inexperience and staffing issues were evident.
Microsoft Entra ID is not as stand-alone product as competitors like Okta. It may lack some of the features that competing products have but on the other hand it integrates both technically and license wise with other Microsoft cloud services and is easy to deploy. It is also the easiest way to extend identity management to the cloud if you already have Microsoft Active Directory in use.
RSA SecureID is still widely deployed and the de facto industry standard for 2nd factor authentication. Microsoft Azure offers alternative 2nd factor auth but the price was too high. We are still testing Citrix NetScaler offering with CloudBridge for 2nd factor auth and SMS code to user mobile device so it is yet to be seen as a viable alternative to RSA.
I don't know if I can really quantify that. It's one of those products that just exists and so there's not a whole lot of changes that we need to make with the product. And so I guess in terms of value, what we get is we don't have to worry about the identity management piece. We know that that's taken care of.