Sandhya,

Our organization deployed ADFS before looking at alternatives. For us, ADFS was high-maintenance and required a lot of infrastructure. This undifferentiated heavy lifting added no specific value to our Organization's mission. We looked at Azure B2C and Azure Active Directory. While there are some parallels, the decision to go with OKTA became very clear when considering:

• Support Experience (Technical, Contracts, Sales, PS) with OKTA is in an entirely different universe compared to Microsoft. You really have to factor in a Premier Support agreement to get anything close to comparable to what comes included with OKTA.
• Roadmap. Microsoft, even with our participation in their Azure Identity Advisors group, is convoluted and not very predictable. OKTA has been open and honest in providing short, mid, and long-range product vision and plans.
• Pre-built Integrations. With ADFS, you're setting up every single integration with a Tier 2 or above engineering resource that understands identity. With Azure AD, it does get easier, but the catalog is not exactly superb. OKTA's Integration Network is comprehensive, growing, and allows even a Tier 1 engineering resource with the most basic concepts of Identity to setup Federation in most applications.

If absolute lowest cost is your objective, OKTA may not be the best fit. If you see identity as a core part of your long-term business success and seek long-term value as a primary evaluation criteria, OKTA is likely a top contender.