Google Cloud Identity Reviews

We are using Google Cloud Identity for application development.

The best features in Google Cloud Identity are their cloud, their VMs, and their cloud VMs, which are too good compared to OCI.

Using Google Cloud Identity is beneficial in terms of finance as we are always doing automation and AI, and it is definitely the best.

I use multi-factor authentication with Google Cloud Identity.

Regarding how Google Cloud Identity helps to improve security, I can say that security is something everyone is using. I do not feel any different. After this, everything will be JWT token and all things we are using. I do not feel any difference in there.

I have used the SSO feature, single sign-on, with Google Cloud Identity.

In a few words, how Google Cloud Identity affected user management within my organization is that it is not done for my organization but for one of my clients only. I already have the ADs there, but still, it is the best.

I think the reporting tools of Google Cloud Identity are good. I cannot comment on these kinds of things for this particular product.

If you are asking about room for improvement with Google Cloud Identity, whatever is there already, cost is the only problem. If you are comparing with GCP, OCI, the cost will be a little bit higher.

If you ask why not nine for Google Cloud Identity, I must say I have open sources available that are equivalent to this one. The costing part is also coming into consideration. Open sources are definitely available.

We have started using Google Cloud Identity almost one year ago.

The technical support of Google is very good.

Deploying with Google Cloud Identity is not an easy process. It will take one to two weeks.

For the deployment of Google Cloud Identity, it involves around twenty developers, and the actual deployment will be two to three people, or one to two.

Comparatively, we have reduced costs with automation, but it is not about Google or something. Whatever the product you are asking about, product-wise, it is not the Google thing. For Google Cloud Identity, there will be a recurring cost. There is no ROI. ROI will be coming based on the product deployed. It is not Google's benefit. If I use it in Oracle also, I will get the same benefit. It is just a platform to run it.

As of now, we do not have any challenges when implementing the solution with Google Cloud Identity, but in Oracle, we have faced a lot of things.

I can rate them from one to ten at definitely seven to eight. I would give this product an overall rating of eight out of ten.

We work for all sorts of verticals, including NBFC, manufacturing, and IT companies.

First and foremost, Google Cloud Identity does not require maintaining any server or on-premises infrastructure. It is straightforward to implement as it provides zero trust policy and context-aware access with conditional-based access. You can define policies for users who may be available in any part of the world. Users need only a single identity to access their machines and applications.

From a management standpoint, it is easy to use. We do not need to maintain multiple admin panels or multiple consoles to manage user applications. Everything can be done from one console. If you delete one identity, it gets deleted from everywhere. It is a uniform and unified way to maintain and manage things easily from both end-user and admin portal perspectives.

The most beneficial feature for enhancing security is context-aware access. Previously, 7 to 10 years ago, people used to set up policies on the network level. If you were in the network, you could access the application or needed VPN access. With context-aware access, it provides the flexibility to set up anything at the application level rather than the network level, reducing network dependency.

The integration of multi-factor authentication features is always a priority for customers because username and password alone are not enough from a security standpoint. Multi-factor authentication is required for all applications connected with identities, and it functions very effectively.

The single sign-on feature provides seamless integration. For SAML-based applications, you can integrate applications within three steps. In Active Directory or the Microsoft environment, you need specific integration knowledge. If you know how to manage identity in Google, it is easy to set up the integration and complete the implementation.

If applications support SAML protocols, integration is always an easy task. However, there are difficulties with form-based applications or LDAP-based applications, particularly traditional applications.

We need more flexibility not only with SAML but also with LDAP-based and form-based applications. Context-aware access currently only works with SAML-based applications. If other application integrations could support context-aware access, that would be helpful, as companies are in a transition mode with various traditional, form-based, and LDAP-based applications.

Mobile device management could be improved. Through Google Cloud Identity, we can manage Android applications and have control over iOS devices, but container functionality is missing. This is particularly important for BYOD (Bring Your Own Device) scenarios, especially in India where the market is now split equally between iOS and Android users. Improvements in this area and integration capabilities would be beneficial.

I started working with Google Cloud Identity around 5 or 6 years ago.

We are a Google partner and sell Google Cloud Identity and Google Workspace.

I recommend Google Cloud Identity, but it is important to first conduct a discovery about the organization, their applications, and requirements before determining if Google Cloud Identity is the appropriate product.

