Azure AD
A cloud identity and access management service from Microsoft, now rebranded as Microsoft Entra ID. It provides single sign-on, multi-factor authentication, conditional access, and SCIM-based user lifecycle management, and is one of the mainstream identity providers for enterprise SaaS applications.
Timeline (last 90 days)
Directory sync uses the SCIM protocol to automatically push user and group information from enterprise directories (such as Okta and Azure AD) to SaaS products.
In enterprise scenarios, these permissions are usually configured centrally by administrators through Entra ID (formerly Azure AD) and are constrained by data loss prevention (DLP) and compliance policies.
Mainstream IdPs such as Okta, Azure AD, and OneLogin all natively support SCIM 2.0 outbound provisioning.
WorkOS's Directory Sync feature connects to enterprise identity providers (such as Okta, Azure AD and Google Workspace) via the SCIM protocol.
Single Source of Truth is a core principle in IAM, meaning that all user identity data is based on one authoritative system, with common implementation vehicles including Active Directory, LDAP, Okta, and Azure AD.
SSO is usually implemented by an identity provider (IdP), such as Okta or Azure AD.
Identity provider (IdP) registration is usually based on the OAuth 2.0 or OpenID Connect protocol, with AWS as the service provider trusting these identity sources.
Microsoft Teams meeting links are typically created via the onlineMeetings interface of the Microsoft Graph API, requiring an Azure AD app registration and the corresponding permissions.
Mainstream IAM platforms such as Okta, Azure AD, and AWS IAM typically record every authentication and permission-use event.
A typical use case of SCIM is: when an enterprise uses identity providers (IdPs) such as Okta and Azure AD as the authoritative identity source, SCIM is used to automatically push operations such as creation, update and disabling of employee accounts to downstream applications such as Slack, Zoom and Salesforce.
22 more timeline events
All Facts (20)
SSO implementation typically relies on standard protocols such as SAML or OIDC, integrating with enterprise identity providers such as Okta, Azure AD, and Google Workspace.
70%UnverifiedAzure AD has been renamed to Microsoft Entra ID.
60%UnverifiedDirectory sync uses the SCIM protocol to automatically push user and group information from enterprise directories (such as Okta and Azure AD) to SaaS products.
50%UnverifiedIn enterprise scenarios, these permissions are usually configured centrally by administrators through Entra ID (formerly Azure AD) and are constrained by data loss prevention (DLP) and compliance policies.
50%UnverifiedMainstream IdPs such as Okta, Azure AD, and OneLogin all natively support SCIM 2.0 outbound provisioning.
50%UnverifiedWorkOS's Directory Sync feature connects to enterprise identity providers (such as Okta, Azure AD and Google Workspace) via the SCIM protocol.
50%UnverifiedSingle Source of Truth is a core principle in IAM, meaning that all user identity data is based on one authoritative system, with common implementation vehicles including Active Directory, LDAP, Okta, and Azure AD.
50%UnverifiedSSO is usually implemented by an identity provider (IdP), such as Okta or Azure AD.
50%UnverifiedIdentity provider (IdP) registration is usually based on the OAuth 2.0 or OpenID Connect protocol, with AWS as the service provider trusting these identity sources.
50%UnverifiedMicrosoft Teams meeting links are typically created via the onlineMeetings interface of the Microsoft Graph API, requiring an Azure AD app registration and the corresponding permissions.
50%UnverifiedMainstream IAM platforms such as Okta, Azure AD, and AWS IAM typically record every authentication and permission-use event.
50%UnverifiedA typical use case of SCIM is: when an enterprise uses identity providers (IdPs) such as Okta and Azure AD as the authoritative identity source, SCIM is used to automatically push operations such as creation, update and disabling of employee accounts to downstream applications such as Slack, Zoom and Salesforce.
50%UnverifiedPortkey supports SAML 2.0, Okta and Azure AD SSO, role-based access control, and PII anonymization.
50%UnverifiedSAML 2.0 is the earliest XML-based authentication protocol widely adopted by enterprises, supported by mainstream IdPs such as Okta and Azure AD, but it is cumbersome to configure and difficult to debug.
50%UnverifiedDifferent customers may use different identity providers (Okta, Azure AD, Google Workspace, etc.), and each additional IdP type requires extra adaptation and testing work.
50%UnverifiedQuery-time real-time verification means every retrieval traces back to an authoritative identity provider (such as Azure AD or Google Workspace), which is consistent with the zero-trust principle of independently authenticating each access.
50%UnverifiedIAM Identity Center, formerly known as AWS SSO, supports integration with external identity providers such as Microsoft Active Directory, Okta, and Azure AD, synchronizing user and group information via SAML 2.0 or SCIM protocols.
50%UnverifiedEven though next-generation IdPs such as Okta and Azure AD already fully support OIDC, enterprise buyers still explicitly require SAML support in RFPs.
50%UnverifiedThe correct user mapping strategy is to use the combination of oid + tid (Tenant ID) as a stable primary key.
50%UnverifiedIn Azure AD, oid (Object ID) is the immutable unique identifier for each user within a tenant, remaining unchanged even if the user modifies their email address, UPN, or display name.
50%