Directory sync
Connect Microsoft Entra ID or LDAP and let Besecure read your people from the directory you already maintain.
- Microsoft Entra ID and LDAP
- Automatic or on-demand synchronisation
- Connection tested before you commit
- Every run reports what it did
What it does
Keep the directory you already run
Besecure connects to Microsoft Entra ID or LDAP and reads your people from it, rather than asking you to rebuild the organisation by hand in a second system.
Test before you commit
The connection can be tested before anything is saved, so a wrong service account, base DN or port surfaces immediately instead of at the first sync.
Automatic or on demand
Run synchronisation on a schedule, or trigger it yourself once you have made a batch of changes upstream.
You can see what happened
Each run records when it ran, whether it succeeded, how many records it processed and what failed — so a partial sync is visible rather than silent.
What the rollout looks like
Choose the directory type
Microsoft Entra ID or LDAP.
Enter the connection
Host, port and transport security for LDAP, or tenant and client details for Entra ID.
Test it
Confirm Besecure can reach the directory and authenticate, before saving anything.
Choose how it runs
Set automatic synchronisation, or keep it manual and run it yourself.
Questions about directory sync
Which directories can Besecure sync from?
Microsoft Entra ID and LDAP.
Is the connection encrypted?
LDAP connections can use LDAPS or StartTLS, chosen when the directory is configured.
What happens if a synchronisation fails?
The run is recorded with its status, the number of records processed and a message describing what went wrong, so a failed or partial sync is visible rather than silent.
More of what Besecure does
Adaptive access policies
Apply extra control when the sign-in context looks different.
API and app security
Protect modern, legacy and custom applications with the same access layer.
Governance and reviews
Give auditors and managers one evidence trail for access.
Multi-factor authentication
A second factor on every account, enrolment you can require rather than suggest, and password rules set to…
Privileged access controls
Keep administrative and support access narrow, visible and time-bound.
Single sign-on
One sign-in for every application your team uses, assigned by role rather than person, with every sign-in recorded.
User lifecycle management
Automate access from onboarding through role changes and offboarding.
One sign-in for every app your team uses.
Set up your organisation, connect your directory and give your people a single secure launchpad.