Companies with a Microsoft footprint or Microsoft-shop companies typically prefer Microsoft Entra ID over Google products. Some SysAdmins are not in favor of Cloud Identity because they believe their jobs might be at risk since it is easy to manage and does not require server maintenance or scripting knowledge. It operates through a checkbox system with quick deployment times. However, this is more about choice and work behavior. We focus on change management, which has proven effective.

I would rate Google Cloud Identity an 8 out of 10 overall, though ratings may vary depending on specific categories such as MDM versus identity management features.

We use Google Cloud Identity as it is a part of the Google Workspace, and we took the Enterprise suite which comes with Google Identity.

There are still some small integrations connected to Google Cloud Identity for convenience.

I am still using Google Cloud Identity for small integrations.

The best features of Google Cloud Identity are that it's free and works with modern applications, meaning if it's OAuth or using the OAuth protocol, it's very easy to integrate with those applications.

Multi-factor Authentication has helped enhance security in our organization, but we did not use the Google suite or Google Cloud Identity for it; we are using Azure Entra.

The reporting capabilities of Google Cloud Identity are convenient because I can readily drill down the data when we do investigations about logins, breaches, or compromises; it's easy to trace the login history.

We do not use these capabilities of Google Cloud Identity because of the limitations for Active Directory integration.

Google Cloud Identity could have impacted our organization positively, but if it weren't for the Active Directory integration requirement, we could have been using the Google Identity solution.

Google Cloud Identity can be improved by having better integration with Active Directory, but since Active Directory is also a Microsoft solution, we don't think it will happen; that's the only disadvantage of Google. The Active Directory integration that Entra has is a better implementation compared to Google, which we found lacking.

I have been working with Google Cloud Identity for more than 10 years.

The deployment model we are using for Google Cloud Identity has limitations as Google is not good in that area; there is limited support for hybrid, so it's only for public, which is one of Google's weaknesses.

I would rate Google Cloud Identity support a two out of ten because we don't have experience with it; however, for other services, they're good, and I'd rate them eight.

Negative

Before choosing Google Cloud Identity, we evaluated other solutions including Azure and Entra, and we looked into Okta as indicated in the research, but we did not pursue it anymore, so we chose the Entra identity solutions.

The initial setup of Google Cloud Identity is straightforward.

We did not use an integrator, reseller, or consultant for the deployment; we have third-party support.

Before choosing Google Cloud Identity, we evaluated other solutions including Azure and Entra, and we looked into Okta as indicated in the research, but we did not pursue it anymore, so we chose the Entra identity solutions.

Google Cloud Identity can be improved by having better integration with Active Directory, but since Active Directory is also a Microsoft solution, we don't think it will happen; that's the only disadvantage of Google. The Active Directory integration that Entra has is a better implementation compared to Google, which we found lacking. On a scale of one to ten, I rate Google Cloud Identity an eight.

When you try to access any application, the system needs to verify it is you. Normally, for traditional security, you just need to enter your username and password. 

However, with Google Cloud Identity, you can have multilayer security, such as two-step verification or multi-factor authentication. This includes receiving codes via SMS, voice calls, or using Google Authenticator. 

My company sells this product as part of our IT consultancy, and we use it as a system reseller and Google partner.

Google Cloud Identity helps improve our organization's security by providing an additional layer of security, such as multi-factor authentication. This ensures that our data is protected even when accessed remotely, which is crucial for hybrid or work-from-home arrangements. 

Additionally, it has helped in reducing operational costs and response times for security incidents, making our security measures more efficient.

The most valuable feature of Google Cloud Identity is its simplicity in deployment. You only need to purchase and assign licenses to users, and there's no need for extensive setup. Another valuable feature is its integration with Google Workspace, which enhances security through context-aware access and allows for geographic and IP-specific restrictions. This ensures secure access to applications and data.

Google Cloud Identity should improve its compatibility with other products without any impact, such as Jamf Cloud. 

Additionally, there should be more control over data and improved security measures, particularly in enhancing encryption and addressing vulnerabilities that attackers might exploit.

I have been using Google Cloud Identity for around six years.

I rate the stability of Google Cloud Identity as very high, between eight to nine out of ten.

Google Cloud Identity is quite scalable. I rate its scalability similarly high, between eight to nine out of ten.

Google's technical support needs to be more knowledgeable and responsive, especially in different time zones. Their standards and response times need improvement, especially for support teams located in India as compared to Europe.

Neutral

The initial setup of Google Cloud Identity is very straightforward with no specific installation required. You just need to purchase the licenses and assign them to users.

