Integration with BCS

Joinly reads your employees from BCS and uses that as the source of truth for access management. A new hire, a role change or a departure in BCS is translated automatically into accounts and permissions in Microsoft Entra ID, your on-premises Active Directory and your connected applications. You maintain the data once, where it belongs.

Over an API, not by exchanging files: Joinly collects the employees from an endpoint on your BCS environment, using its own authentication key. No CSV involved. How often that happens is up to you — hourly, daily or weekly, at a time you set. Most organisations run the import overnight, so a new joiner has an account waiting the next morning.

Only what is needed to decide on an account and the right permissions: employee number, name (including preferred and partner name), date of birth, start and end date, business and private contact details, department, manager and job title. Salary, absence and appraisal data stay in BCS. Which field ends up where is yours to set in the field mapping.

Optionally. Joinly can write the username (UPN), the email address and the phone number back into BCS, so HR can see which account belongs to which employee. You switch that write-back on or off yourself; by default the integration runs one way, out of BCS.

No. Joinly first imports your existing environment and matches the accounts it finds there to the employees from BCS. Existing accounts are recognised and adopted rather than created twice. Which matching strategy applies — person identifier, employee number or UPN — is yours to choose.

Yes. You run the import as a dry run first: Joinly calculates everything, writes nothing, and hands you an Excel export of exactly what would happen. After that a threshold keeps watching. If BCS delivers more new, activated or deactivated employees in one run than you allowed, Joinly blocks the import instead of executing it.

Contractors, hired staff and interns are registered directly in Joinly or through a second source. From then on they follow the same lifecycle as the employees from BCS, end date included — so temporary access expires by itself instead of lingering.

Yes. A single HR source can feed both Microsoft Entra ID and an on-premises Active Directory, plus your business applications and your ITSM system. Hybrid organisations use that to keep cloud and on-premise following the same truth. Several HR sources side by side is possible too.

The integration is a matter of configuration, not development: Joinly collects employees from one normalised endpoint, so nothing has to be built into the platform to support BCS. The work is in the agreements — which fields lead, which naming convention you use and which permissions belong to which job. Most organisations start with onboarding and expand into role changes and offboarding afterwards.

Joinly is ISO27001-certified. Traffic with BCS runs over a secured connection with its own authentication key, and every change Joinly makes is recorded. At audit time you can show who was given which access when, why it was granted and when it was revoked again.

The integration is part of the subscription — you pay per account per month, not per connector. The pricing page shows what the plans cost and what each one includes.