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.
"It is a stable solution. Stability-wise, I rate the solution a ten out of ten."
"It's easy to set up."
"The solution is primarily used for single control and single sign which helps with the security and authentication of multiple devices."
"The most valuable feature is that you can manage users from one central location."
"The Cloud Identity is well advanced in terms of features, applications, and the components that it is offering."
"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."
"One of the most useful features was the single sign-on. You can use it as an identity provider or service provider. And you can use their organization unit feature to enable or disable some of the features for a specific group of users."
"The most valuable feature of Google Cloud Identity is group access. You are able to assign policies to groups instead of users individually."
"The most valuable feature is the conditional access policies. This gives us the ability to restrict who can access which applications or the portal in specific ways."
"It has given us the ability to be able to establish single sign-on identities in which we can establish credentials no matter where we are, whether it is on-premises or in the cloud, in a hybrid cloud, or in an additional connection from another cloud where we share equipment or host."
"A use case that we did for an end user in a manufacturing organization: We used WVD with biometric authentication because 1,500 processes need to happen in a process. The user didn't want to use a login using their credentials. They wanted to use fingerprinting or tap their ID. That is where we integrated with the authentication. Now, they can process in a couple of hours, and they run those 1,500 processes every day. This changed their login process, which improved the manufacturing process. This helped a lot for their high deployment."
"Coming from a traditional on-premises Active Directory infrastructure, it is purely a SaaS platform. It is global. It is evergreen. It is always evolving. It is core to the Microsoft Ecosystem."
"One of the most important is the Conditional Access. It helps affect a Zero Trust strategy positively."
"Azure AD allowed us to get rid of servers and other hardware running at our offices. We moved everything to the cloud. Once we set up roles and permissions, it's only a matter of adding people and removing people from different groups and letting permissions flow through."
"This solution serves as the basis to understand the MS SSO and MFA capabilities."
"The ability to speed up ability is an asset."
"The one place it could be improved is the password vaulting. The password vaulting does not prevent the admins from reading users' passwords, and that's a debate."
"The pricing for this solution is a little bit higher than AWS and others, which is something that should be improved."
"If I were to suggest enhancements, it would mainly revolve around ensuring compatibility and maximizing integration options with various services."
"Google Cloud Identify could make the technology used easier to understand as a layman making it more user-friendly."
"Technical support is slow."
"I would like to see more integration in future releases."
"The interface could be improved by simplifying it further."
"To improve the product, the integration with third-party products could always be smoother."
"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."
"The integration between the Azure active directory and the traditional active directory could be improved upon."
"Microsoft has so many different requirements and priorities that sometimes they don't invest all their energy into the products that you have expectations to investigate."
"Overall, it's not a very intuitive solution."
"Azure Active Directory could improve by having an authentication service for laptops or desktop computers running Mac and Linux operating systems. They currently have authentication capabilities for Microsoft Windows. Having this capability would benefit people because in today's world everybody is working from the home environment."
"Azure Active Directory could benefit by adding the capability for identity life cycle for the on-premise solution. For example, an HR solution, which is built on-premise or, in general, better on-premise capable solutions."
"In a hybrid deployment, when we update a license by changing the UPN or email address of a user, it does not get updated automatically during normal sync. This means that we have to update it manually from Azure, which is something that needs to be corrected."
"The synchronization between my AD and Azure AD needs improvement."
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 solution that can help with collaboration and productivity". 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". 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, Okta Workforce Identity, Cisco Duo and Yubico YubiKey. 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.