Amazon Cognito vs. Microsoft Entra External ID

Well Suited

1. B2C mobile and web apps with a high number of users.
2. Cheaper and cost-effective.
3. If the other pieces of the infra are already using AWS services like Lambda, S3, Pinpoint, etc.

Not Suited For:

1. Advanced use-cases (Biometrics based authentication) Email, and other MFA channels.
2. For any use-cases needing SCIM.
3. Customized flows of SSO, and MFA will need a layer on Lambda and other AWS services.

Incentivized

It is not easy to calculate the actual ROI due to the difficult quantification of all factors, but it certainly contributed a lot in protecting, monitoring and controlling access to our system. It also made it much easier to detect vulnerable external users with simple and "easy to hack" passwords they use on multiple apps.

• Strong integration with React.js and client-side applications
• Easy to bridge Cognito identities with the rest of the AWS ecosystem
• Easy to store user profile data directly in Cognito rather than having to build additional services/endpoints
• Easy integration with AWS Lambda to extend and add sophistication to the service

Incentivized

• Single sign-on simplifies access to your apps from anywhere
• Strong authentication for your customers using their preferred identity provider.
• Integrating with social accounts such as Facebook or Google+

Incentivized

• Amazon Cognito has a bit of a learning curve. You need to learn its concepts and terminology. The documentation does not describe some topics comprehensively.
• Some Console screens would benefit from improved search and filtering options.
• When another AWS product (e.g., SageMaker) configures Cognito on your behalf, it is not clear what you're getting. For example, the expiration of a temporary password was configured but never communicated.

Incentivized

• Troubleshooting diagnostic logs effectively requires VS Code
• Group and role management requires additional effort
• The programming model (XML) could use some developer experience love

Incentivized

All the features AWS Cognito offers gives the user the options they need without making it too complicated. Your customers will be happy. On the administration site usability is also great. After a small learning curve, you can setup Cognito for your usage

Incentivized

AWS Support overall is poor. Your main resources are trainings and the docs, and the docs can be very confusing. Using Cognito well involves having a developer learn it deeply and help support your team in understanding it. That said, Cognito's competitors also have dismal support and even worse documentation, so while this isn't a strength for Cognito it may still be the frontrunner here.

Incentivized

They are ideal tools to create a secure and unique login experience for our applications. Thanks to its API authorization, Amazon Cognito ensures connections to applications that are secure.It is easy to use and provides easy access to files and applications that you need to complete your goal.

Incentivized

Each one of these alternatives has pros and cons. PingOne from Ping Identity states they "help deliver the secure and seamless customer experience to win battles for customer acquisition, retention, revenue, loyalty, and trust." While that may be the case, they did not fit our needs. We have a complex system and it did not seem to fit into our business.

Incentivized

• ROI is great for Amazon Cognito Overall.
• It is included in the AWS Free Tier so you can use it for a good amount without paying, so the software can be tested beforehand.
• The paid pricing is also affordable, so a positive impact on ROI.

Incentivized

• Having monthly active users billing was cost-effective.
• Helped with the IT support that was already managing the Azure platform of the company; this helped to manage the costs better and optimize them.

Incentivized