NewBuild any Microsoft Entra ID attribute without code — conditions, text and date logic, no scripts. See how →
Integrations

Built for the Microsoft ecosystem. Open to your HR systems.

The complete map of where IDFusion plugs in — sources we read from, targets we write to, and notifications for anything downstream.

The complete picture

One platform between your HR systems and your Microsoft estate.

HR data flows in from the left, IDFusion interprets it, and Microsoft Entra ID carries it out to the right — Access Packages, Lifecycle Workflows, Custom Security Attributes and, for hybrid organisations, on-premises Active Directory. Notifications keep everything else informed.

SOURCES TARGETS IN ENTRA ID Dayforce Dynamics 365 HR SuccessFactors Affinity CSV & JSON files Generic REST PLATFORM IDFusion provisions MICROSOFT Entra ID On-Premises AD (Hybrid) Access Packages Lifecycle Workflows Custom Security Attributes Notifications sent directly by IDFusion
HR sources

Start from the system your people data already lives in.

Pre-built connectors for the HR systems used by enterprise organisations, plus file import and a generic REST connector. We are continually expanding pre-built connectors and our team will build a custom connector if your identity source system isn’t listed. Every source follows the same journey — merge, classify, model, provision.

Dayforce (Ceridian) Available
HR system

Full employee profiles, org structure and the manager chain — imported on your schedule.

Microsoft Dynamics 365 HR Available
HR system

Worker records straight from your Microsoft estate, kept in step with every change.

SAP SuccessFactors Available
HR system

Employee master data from SuccessFactors, built to handle large workforces.

Affinity Available
Payroll & HR

Payroll-grade employee data — a natural supplementary source beside your HR system.

Microsoft Entra Guests Available
Guest lifecycle

Bring B2B Entra Guest accounts into IDFusion, then assign business roles to govern access the same way you do for employees.

CSV and JSON files Available
File import

Turn any list — vendors, contractors, seasonal cohorts — into managed identities.

Generic REST connector Available
HR systems with an API

Connect an HR platform that offers a REST API, with fields and schedules configured in the portal.

Workday Available Q4
HR system

Worker records from Workday, following the same journey as every other source.

TechnologyOne Available Q4
HR & payroll

Employee data from TechnologyOne, following the same journey as every other source.

On the roadmap
  • BambooHR Roadmap
  • Oracle HR Roadmap
  • ServiceNow HR Service Delivery Roadmap
  • Chris21 Roadmap
Talk to us about timing if one of these is your system of record.
Targets

Cloud, hybrid, and as many tenants as you run.

Personas decide where each person lands — one Entra ID tenant or several — and hybrid organisations can provision to on-premises Active Directory through Microsoft Entra. Each target keeps its own username rules and attributes.

Microsoft Entra ID Available
One tenant or many

Accounts created and maintained in every Entra ID tenant your personas point to — corporate, partner or subsidiary.

On-premises Active Directory Available
Hybrid, through Microsoft Entra

Provision to on-premises Active Directory through Microsoft Entra, with each account placed in the right organisational unit.

The Microsoft identity stack

Deep, native integration on the Entra ID side.

IDFusion doesn’t treat Entra ID as one target among many — it’s the whole point. Once an account exists, IDFusion drives the parts of the Microsoft identity platform that govern what that person can reach.

Entra Access Packages
Created for every Business Role

IDFusion creates the matching Access Package for each Business Role in every target tenant; Entra ID grants it while someone holds the role and removes it when they no longer do.

Entra Lifecycle Workflows
Triggered by classification

Joiner, mover and leaver workflows run from the lifecycle events IDFusion classifies — not from guesswork.

Custom Security Attributes
Sensitive identity fields

Protected attributes for fields too sensitive for a standard profile — citizenship, clearance level, cost-centre tiers — visible only to authorised people. Standard and multi-valued attributes stay in sync too, with full audit history.

Setting up a connection

Every connector follows the same three steps.

No custom code — connect, map, schedule. Configured through the portal, with our team alongside you during onboarding.

01 Connect securely

Connect to your HR system with credentials held in a dedicated, encrypted store for your organisation.

02 Map your fields

Match every HR field to your identity model through the visual mapping interface — renamed, reformatted, or combined.

03 Set the schedule

Imports run securely in the background on the cadence you choose.

Step 02, up close

Your fields, mapped your way.

Every organisation names things differently. Each HR field is mapped to your identity model — renamed, reformatted, or combined — and the mapping is configured per client, not fixed by the product.

FROM YOUR HR SYSTEM TRANSFORM TO YOUR IDENTITY MODEL
Preferred first name rename Given name
SENIOR ENGINEER title case Senior Engineer
Department code 4410 look up Engineering
First name + surname combine Display name
Manager’s employee ID resolve Manager

Configured per client through the visual mapping interface — add, rename or transform fields without touching the connector. Need something more involved? The no-code attribute builder handles conditions, text and date logic.

Next step

Don’t see your HR system?

We’re continually adding connectors, and we build custom connectors for systems we don’t yet support — with others already on the roadmap. Tell us what you run.