Google Cloud Identity is a unified identity, access, app, and endpoint management (IAM/EMM) platform that gives users access to apps with single sign-on, provides multi-factor authentication to protect users and company data, and enforces policies for personal and corporate devices and endpoints.
N/A
Microsoft Entra ID
Score 8.8 out of 10
N/A
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.
Microsoft Entra ID offers the same or very similar services to the other products but in a package that is familiar and recognizable to everyone. It enjoys better community support and world-class security and reliability.
For example, if the system you are building is a general application service that does not primarily focus on ID management, it would be wise to use a service like Google's rather than developing your own IDaaS. While there may be cases where an IDaaS other than Google's is acceptable, Google is likely one of the best solutions when considering user recognition and ease of use. On the other hand, Gmail addresses are commonly used for other purposes, and users may not pay much attention to password management, so you should avoid using them for systems that require security. To strengthen security, you should consider making multi-factor authentication mandatory, etc.
That one is tough. It's just easy to integrate the sign-on portion with other products from other companies. Like BluePoint or Podint. It's very easy to integrate the user information with others. Using Android ID to register an application with other companies' applications.
The first thing is that it's a really good platform to make a whole inventory of your hardware and software that you already have in the organization. It's very simple. It's very easy to look at what you have in the whole organization. And after that, start applying, for instance, some policies, some solutions in terms of zero trust access using MFA as a second form of authentication. So, these are the ways we use the MTIV platform.
This time, I investigated it in advance, and it worked as expected, so I don't have any specific ideas for improvement.
Additionally, if we were using another IDAAS, it would have been beneficial to have knowledge on how to integrate it with Google tools, along with some relevant case studies.
There is one thing that we lost since we migrated from Active Directory and it is the user expiration date. If I have an external that I know will work for six months, I have to manually check or put some kind of reminder. I cannot set an expiration date in Microsoft Entra ID. I still don't know why.
MSFT Entra ID has been essential for managing our geographically dispersed team. We're confident that it will scale with us as grow, and we'll be able to take advantage of additional security and ID management features as they become necessary. Being able to centrally manage our user access from anywhere with a small support team is such a relief.
I chose Google because I thought it would be the best fit, but I didn't fully consider other cloud platforms (Azure, AWS, etc.), so I rated it 8. We assume that current Japanese users are familiar with Google, because we feel that there are far more people with Google email addresses than those with IDs on other cloud services.
It's not complex. It works as configured, right? There's a lot of granular rules, and it'll get very specific if you need it to. But for many of our security capabilities, especially for mid-market enterprises, I think you can get all the capabilities you typically need with OnStar.
I have not needed to engage support for anything at this time. I have been able to find the answers either online or in a knowledgebase. I tried to skip the question but it would not let me, so I rated a 9 based on other interactions with Microsoft support I have had
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.
We adopted Google Cloud Identity as an additional feature because it allowed us to integrate with it using multi-factor authentication. The IBM Cloud platform remains valid, and we have no plans to discontinue its use for identity management. From the user's perspective, we simply added more authentication options. This also ensures we are prepared for future use when multi-factor authentication becomes available for user apps on the IBM Cloud.
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.
Microsoft Professional Services' technical knowledge is appreciable as consultants design the solution as per customer requirements. Mapping of features per user specifications and assisting Customer IT engineers to implement so they can manage and administer the services.
From a business perspective, there were two steps.
First, we switched from our in-house ID management system to a cloud service. This allowed us to focus our development resources on application development.
At the same time, we were able to localize the handling of personal information, which resulted in increased efficiency in management aspects, including handling external inquiries, and in the development of encryption.
The second step was adding Google Cloud Identity as an option.
This allows more users to easily use our services. It can be said that this has improved user convenience.
I expect Google to accommodate future changes in authentication requirements, such as biometric authentication.
Definitely, I can consider this one a positive because, as I mentioned earlier, it's a tool that can help our internal ID team track end users' activities in their sign-in logs and a lot of other things, which is really good and helpful for us.
