Bring Cust into the access process your IT team already runs. Microsoft Entra ID gives your team single sign-on with their work accounts, while SCIM provisioning keeps Cust membership aligned with changes in your directory.
Use OpenID Connect for sign-in, verify your organization’s domains, and choose when to require SSO. With provisioning enabled, Entra ID can create members, update their names and roles, and remove their Cust access when they are deprovisioned.
Members sign in to Cust through your configured Microsoft Entra ID application. Require SSO for verified domains to keep sign-in under your organization’s identity controls.
Use SCIM to provision new members, keep their names current, and remove access when someone leaves. Manage provisioned members from Entra ID as your team changes.
Map Entra ID app roles to Cust’s Admin, Builder, and Member roles. Keep access appropriate for the people building workflows, managing the workspace, and working with customers.
In Cust’s Single sign-on settings, choose Other OpenID Connect provider. Register the displayed callback URL in your Entra ID web application, then add its issuer URL, client ID, and client secret in Cust.
Verify your organization’s domains and enable single sign-on. Check that members can sign in before requiring SSO for those domains.
Use the SCIM base URL and token from Cust in Entra ID’s provisioning configuration. Map member attributes and app roles, then test provisioning with a member before rolling it out.
Connect with our team to plan Microsoft Entra ID sign-in and provisioning for your organization.
Need help? Contact us at [email protected]