Real-time
Two-way sync
Changes in Hibob or Microsoft 365 instantly reflect in both systems. No stale data, no manual imports.
Human resources ⇄ Business productivity
Hibob to Microsoft 365 integration — real-time, two-way sync
Keep Hibob and Microsoft 365 in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
- SOC 2 and 6 other compliance frameworks
- POC with real engineers in minutes
Adopted by fast-scaling companies moving mission-critical data in real time
Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Hibob and Microsoft 365
Keep the people, teams, and status that Microsoft 365 and Hibob share aligned in real time, so a hire, role change, or departure recorded in one reaches the other within seconds.
Each tool in Microsoft 365 keeps its own list of who can use it: users, members, or agents, along with the team they sit on and whether they are still active. Hibob is the authoritative record of the same people as employees, with their department, manager, and employment status. When those two are connected only by manual account admin or a periodic export, the work tools drift: new hires wait days for access, team and manager changes never catch up, and people who have left keep standing accounts.
Stacksync syncs Mail Messages, Calendar Events, Contacts, OneDrive Files (driveItems) in Microsoft 365 with Documents, Named lists, People (Employees), Employment in Hibob bi-directionally and in real time. A person added, moved, or offboarded in Hibob creates or updates the matching user in Microsoft 365 within seconds, with field-level mapping and conflict resolution in place of spreadsheets and one-off account changes. Where Microsoft 365 captures details of its own, such as a corrected contact or a login identity, those can flow back to Hibob in whichever direction you configure.
Because the sync is field-level, each system keeps its own extras; only the shared facts, who a person is, which team they belong to, and whether their access should be on, are held in agreement.
Common use cases
- 01 Mirror calendar events into scheduling or CRM tools so meetings appear on customer timelines.
- 02 Sync SharePoint lists with operational databases so business users edit in SharePoint while systems read SQL.
- 03 Two-way sync People (employee) profiles and Work records with a Postgres database so internal apps and directories read profiles in SQL while HR corrections flow back into Bob.
- 04 Auto-provision or deprovision accounts in an IdP, ticketing tool, or app database when Bob Lifecycle events fire employee joined or terminated.
Common sync patterns
Offboarding: no standing access after a departure
When someone is marked as leaving in Hibob, the matching account in Microsoft 365 is deactivated or flagged, so departures do not leave open access behind.
One employee directory
A person's name, title, contact details, or status corrected in either system updates the other, so both sides stop maintaining separate copies of the same person.
Org and team structure kept current
Department, team, and reporting-line changes from Hibob keep the groups, queues, or projects in Microsoft 365 assigned to the right people.
What you can sync between Hibob and Microsoft 365
Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.
| Hibob objects | Microsoft 365 objects | How this pairing syncs | |
|---|---|---|---|
| Employment Historical table of job terms, contract, and working pattern under /people/{id}/employment; full CRUD, entries keyed by effectiveDate. | Groups Microsoft 365 and security groups kept aligned with org structure and access rules. | Employment is specific to Hibob and Groups to Microsoft 365 — each maps to any object or custom field on the other side. | |
| Work Reporting line, department, site, and title under /people/{id}/work; drives the org chart and is synced two-way to directories. | Mail Messages Exchange Online messages read for logging, archiving, or activity capture. | Work is specific to Hibob and Mail Messages to Microsoft 365 — each maps to any object or custom field on the other side. | |
| Salaries Compensation history at /people/{id}/salaries; full CRUD but gated behind the Payroll permission on the service user. | Calendar Events Events synced with scheduling tools and CRMs for meeting visibility. | Salaries is specific to Hibob and Calendar Events to Microsoft 365 — each maps to any object or custom field on the other side. | |
| Time off Absence requests and who's-out data via /timeoff/employees/{id}/requests and /timeoff/whosout; submit new requests and read balances. | Contacts Personal and org contacts kept consistent with CRM contact records. | Time off is specific to Hibob and Contacts to Microsoft 365 — each maps to any object or custom field on the other side. | |
| Lifecycle Hire, termination, and leave status changes at /people/{id}/lifecycle; read-only and the source of lifecycle webhook events. | OneDrive Files (driveItems) File and folder metadata synced for document workflows and audits. | Lifecycle is specific to Hibob and OneDrive Files (driveItems) to Microsoft 365 — each maps to any object or custom field on the other side. | |
| Documents Employee documents accessed under the Docs API; gated behind the Documents permission granted per service user. | SharePoint Sites & Lists List items read and written like lightweight database tables. | Documents is specific to Hibob and SharePoint Sites & Lists to Microsoft 365 — each maps to any object or custom field on the other side. |
How changes propagate between Hibob and Microsoft 365
Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.
Hibob Microsoft 365 Sub-second propagation
DetectionHibob notifies Stacksync of record changes through webhook events. Webhooks fire for employee created/updated/deleted, table-entry created/updated, time off, and lifecycle events.
DeliveryEach detected change is written to Microsoft 365 through its API, with automatic retries and rate-limit backoff.
Microsoft 365 Hibob Sub-second propagation
DetectionMicrosoft 365 notifies Stacksync of record changes through webhook events. Graph change notifications (webhooks) plus delta queries for incremental sync.
DeliveryEach detected change is written to Hibob through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Hibob: Rate limits are enforced per service user; violations return HTTP 429 with X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset response headers. The docs list POST /people/search at 50 requests per minute, and bulk /people/search is preferred over per-record reads.
What ships with Hibob ⇄ Microsoft 365
Connect Hibob and Microsoft 365 for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Hibob–Microsoft 365 connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Hibob or Microsoft 365 data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
At scale
Event queues
Handle millions of events per minute without losing a single Hibob or Microsoft 365 record.
Observability
Monitoring
Track your Hibob ⇄ Microsoft 365 sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Hibob and Microsoft 365.
How the Hibob and Microsoft 365 connectors work
Hibob
- Integration surface
- REST API (the Bob API)
- Authentication
- Service User credentials over HTTP Basic auth (Base64-encoded serviceUserId:serviceUserToken); permissions granted per data category (People, Payroll, Documents) in Bob admin
- Change detection
- Webhooks fire for employee created/updated/deleted, table-entry created/updated, time off, and lifecycle events; the employee.updated payload flags which fields changed and Bob recommends an API call for the full record. There is no CDC stream, and deleting a table entry fires no webhook (Bob has no table-entry deletion event).
- Capabilities
- read · write · webhooks
- Rate limits
- Rate limits are enforced per service user; violations return HTTP 429 with X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset response headers. The docs list POST /people/search at 50 requests per minute, and bulk /people/search is preferred over per-record reads.
Microsoft 365
- Integration surface
- REST API (Microsoft Graph)
- Authentication
- OAuth 2.0 via Microsoft Entra ID, with delegated or application permissions
- Change detection
- Graph change notifications (webhooks) plus delta queries for incremental sync
- Capabilities
- read · write · webhooks
How it works
How to connect Hibob to Microsoft 365 — three steps, no code
Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.
- 01
Connect your apps
Authenticate Hibob and Microsoft 365 with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Hibob
connected
Microsoft 365
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Hibob and Microsoft 365 objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.
objects · Hibob ⇄ Microsoft 365Customers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Hibob Microsoft 365Company company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Hibob and Microsoft 365 integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Hibob and Microsoft 365: authenticate both systems, choose the objects to sync (such as Hibob's Employment and Work), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
On the Microsoft 365 side: Mail Messages, Calendar Events, Contacts, OneDrive Files (driveItems), plus custom fields where Microsoft 365 exposes them. On the Hibob side: Documents, Named lists, People (Employees), Employment. Stacksync auto-detects both schemas and converts types between the two systems.
-
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
-
Common patterns for Hibob and Microsoft 365: Offboarding: no standing access after a departure; One employee directory; Org and team structure kept current. When someone is marked as leaving in Hibob, the matching account in Microsoft 365 is deactivated or flagged, so departures do not leave open access behind.
-
Hibob: REST API (the Bob API). Authentication: Service User credentials over HTTP Basic auth (Base64-encoded serviceUserId:serviceUserToken); permissions granted per data category (People, Payroll, Documents) in Bob admin. Microsoft 365: REST API (Microsoft Graph). Authentication: OAuth 2.0 via Microsoft Entra ID, with delegated or application permissions. Stacksync manages authentication, retries, and rate limits on both sides.
-
Microsoft 365: Change notifications can push events for resources such as messages, events, and driveItems, with subscriptions that must be periodically renewed. Hibob: The GET Read-all-company-employees and Read-by-ID endpoints are legacy; Bob steers reads to POST /people/search, which the docs rate-limit at 50 requests per minute. Stacksync's field mapping accounts for these differences between Hibob and Microsoft 365 without custom code.
SECURITY
Security teams trust Stacksync
As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS
SSO & SCIM
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Alerts
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Secure connection options
Securely connects to your systems with:
Related integrations
Every pair below is a real-time, two-way sync. Search all 455 integrations available for Hibob and Microsoft 365.
Popular · 8 of 455
-
Hibob ⇄ ServiceNow -
Hibob ⇄ Slack -
Hibob ⇄ BetterContact -
Hibob ⇄ Agiloft -
Microsoft 365 ⇄ Jobvite -
Microsoft 365 ⇄ Lever -
Microsoft 365 ⇄ Namely -
Microsoft 365 ⇄ Paylocity
No integrations match .
