Skip to content
m0vom0vo

Enterprise identity

Microsoft Entra SSO that lands people in the right organization

m0vo integrates with Microsoft Entra ID using OpenID Connect. Each organization can register its own Entra app—client ID, secret, and tenant—so employees sign in with work accounts and land in the correct org context.

What you get

  • Per-organization Entra (OIDC) configuration managed by org admins
  • Standard redirect URI for Entra app registration and token exchange
  • Work-account sign-in without a separate catalog password when policy allows
  • Org lookup on the login page so staff find the right enterprise SSO path
  • Complements Google social login and email signup for mixed workforces
  • Server-side secrets encrypted at rest

Why Entra matters for IT product teams

Portfolio and contract data is sensitive. Enterprises already run identity on Microsoft Entra ID (formerly Azure AD). m0vo meets that standard: staff use corporate credentials, conditional access and MFA stay with Entra, and m0vo never needs a second password store for those users when SSO is enabled.

How org-scoped Entra configuration works

Org admins (or platform admins) enable Microsoft Entra under organization settings: tenant ID, application (client) ID, and client secret. m0vo uses industry best practices to integrate, and provides a login path keyed by organization. Only that org’s Entra app is used for its members—tenants stay isolated.

Alongside social and email identity

Not every collaborator lives in Entra. m0vo still supports email signup with confirmation, and Google for personal or mixed environments. Enterprise SSO is additive: enable Entra where policy requires it, keep social or email where it does not. Linked identities appear on the user profile so people understand how they signed in.

Security of the SSO path

Authorization codes are exchanged server-side with PKCE where applicable; sessions are iron-session sealed cookies with configurable idle timeout. Client secrets are never returned to the browser after save. Failed or cancelled IdP flows return users to login with a clear message—no partial sessions.

More platform capabilities