We compared Microsoft Entra ID and Google Cloud Identity based on our user's reviews in several parameters.
Microsoft Entra ID is praised for its user-friendly interface, efficient authentication process, and seamless integration. Users appreciate the exceptional customer service and reasonable pricing. Google Cloud Identity stands out for its comprehensive security measures, seamless integration with Google services, and efficient user management capabilities. Users highlight the excellent customer service and flexible licensing options. Therefore, Microsoft Entra ID excels in customer service, setup cost, and flexibility, while Google Cloud Identity shines in security measures, integration, and user management capabilities.
Features: Microsoft Entra ID stands out for its user-friendly interface, efficient authentication process, and seamless integration across various platforms. In contrast, Google Cloud Identity is known for its comprehensive security measures, seamless integration with other Google services, efficient user management capabilities, and streamlined access controls.
Pricing and ROI: The setup cost for Microsoft Entra ID is described as affordable and competitive, with a straightforward and user-friendly setup process. Users appreciate the flexibility and options available for licensing. On the other hand, Google Cloud Identity offers reasonable pricing, a straightforward setup process, and flexible licensing options catering to users' needs and requirements., The ROI from Microsoft Entra ID is positive, with users experiencing cost savings and improved efficiency. Meanwhile, Google Cloud Identity offers cost-effectiveness, enhanced security measures, increased productivity, and easy management of user access and permissions.
Room for Improvement: Microsoft Entra ID could benefit from better user interface design and optimization for different devices, simplifying the sign-up process, increasing customization options, and adding advanced security features. On the other hand, Google Cloud Identity users would like improved integration with other platforms and applications, a simpler and more user-friendly interface, better documentation, and more comprehensive support resources.
Deployment and customer support: The reviews for Microsoft Entra ID and Google Cloud Identity highlight that the duration required to establish a new tech solution can vary significantly for both products. However, it is important to carefully evaluate the context in which users use terms like deployment, setup, and implementation to determine the overall time required., Microsoft Entra ID's customer service is exceptional, efficient, and reliable. Users appreciate the prompt and knowledgeable assistance, effective communication, and seamless problem resolution. Google Cloud Identity's customer service is highly regarded and considered satisfactory.
The summary above is based on 104 interviews we conducted recently with Microsoft Entra ID and Google Cloud Identity users. To access the review's full transcripts, download our report.
"I think the first thing that is great is that it gives you a lot of features, like login, and then vaulted passwords and secure LDAP. It becomes easier for the end customer to leverage all those features without going to a higher SKU of G Suite."
"The solution is user-friendly."
"The most valuable feature is that you can manage users from one central location."
"Google is always on its own. Google Cloud Identity is pretty good on every point."
"I used it as an administrator without implementing it myself. As for valuable aspects or benefits, the significant point is that it's a straightforward, single solution that just works."
"The initial setup is easy."
"Although we have not looked at the whole product and explored it completely, we find that all the authentication features that we are using now are valuable."
"The solution is primarily used for single control and single sign which helps with the security and authentication of multiple devices."
"Single sign-on provides flexibility and helps because users don't want to remember so many passwords when logging in. It's a major feature. Once you log in, you have access to all the applications. It also enables us to provide backend access controls to our users, especially when it comes to groups, as we are trying to normalize things."
"The features around permissions are excellent."
"I like the way it communicates to the cloud."
"It helps us with maintaining enterprise identities."
"It is cloud based so it is always updated,"
"The security and infrastructure management features are the most valuable ones for us."
"Conditional Access is a helpful feature because it allows us to provide better security for our users."
"The solution adds an extra layer of security."
"The solution's storage capacity could be increased."
"We cannot manage the attributes of SSPR."
"If you want to set up some alerts, you don't have much control over the configuration. You have to use their default alerts. And they only provide alerts for certain activities, so you cannot customize those. Monitoring isn't very helpful either."
"The management of external users needs to be introduced in the tool as it is an area of concern in the tool presently."
"The integration should be made easier."
"To improve the product, the integration with third-party products could always be smoother."
"Google Cloud Identify could make the technology used easier to understand as a layman making it more user-friendly."
"Technical support is slow."
"I hope, in the roadmap, Microsoft eventually offers the same features as Okta. It will take some more time to mature."
"Azure AD does not support legacy authentication protocols, such as NTLM or Kerberos."
"The downside of using a single password to access the entire system is that if those credentials are compromised, the hacker will have full access."
"Tech support is inconsistent."
"Initially, we wanted to exclude specific users from MSA. So, we had a condition policy, which forces MSA for all the users. So we wanted to exclude users who are using an NPS extension. So it was not listed, as a NPS extension was not listed outside an application, in actual, so, we go back and were not able to exclude users using NPS extension from MSA. So that was one limitation that we found and we had to work around that."
"The synchronization with the local Active Directory and synchronization with all of the users on the local and cloud could be better."
"From time to time it takes a little bit of time to replicate, with some of the applications—something like five to 10 minutes. I know that the design is not supposed to enable real-time replication with some of the applications. But, as an administrator, I would like to run a specific change or modification in Azure Active Directory and see it replicated almost immediately."
"There are some features, where if you want to access them, then you need to make use of PowerShell. If someone is not really versed in PowerShell scripting, then they would definitely have issues using some of those features in Azure Active Directory."
Google Cloud Identity is ranked 3rd in Identity and Access Management as a Service (IDaaS) (IAMaaS) with 21 reviews while Microsoft Entra ID is ranked 1st in Identity and Access Management as a Service (IDaaS) (IAMaaS) with 190 reviews. Google Cloud Identity is rated 7.6, while Microsoft Entra ID is rated 8.6. The top reviewer of Google Cloud Identity writes "A stable and scalable cloud solution easily compatible with Google office Suite". 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". Google Cloud Identity is most compared with Microsoft Intune, Okta Workforce Identity, JumpCloud, VMware Workspace ONE and ManageEngine Endpoint Central, whereas Microsoft Entra ID is most compared with Microsoft Intune, CyberArk Privileged Access Manager, Cisco Duo, Yubico YubiKey and Okta Workforce Identity. See our Google Cloud Identity vs. Microsoft Entra ID 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.