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.
$6
per user/per month
PingOne from Ping Identity
Score 8.5 out of 10
N/A
The PingOne Cloud Platform from Ping Identity in Denver, Colorado is an identity management and access solution (IAM) for enterprises. Features of the products include single sign-on, multi-factor authentication, user management with directory, provisioning and deprovisioning. The solution is presented as a comprehensive, standards-based platform that allows users and devices to securely access any service, application or API from any device. Designed for hybrid IT…
$20,000
per year
Pricing
Microsoft Entra ID
PingOne from Ping Identity
Editions & Modules
Premium P1
$6.00
per user/per month
Premium P2
$9.00
per user/per month
Essential
$20,000
per year
Plus
$40,000
per year
Premium
Contact Sales
Offerings
Pricing Offerings
Microsoft Entra ID
PingOne from Ping Identity
Free Trial
Yes
Yes
Free/Freemium Version
Yes
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
Try PingOne for Customers for free. Sign up for a free 30-day trial of PingOne for customers.
It is a lot easier to administer Microsoft Entra ID compare to Ping. Microsoft Entra ID is a lot more intuitive and easy to understand. Microsoft Entra ID is more flexible when integrating SaaS solutions. Implementing passwordless and conditional access policies to add an …
License and some capabilities are better in Microsoft Entra ID
Verified User
Project Manager
Chose Microsoft Entra ID
I have been part of teams that have used both Oracle as well as Okta Identity Cloud. I think Azure AD falls between the two in performance and functionality. I think Oracle has been completed outdated as the UI is very clunky and old fashioned and seems like we are still stuck …
I found both platforms compelling from an ease of use and user experience perspective. The decider for me was cost driven as I had already used Ping to drive a self-service transformation in a prior organization, and I intended to do the same at this one. Okta had issues with …
It is especially good for organizations that are otherwise in the Microsoft ecosystem (Microsoft 365 applications). Microsoft Entra ID is really well supported sign-in method in various SaaS-applications and they often have step-by-step guides how to deploy the SSO with Microsoft Entra ID. It's less suitable for organizations that might use other productivity tools than M365 or do not have Windows-based computers.
Really like [this] solution, it fits our requirements 100%. There are unlimited possibilities to extend the product, either by creating additional adapters or selectors. We really like the policy management level in PingFederate. It's extremely helpful when we can specify customer journey per many different requirements like user location, application type etc. As well, both StepUp and TopDown authentication flows were implemented [easily].
Single Sign-on helps ease the user experience, allowing users to avoid typing multiple passwords.
The identity and management are straightforward to use and easy to connect to other applications, as well as third-party applications.
The support of remote work. Nowadays, many people work from home and need to access their accounts. Microsoft Enterprise ID gives secure access to the company data.
Based on open standards, we can use as much or as little of the Ping suite as we like, depending on which other technologies we've already implemented.
Continuous innovation and product enhancements have ensured their products continue to meet our rapidly evolving needs.
Ping Identity has been an outstanding partner, starting with the RFP process and continuing to this day, years after the sale. They are focused on our success at every level of the company and are highly responsive to our needs, issues, and product suggestions.
Probably the most primary thing is just the interface itself. It's frequently changing and so oftentimes we kind of have to go back and redocument our processes for our IT staff because the steps that they would take to perform a task one month. Now it's a totally different staff, new dashboard, even a new name for the product or the feature. So it would be nice if that stuff was a little bit more consistent.
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 mean it's pretty good. It is click, click. I mean, oftentimes I can go to the expert or layer two support to get help. Suddenly I go to them. So it has to be pretty useful to be honest. I do a lot of, and there's a lot of, you could do research quickly online to find out how to do certain things. I think that's the only thing we can improve to in terms of kind of a best practice path is setting up it. But because I'm it profess of tons of years in co-management services, I can figure it out. But for others they may not be able to figure it out. You still need an IT person of course to translate all of that. But to me pretty straightforward. I come from the days of directory from 2008, 2000, Microsoft server 2000.
Easy to use; all UI's are user friendly and easy to learn.[The] possibility to use API is [a] big value as well. We really like integration with CyberArk; with it we can manage privileged accounts according to company standards without breaking any rules, and we can be 100% sure that only approved persons will have administrative access.
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
Ping's support is willing and attentive, but if I am in a position to engage them I am often at a point where most of the usual support engineers would not be in a position to answer the questions I have. However, Ping has been more than willing to engage their product and development teams with our organization as we take advanced deployment and use case challenges to them.
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've used other Microsoft products and we've also used some standalone products, like each application you can have its own identity, so we've looked at some of those too, but we try to use the Entra ID as much as possible because it offers a wider range of reliability.
This solution is selected before my time so, not much influence ,but product allow to customized and require decent ping skills to configure the solution. Okta and Other solutions are well suited in this category with some positive and some negative capabilities. it must say that Auth0 is the best option with Azure Identity to move ahead.
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.
I think it's had positive. It's enabled us to make authentication easier and more streamlined across the organization from frontline workers to back office workers.
It's allowed us to really adopt authentication policies and methods that suit that user and their work environment.