Microsoft Entra ID vs. PingOne from Ping Identity

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.

Incentivized

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].

• 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.

Incentivized

• 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.

• 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.

Incentivized

• Solutions are attractive to engineers but harder to sell to upper management.
• Support was initially a challenge but has improved immensely.

Incentivized

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.

Incentivized

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.

Incentivized

As I mentioned earlier, efficiency and security are this software's bread and butter. The usability is very simple and straightforward, very user-friendly. As a result, it is efficient in a way that we can provide faster quality service to our merchants, and security in a way that our credentials will never leak since PingOne always values Personal Identifiable Information.

Incentivized

There has been a handful of outages but they have been either minimal or rarely severe

Incentivized

I could probably rate this a 10 but I'm always conservative on giving out perfect scored bt performance has not been a problem for us using Entra ID.

Incentivized

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

Incentivized

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.

Incentivized

Most training was internally produced

Incentivized

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.

Incentivized

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.

Incentivized

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.

Incentivized

The features are getting addresses per requirements and their value for Money. The proposed ROI and actual ROI build confidence.

Scalability is pretty trival for Entra ID. It's not difficult to manage a few or many accounts.

Incentivized

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.

• 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.

Incentivized

• Decreased overall number of help desk calls for password reset.
• Reduced time need for authentication; user[s] now have to authenticate once to be able to use more than 20 applications, instead of authenticating 20 times (per app).