Summary
FranConnect supports Email OTP as its MFA method and SAML SSO with Microsoft Entra (Azure AD). SSO can run alongside native FranConnect logins during a transition, and existing users can be mapped to SSO without creating duplicate accounts if configured correctly. During setup, the SAML Groups option may not appear until the browser is refreshed.
MFA Capabilities
- MFA can be enabled, but it applies system-wide — it cannot be scoped to specific user roles only.
- The only supported MFA method is Email OTP (no authenticator app or SMS/phone OTP support).
- Related article: How to Manage Password and MFA Settings in FranConnect
SSO Capabilities (Microsoft Entra/Azure AD)
- FranConnect supports SAML SSO with Microsoft Entra (Azure AD). Reference article: Configuring SAML SSO: Microsoft Azure.
- Dual authentication during transition is supported. Enabling Entra SSO does not disable or disturb existing native FC login users. Both can run in parallel until the customer is ready to fully cut over.
- Native login is only disabled as a separate, deliberate step, once the customer is ready for an Entra-only setup).
Migrating Existing Users to SSO
- Leave “Is Default SAML SSO?” unchecked to keep native FranConnect login working alongside SSO — this enables a gradual rollout instead of a hard cutover.
- Existing accounts are not automatically converted to SSO. The link between an SSO identity and an existing FranConnect account is made via the Login ID/Username claim — map an Azure attribute (e.g., employee ID) to the FranConnect Login ID.
- If the mapped value matches an existing FranConnect username, that user authenticates via SSO going forward, with no new account created.
- If it doesn’t match, and “Is Provision User?” is checked, a new account is auto-created at first SSO login (JIT provisioning). Mismatched identifiers can therefore create duplicate accounts — test this mapping carefully before rollout.
Known Setup Issue: SAML Groups Not Appearing
- During setup, customers may reach the “Creation & Addition of SAML Groups” step in the documentation but not see the SAML Groups option in the UI.
- Resolution: This is typically a stale-session UI issue. Refreshing the browser causes the SAML Groups option to appear, as it was enabled by a prior configuration step.
- If a customer reports this, ask them to refresh their browser before escalating.
Recommended Customer Guidance Flow
- Confirm the end-state goal (e.g., all auth via Entra).
- Point to Configuring SAML SSO: Microsoft Azure.
- Explain dual-auth support and that native login is disabled only as a deliberate later step.
- Walk through the Login ID/Username claim mapping and provisioning behavior to avoid duplicate accounts.
- If they report missing SAML Groups options, advise a browser refresh first.
- For deeper configuration specifics, escalate to engineering once the customer confirms readiness to proceed.