Microsoft Entra ID

Integrate An Application

Microsoft Entra ID supports two protocols, OIDC (OpenID Connect) and SAML (Security Assertion Markup Language).

You can follow Microsoft documentation for OIDC integrations, also called "App Registrations" in Entra ID. These do not require special permissions for basic directory information release (name, email).

SAML integrations, also called "Enterprise Applications", require the following information:

  • Entity ID
  • ACS/Reply URL
  • SAML claims required by the app (such as "eduPersonUniqueId" or "mail")

Creating An Integration

You can use apps.identity.tamu.edu to create App Registrations & Enterprise Applications and view apps you own. The interface is self-service, adds automatic departmental tagging, and manages the lifecycle of the integration for you.

Understanding OIDC/SAML Protocols

  1. OIDC: To better understand OIDC and OAuth2, we recommend this Okta-published guide.
  2. SAML: For an explanation of the SAML protocol, see this guide from Duo.

App Compatibility

If you believe OIDC & SAML will not meet the needs of your application, please reach out to identity@tamu.edu.

Entra ID at Texas A&M

Texas A&M University has one primary Microsoft Entra ID tenant. The primary domain in this tenant is configured to syncronize objects in the Active Directory domain auth.tamu.edu to Entra ID.

For more in-depth technical information, Microsoft provides comprehensive documentation geared toward developers around Entra ID.