Google Cloud Identity is cost-effective and provides numerous services under one license, which include Google Drive, Google Meet, and other Google Workspace applications, thus providing financial benefits and cost savings for the company.

Google services are affordable compared to other services. Additional costs depend on the specific products; for example, Google Cloud Platform (GCP) may require extra payment for additional support, while Google Workspace does not.

I can recommend Google Cloud Identity due to its stability, scalability, and integration with Google Workspace for collaboration. It ensures data protection and offers a comprehensive set of services. I'd rate the solution eight out of ten.

At the moment, my company uses Google Cloud Identity for some of our internally authenticated users for internal application development and custom development. My company uses Google Cloud Identity in conjunction with a product called IAP, which is BeyondCorp Enterprise's authenticated proxy solution.

The most valuable feature of the solution stems from the IAP part, which is unique. The tool offers a free tier version for 100 users, for which I get an ID similar to a Microsoft ID, which is quite handy. In general, it's a fairly basic product.

I think Google Cloud Identity is a very good product already, and it is also much better than Microsoft's because Microsoft's legacy products, which do a lot of work apart from what they do in general, are very poorly documented. I think the advantage of Google is that its products are properly documented and seem to be relatively easy to use. Microsoft products come with extremely poor documentation. Google's pure documentation, technical reference documentation, and tutorial documentation basically work. With Microsoft, even if you follow the instructions, it doesn't work. It is usually difficult to find information with Microsoft, so you end up working around in circles, making Microsoft products and their documentation infamous among the developers as it is quite difficult.

The management of external users needs to be introduced in the tool as it is an area of concern in the tool presently. Currently, the tool allows you to put in only Google's authenticated users, but if you could put in external users, especially in groups, then it would probably be great.

User management is an area of concern where improvements are required. At the moment, you cannot let users who are not a part of your organization be added to a security group. It is possible to add external users to your organization's security group with Microsoft.

When it comes to Google Cloud Identity, you can get around 100 free licenses for a hundred seats, but if you want to go above the limit of 100 users, then you have to buy the tool for every single user, making it look equivalent to the product which is Microsoft Office. If you have over 100 users in your company, you need to buy Microsoft Office and pull out Google from the company's infrastructure. Google Cloud Identity is not ideal regarding the licensing models offered.

I have been using Google Cloud Identity for probably about six months.

It is a stable solution. Stability-wise, I rate the solution a ten out of ten.

Scalability-wise, I rate the solution a seven out of ten.

Around 500 people in my company use the solution.

Though I have not specifically contacted Google Cloud Identity's technical support, I do contact the support team of Google in general, and I can say that they have been really good. The support team's response time and quality have been good.

The product's initial setup phase was very simple.

The solution is deployed on the public cloud.

Google Cloud Identity's setup phase is just a part of a larger setup process of Google, which doesn't take more than 30 minutes.

I rate the product price a seven on a scale of one to ten, where one is a low price, and ten is a high price. Microsoft products allow you to have 10,000 users.

With Google, I find the documentation part to be much better compared to other products in the market. The product works much more reliably and consistently while being functional. The tool gives you more ability to maintain the data that is within the company, which probably makes a big difference.

I rate the overall tool a seven out of ten.

I use the solution for dealing with Google Cloud Platform. When I use the solution for customers dealing with the Google Cloud Platform, they do not need to use Workspace. They just use Google Cloud Identity.

The solution is the best part of the Google ecosystem because it's familiar. When we go to change the allegation session, there's no problem.

I would like to see more integration in future releases.

I use Google Cloud Identity through a Google Workspace account account. When I create, I change the license, and I face no problem with that. The only difference for me and my users is that when we log in with Google identity, we cannot use Gmail and other things, but there's no problem with the other parts.

I've been using Google Cloud Identity for almost a year.

I rate Google Cloud Identity's stability a ten out of ten.

Fewer than 100 people are using the solution in my organization. We plan to increase this number.

Google's tech support is great, even though I sometimes have trouble reaching them.

Positive

The initial setup is easy. It took 15 minutes to activate the account.

We have a monthly license. The solution is not expensive, but the pricing is medium compared with our currency.

Changing from one session to another is seamless. I rate Google Cloud Identity a ten out of ten.

Two problems we face are with education and the market. If I am giving a solution to people, I am the adviser and advocate for this product. But if I advise people not connected to me, they find it hard to find the solution.

