Which connection type? SCIM, SAML, OAuth or OpenID

@Steph O'Brien

You can use any protocol to integrate your application with Azure AD.

First you need to check and confirm as to what authentication protocols does your web application supports.

OpenID, SAML and Oauth are the authentication protocols that Azure AD supports.

OpenID and SAML are both authentication and authorization protocols. Oauth is an authorization protocol.

Integrating your application with Azure AD with OpenID or SAML would handle both authentication and authorization.

You can refer to below article to get more information about authentication protocols supported by Azure AD,

https://learn.microsoft.com/en-us/azure/active-directory/develop/authentication-vs-authorization

How Open ID connect authentication works:

https://learn.microsoft.com/en-us/azure/active-directory/fundamentals/auth-oidc

SCIM is a provisioning service. Azure AD make use of SCIM to provision user, and group from Azure AD to integrated applications.

You cannot use SCIM for authentication.

https://learn.microsoft.com/en-us/azure/active-directory/fundamentals/sync-scim

https://learn.microsoft.com/en-us/azure/databricks/administration-guide/users-groups/scim/aad

https://learn.microsoft.com/en-us/azure/active-directory/app-provisioning/how-provisioning-works

Let me know if you have any further questions.

Please "Accept the answer" if the information helped you. This will help us and others in the community as well.

SAML and OIDC are for authentication (i.e.: is this user who they say they are). OAuth is an authorization standard - i.e. "What resources does this user/other entity have access to". SCIM is a standard for provisioning of identity data (users, groups/members, etc) across systems.

Between SAML and OIDC, OIDC is more modern, SAML is more widely adopted thanks to being around longer. You can potentially implement either or both of those to cover the initial user authentication/sign-in experience between an identity provider (IDP) and your app. If you adopt OIDC, you'll also want to implement OAuth 2.0.

Whether SCIM is needed to enrich the quality of user/identity data present in your app is a separate question.

Hi Steph,

Is this a corporate app or a public facing app?

If it's corporate then likely SAML is the way to go.

The advantage of SAML may be that if your users are already authenticating with Azure AD, they should not have to authenticate again with your app.

If this is a public facing app and your users don't use Azure AD to authenticate then SAML may provide less advantages.

Also consider future requirements as some things may only support oauth2 over saml.

https://auth0.com/intro-to-iam/saml-vs-oauth