Connect BigCommerce with Microsoft Entra ID (Azure Active Directory / Azure AD) to centralize admin logins, enforce MFA and conditional access, and simplify B2B identity management at scale.
• BigCommerce admin authentication is federated to Microsoft Entra ID (Azure Active Directory / Azure AD) via SSO using standard SAML 2.0 or OIDC flows, depending on the chosen app pattern.
• Admin identities are matched to Entra ID users through stable attributes (typically email/UPN), with controlled claim mapping for name and identifier fields.
• Conditional access evaluation and MFA challenges are enforced by Entra ID during the sign-in transaction, with results returned to BigCommerce as the authentication assertion/token.
• Session initiation is handled through IdP-initiated and/or SP-initiated login, with redirect and relay-state handling to return admins to the correct BigCommerce context.
• User lifecycle changes in Entra ID (disable, delete, group changes) are reflected at next authentication attempt, preventing access when the identity is no longer valid.
• Sign-in events and failures are logged in Entra ID, while BigCommerce admin activity remains in platform logs, supporting cross-system audit trails and incident review.
.png)
We configure Entra ID as the identity provider and map users, groups, and roles so BigCommerce admins sign in via SSO under your existing IT policies.
Yes – MFA and conditional access are enforced in Microsoft Entra ID, while BigCommerce relies on the SSO assertion, keeping controls consistent across apps.
Yes – access can be scoped using Entra ID groups and assignment rules, so only approved teams can reach BigCommerce admin and sensitive areas.
Accounts are managed in Entra ID, so disabling a user or removing them from a group cuts off BigCommerce admin access immediately.
scandiweb’s engineers handle the integration end to end, backed by 2,100+ eCommerce projects delivered since 2003. We validate login flows, fallback access, and auditability before go-live.










