We performed a comparison between Microsoft Entra ID and VMware Identity Manager based on real PeerSpot user reviews.
Find out in this report how the two Identity and Access Management as a Service (IDaaS) (IAMaaS) solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."It's very good at not disrupting the user experience."
"We have about 80 users in the Azure Active Directory right now, however, we know that if it was necessary to scale it for hundreds or thousands of users, it wouldn't be a problem."
"The scalability is good now, and I find it to be more stable and faster since scaling up to ESX."
"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."
"I like that you can run it on-premises. I also like that I can use Azure at any time as the main one."
"It has been stable, and we haven't had any issues since we started to use it."
"Conditional access is a very important feature where a specific user can be restricted such that they cannot connect to the application if they travel outside of the US."
"In terms of identity management, it helps to improve security posture. It generally helps in terms cloud security, simplicity, and single sign-on for multiple apps."
"It helps the end users to work on the road without needing to set up all kinds of VPN connections"
"The most valuable feature is single sign-on."
"One of the features that I enjoyed most was the integration with Azure AD because I could use VMware Identity Manager to standardize the User Principal Name coming from Active Directory. You have Azure AD Connect to do that. In between, if you have vIDM handling it, you can easily get the synchronization of users into your VM and standardize the User Principal Name. If you require quality assurance for handling it, you can actually count on the vIDM to do so. That was one of the main things I enjoyed about the product."
"The solution was easy to deploy."
"Zero Trust implementation is a great feature."
"The most valuable feature is the User Experience Designer, which has been very helpful for our project."
"Its value is when you use it with a Workspace ONE UEM solution as it is part of the ecosystem for VMware Workspace ONE."
"The most valuable feature is that it will use my credentials to access various parts of the infrastructure or other solutions, such as vRealize."
"I would like it if Intune could manage MacOS or iOS directly. Right now, we have to use a third-party solution."
"I would like to dive into some of the things that we saw today around the workflows at this Microsoft event. I cannot say that they need to make it better because I do not have much experience with it, but something that is always applicable to Microsoft is that they need to be able to integrate with their competitors. If you look at IDP, they do not integrate with Okta."
"Technical support could be faster."
"There are issues using it with ADFS."
"The support could be better. Lately, they sort of dropped off a bit in terms of quality."
"They can combine conditional access for user actions and application filtering. Currently, they are separated, and we cannot mix the two. I do not know how it would be possible, but it would be interesting."
"Microsoft should work on enhancing its machine-learning algorithm to prevent unnecessary lockouts of users."
"The Cloud Provisioning Agent cannot provision a lot of the information that AD Connect does. For starters, the lightweight version cannot synchronize device information. If you have computers on-premises, the information about them will not be synchronized by the Cloud Provisioning Agent. In addition, if you have a user on the cloud and he changes his password, that information should be written back to the on-premises instance. But that workflow cannot be done with the lightweight agent. It can only be done with the more robust version."
"The mobile SSO doesn't work as well on Android."
"it's very dependent on an active directory"
"Many of the features that exist in Active Directory do not exist in Identity Manager, which means that people depend on Active Directory."
"I would like better integration for deploying programs with binary files."
"We have a lot of problems when it comes to integrating with Active Directory."
"There is a need for better user lifecycle management within VMware Identity Manager, along with better user governance...The scalability of the product needs to improve."
"The security features could always use improvement, although there has already been a huge improvement from years ago."
"The database gets corrupted when used in the cluster. Sometimes it works, sometimes it doesn't."
Microsoft Entra ID is ranked 1st in Identity and Access Management as a Service (IDaaS) (IAMaaS) with 190 reviews while VMware Identity Manager is ranked 15th in Identity and Access Management as a Service (IDaaS) (IAMaaS) with 12 reviews. Microsoft Entra ID is rated 8.6, while VMware Identity Manager is rated 7.6. The top reviewer of Microsoft Entra ID writes "Allows users to authenticate from home and has excellent integrations in a simple, stable solution". On the other hand, the top reviewer of VMware Identity Manager writes "A tool that needs to improve scalability but is useful to manage user". Microsoft Entra ID is most compared with Microsoft Intune, Google Cloud Identity, CyberArk Privileged Access Manager, Yubico YubiKey and Cisco Duo, whereas VMware Identity Manager is most compared with CyberArk Privileged Access Manager, Cisco ISE (Identity Services Engine), Fortinet FortiAuthenticator, SailPoint IdentityIQ and Okta Workforce Identity. See our Microsoft Entra ID vs. VMware Identity Manager report.
See our list of best Identity and Access Management as a Service (IDaaS) (IAMaaS) vendors.
We monitor all Identity and Access Management as a Service (IDaaS) (IAMaaS) 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.