SAP SuccessFactors to Entra ID and Active Directory: Joinly vs Microsoft's native provisioning

What Microsoft gives you for SAP SuccessFactors

Microsoft ships an inbound provisioning connector for SAP SuccessFactors. The Entra provisioning service reads SAP SuccessFactors itself and writes users to Microsoft Entra ID, or — through the Microsoft Entra provisioning agent — to on-premise Active Directory. Attribute mappings and scoping filters are configured in the Entra admin centre. What happens around the account (groups, licences, the leaver process) is not part of the connector: Microsoft positions Lifecycle Workflows, part of Entra ID Governance, for that.

What Joinly adds

Joinly starts where the Microsoft route starts, at SAP SuccessFactors, and goes further on both ends.

• A ready-made SAP SuccessFactors import plugin, reading the Employee Central OData API with oAuth 2.0 (SAML Bearer Assertion / X.509) — no deprecated basic auth — no client to build or host.
• The rules: which department, job, location or legal entity maps to which groups, licences and organisational unit. Microsoft's mappings move attributes; Joinly's rules decide access, and record the reason per assignment.
• Both directories from one source: Entra ID through Microsoft Graph, on-premise Active Directory through the Joinly AD Agent (outbound only, no provisioning agent to install and no inbound rules), so hybrid organisations do not run two pipelines.
• A brake: a dry run with an Excel export, thresholds per run, read-only mode, and a hard stop when an evaluation would revoke more than 20% of assignments at once.
• Beyond the directory: shared mailbox, out-of-office, SharePoint and Teams, a ticket in TOPdesk or Freshservice, an SMS with the first-day credentials, a webhook to any application — as steps in the same workflow.
• An audit log per mutation with its source and the workflow that caused it, which is the evidence an ISO 27001 or NIS2 auditor asks for.

Side by side

When Microsoft's route is enough

If Entra ID is your only target, your team is at home in the Entra admin centre and Lifecycle Workflows, and access beyond birthright groups is handled elsewhere, the native SAP SuccessFactors connector can carry you. Be honest about the mover: a change of department in SAP SuccessFactors updates an attribute, and something still has to translate that into the right groups.

When you want Joinly

When there is an on-premise Active Directory next to Entra ID. When the answer to "why does this person have this group" has to come from a rule, not a memory. When you want to see what a run would do before it does it. When offboarding has to reach the mailbox, SharePoint and the service desk, not just the account. And when an auditor will ask for the log.

Can I use both?

Yes. Joinly can deliver its result to Microsoft's API-driven provisioning endpoint as SCIM 2.0 bulk requests — to Entra ID or, through the provisioning agent, to Active Directory. Then Joinly reads SAP SuccessFactors and applies the rules, and the Entra provisioning service does the write. The SCIM page for SAP SuccessFactors describes that route.