The solution is user-friendly. Anyone can use it. Google has clear documents for most of its features.

We cannot manage the attributes of SSPR. Microsoft has such provisions. The product does not have the dynamic groups feature provided by Microsoft. Equal to and not equal to are the only two contents in Google. Features like user life cycle governance and lifecycle management provided by Microsoft are not available in Google.

I have been using the solution for five years.

I rate the product’s stability a six out of ten.

Scalability is very good. I rate the solution’s scalability an eight out of ten. In my organization, more than 1500 people are using the solution.

The support team is pathetic. We can't reach Google Enterprise Support directly. We need to follow up with the partner who is supporting us. We need to follow their clock. If things get escalated, then Google Enterprise Support will get involved through email. Sometimes this process causes business impacts.

The technical support team is very polite. The team answers our questions patiently and helps us resolve the issues. The process of getting to the technical person on the call is pathetic. The first level of support goes to the partners. Based on our license structure, it goes to Enterprise, Business, or Standard. From there, we can escalate and take the issue to the next level and reach the technical support team.

I used Microsoft. I recommend Microsoft over Google because I feel that Microsoft has more capabilities on the security side.

The initial setup of the instance was straightforward.

The deployment doesn’t take long for an experienced person. We just have to activate the instance. The deployment is very easy. Once Google gives us space, MX will be very easy for us to set up. I implemented the product using GCDS. Provisioning and de-provisioning can be controlled from Active Directory. 

There are no challenges in user deployment. Based on the condition, it will be pushed immediately. Scoping of the license for use and everything else will be predefined based on the role. I don't feel any challenges in the deployment process. It's very good. The process is pretty simple. The solution clearly notes each and every point in the documents. We faced no challenges.

The licensing cost depends on the partners and the relationship between the company and the partners. We can get some discounts. We have a combination of licenses. We have some Business licenses and also some Enterprise licenses. Google does not directly deal with the billing fee.

Google is in a growing phase of IdP. The service is not full-fledged. I consider it an IdP. I am a fan of Google when it comes to emailing and other services. However, for user and access management, I would always opt Microsoft. The product is missing security features and a few other key features like attributes and dynamic group conditions that are required for ABAC and RBAC. 

The solution needs to improve the key features. Google is a very cool tool to leverage licensing. For the last one and a half years, they were on a litigation hold for the user's email box and drives. Overall, I would rate the product a six out of ten.

We use Google Cloud Identity for user management and administration.

The most valuable feature of Google Cloud Identity is its stability. The solution's multi-factor authentication (MFA) capability is good.

The solution's storage capacity could be increased.

I have been using Google Cloud Identity for six months.

I rate the solution an eight out of ten for stability.

Google Cloud Identity is a scalable solution. Two users are extensively using the solution in our organization, and we have plans to increase the usage.

I rate the solution an eight out of ten for scalability.

I previously used Azure. I switched to Google Cloud Identity because it was easier and cheaper.

The solution's initial setup wasn't very easy.

We implemented Google Cloud Identity through an in-house team. It took me one week to deploy the solution.

Google Cloud Identity has a yearly licensing fee, but I had some discounts from the hosting provider.

On a scale from one to ten, where one is cheap and ten is expensive, I rate the solution's pricing a three out of ten.

Google Cloud Identity is a cloud-based solution. I would recommend Google Cloud Identity to other users. It is the easiest and the cheapest solution for a startup or new company.

Overall, I rate the solution an eight out of ten.

The sole use case is to achieve a unified account experience across various platforms, specifically with Google Cloud Identity.

It's a data field list aiding in the onboarding and offboarding process. It enables centralized security control for the account, eliminating the need to manage it across multiple platforms.

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.

If I were to suggest enhancements, it would mainly revolve around ensuring compatibility and maximizing integration options with various services.

I've been using Google Cloud Identity for about two or three years.

I would rate the stability 10 out of 10. 

I never utilized it, and I never submitted any tickets or similar requests.

The implementation was done in house. Our IT team, which was quite sizable, had the capability to handle it. Maintenance might typically require one or two team members. The roles involved were usually IT engineers and IT associates.

The advice I've offered is fundamental and not specifically tied to Google Cloud Identity. It's more about understanding and evaluating tools that align with your needs and seamlessly integrate with your existing TechStack. Price may not be a decisive factor, as my understanding is that you aim to be competitively priced compared to other competitors.

On a scale of one to ten, I would rate it eight.