Case study · An enterprise task-management platform via Transviti
Two-Way Microsoft Entra ID Sync
Keeping a task platform and Entra ID in step
Ended double data entry by syncing employee records between an enterprise task platform and Microsoft Entra ID, in both directions.
At a glance
- Client
- An enterprise task-management platform via Transviti
- Role
- Frontend Developer · Research and integration
- Timeline
- Jan 2024 – Feb 2024
- Industry
- Enterprise SaaS · Middle East
Results
- Organisations on Entra ID no longer had to enter employees twice, and records stayed consistent across both systems.
Stack
- Microsoft Entra ID
- Microsoft Graph API
- MSAL
- OAuth 2.0
Links
Client confidential.
IllustrativeThe problem
Many organisations manage their employees in Microsoft Entra ID. The task platform had no connection to it, so admins had to add every employee twice.
Keeping both systems up to date by hand was slow and caused mismatched records.
What I built
- 01
Integration research
I researched how to connect the platform to Entra ID and recommended the Microsoft Graph API.
- 02
Secure authentication
Used the Microsoft Authentication Library (MSAL) to authenticate the platform with Entra ID.
- 03
Two-way sync
Employee changes in Entra ID flow into the platform, and changes made in the platform are written back to Entra ID.
Key decisions
Microsoft Graph as the integration point
It’s Microsoft’s supported API for Entra ID data, so the integration rests on a stable, documented interface.
MSAL instead of custom auth
Microsoft’s own library handles tokens and sign-in securely, with less custom code to maintain.
Two-way, not one-way
Both sides edited employee data, so a one-way import would still have left records drifting apart.
Team & credits
- Designer
- Backend Developer
- Backend Developer
Built with Transviti’s design and backend team.
Building, hiring, or researching?
Tell me what you're working on. A 15-minute call is the fastest way to see whether I'm the right fit.