Identity and access management
Factorial to Entra ID integration: Microsoft accounts from Factorial, next to Factorial's Azure app
With an integration between Factorial and Microsoft Entra ID, every new employee from Factorial gets a Microsoft account with job title, team, legal entity and manager, and the account is blocked after the end date. Factorial itself offers a Microsoft Azure app which, according to Factorial, mainly handles single sign-on and keeps user data up to date; KoppelHet comes in when you want accounts created, changed and blocked from Factorial, with your own rules for entities, groups and licences.
What the integration does
Organisations with Factorial and Microsoft 365 often let staff sign in to Factorial with their Microsoft account through the Azure app. IT still creates the accounts themselves by hand after a message from HR, and leavers sometimes stay active for weeks.
- HR records a new employee in Factorial at the Dutch legal entity.
- Factorial reports the hire; KoppelHet creates the Microsoft account, disabled until the start date.
- Groups and licence follow from legal entity, team and job.
- On a team or job change KoppelHet adjusts department, manager and groups on the effective date.
- After the end date the account is blocked; sign-in to Factorial through Microsoft stops with it.
What to watch for with Factorial and Microsoft Entra ID
- According to Factorial, its Microsoft Azure app is free and meant for single sign-on, with up-to-date user data and access management as benefits. Factorial does not describe how data goes from Factorial to Entra ID. KoppelHet handles exactly that flow, and single sign-on can stay as it is.
- If employees sign in to Factorial through Microsoft, that access depends on the Microsoft account. When KoppelHet blocks the account after the end date, access to Factorial and the other Microsoft apps stops too.
- Factorial has a separate stream of HR changes per type, such as hire, contract change and termination. KoppelHet reads it per type and per legal entity, so only the entities belonging to this Microsoft environment produce accounts.
- Contracts are stored in Factorial as versions with an effective date. A new job from the first of the month changes the account on that day, not at the moment HR enters it.
- Microsoft requires a country on the user for a licence. The country comes from the legal entity in Factorial, so a colleague in Spain and one in the Netherlands each get the right usage location.
- Factorial retries a failed notification up to twenty times in 48 hours and then switches the subscription off. KoppelHet monitors that and compares all active employees with Entra ID every day, so a departure does not depend on a single notification.
- Factorial puts the API version with a date in the address. KoppelHet tests a new version in Factorial's demo environment first, so a change on Factorial's side does not block accounts.
This integration is also part of joiner, mover, leaver.
How we build and run it
- The integration runs on the KoppelHet platform, hosted in a data centre in the EU.
- Every sync and every error is visible in the functional log; on an error your administrator is notified.
- A change that cannot go through is not half-applied but queued for another attempt.
- KoppelHet is ISO 27001 certified. Data travels encrypted and stays on the platform no longer than needed.
- After go-live we manage the integration and adjust it when your process changes.
- The integration fits next to your existing integration layer. Only the fields in the design are transferred; the platform keeps no register of its own.
Implementation and price
This is not an app you switch on. We build the integration for your organisation on our platform, with building blocks we reuse on every project. So it is custom work that does not start from scratch.
A consultant prepares the intake and analyses both systems. We then record the mapping and exceptions field by field, test in the test or acceptance environment and go live at a moment you choose. Costs are a one-off amount for the setup and a monthly amount for platform, monitoring and support.
Frequently asked questions
Does this also work with on-premises Active Directory?
Yes, through a small program in your network.
What about audit logging, GDPR and our integration platform?
Every action of the integration is in the audit logging of the KoppelHet platform. You are the controller and KoppelHet is the processor, under a data processing agreement; salary and absence from Factorial do not go to Entra ID. An existing integration platform is left alone.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- KoppelHet reads Factorial through the Factorial API (version 2026-07-01 in the path) with OAuth 2.0 - employee updates (new hires, contract changes, terminations) filtered on legal_entities_ids, employees, contract versions, teams and legal entities. Webhook subscriptions with up to twenty attempts in 48 hours, then switched off.
- Entra ID is written through Microsoft Graph (user) with employeeId (at most 16 characters), givenName, surname, userPrincipalName, jobTitle, department, companyName, manager, usageLocation, employeeHireDate and accountEnabled, or through API-driven inbound provisioning (requires Entra ID P1 or higher).
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Factorial | Field in Microsoft Entra ID | Notes |
|---|---|---|
Employee id | employeeId | |
first_name en last_name | givenName en surname | |
Naamgevingsregel per entiteit | userPrincipalName en mailNickname | |
Functie (contract version) | jobTitle | |
Team | department | |
Legal entity | companyName | |
Manager | manager | |
Land van de legal entity | usageLocation | |
Startdatum | employeeHireDate | |
Einddatum (termination) | accountEnabled = false |
Related
Factorial → 4PS Construct
Factorial to 4PS Construct integration: fitters and site managers with their cost centre as a dimension in 4PS
Factorial → Active Directory
Factorial to Active Directory integration: domain accounts from Factorial
Factorial → ADP iHCM
Factorial to ADP iHCM integration: contract versions and terminations of the Dutch entity to ADP
Factorial → AFAS Profit
Factorial to AFAS integration: employees and contracts from Factorial in AFAS Profit Payroll