Real-time
Two-way sync
Changes in Jumpcloud or Microsoft 365 instantly reflect in both systems. No stale data, no manual imports.
Security and identity ⇄ Business productivity
Jumpcloud to Microsoft 365 integration — real-time, two-way sync
Keep Jumpcloud 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 Jumpcloud and Microsoft 365
Keep the users, groups, and profile details that Microsoft 365 and Jumpcloud share consistent in real time, so who can work in Microsoft 365 always matches who your directory in Jumpcloud says belongs there.
Jumpcloud is where a company records who its people are: their accounts, the groups and roles they hold, and the attributes attached to each one. Microsoft 365 is where a slice of those same people do their work, as agents, members, or seats, and every one of them needs a matching account with the right access. When a directory and a productivity tool are maintained by hand, someone added, moved, or offboarded in one becomes a stale entry in the other within the hour.
Stacksync syncs Calendar Events, Contacts, OneDrive Files (driveItems), SharePoint Sites & Lists in Microsoft 365 with System Users (Users), User Groups, Systems (devices), System Groups in Jumpcloud bi-directionally and in real time. A user created, renamed, moved between groups, or deactivated in either system updates the matching record in the other within seconds, with field-level mapping and conflict resolution in place of CSV uploads and nightly IT batch jobs.
That matters most at the edges of employment. When both systems agree on who has an account, which groups they belong to, and whether they are still active, granting access on day one and revoking it on the last day stops being a manual checklist that trails the directory.
Common use cases
- 01 Sync employee records from an HR system into Entra ID users and group memberships.
- 02 Mirror calendar events into scheduling or CRM tools so meetings appear on customer timelines.
- 03 Read Directory Insights events into Postgres or a warehouse for access reviews, login analytics, and SOC 2 audit evidence beyond JumpCloud's retention window.
- 04 Read Systems and System Group memberships into a database for device inventory, patch reporting, and conditional-access analysis.
Common sync patterns
One record per person
People matched across both systems on email or an external ID stay linked, so every account and action in Microsoft 365 ties back to the right identity in Jumpcloud.
Provision access when someone joins
A user added to Jumpcloud, or moved into a group inside it, gets the matching account or membership created in Microsoft 365, so a new hire can start working without a separate setup ticket.
Close access when someone leaves
When a user is disabled or removed in Jumpcloud, their account in Microsoft 365 is deactivated in step, so offboarding shuts down access everywhere instead of leaving a live login behind.
What you can sync between Jumpcloud 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.
| Jumpcloud objects | Microsoft 365 objects | How this pairing syncs | |
|---|---|---|---|
| System Users (Users) Directory user accounts (email, username, attributes, status, MFA, group and app bindings); full CRUD via the v1 /systemusers API - create, update, activate or suspend, and delete to match an HR or identity source. | SharePoint Sites & Lists List items read and written like lightweight database tables. | System Users (Users) is specific to Jumpcloud and SharePoint Sites & Lists to Microsoft 365 — each maps to any object or custom field on the other side. | |
| User Groups User groups that grant app, LDAP, and RADIUS access; created, updated, and deleted via v2 /usergroups, with membership managed through the graph association endpoints. | Teams Team and membership data provisioned from upstream systems. | User Groups is specific to Jumpcloud and Teams to Microsoft 365 — each maps to any object or custom field on the other side. | |
| Systems (devices) Enrolled macOS, Windows, and Linux machines running the JumpCloud agent; agent-enrolled, so the API reads, updates, and deletes systems for inventory and management rather than creating them. | Planner & To Do Tasks Task items synced with project and work-management tools. | Systems (devices) is specific to Jumpcloud and Planner & To Do Tasks to Microsoft 365 — each maps to any object or custom field on the other side. | |
| System Groups Device groups used to scope policies, commands, and access; full CRUD via v2 /systemgroups, with systems bound and unbound through association endpoints. | Users Entra ID user accounts synced with HR and identity systems. | System Groups is specific to Jumpcloud and Users to Microsoft 365 — each maps to any object or custom field on the other side. | |
| Applications (SSO) SAML and OIDC SSO app configs; read via v2 /applications and their user/group assignments created and removed to control who can reach each connected app. | Groups Microsoft 365 and security groups kept aligned with org structure and access rules. | Applications (SSO) is specific to Jumpcloud and Groups to Microsoft 365 — each maps to any object or custom field on the other side. | |
| Policies Device configuration and MDM policies; read, created from templates, and updated via v2 /policies, then bound to systems and system groups to enforce settings across the fleet. | Mail Messages Exchange Online messages read for logging, archiving, or activity capture. | Policies is specific to Jumpcloud and Mail Messages to Microsoft 365 — each maps to any object or custom field on the other side. |
How changes propagate between Jumpcloud 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.
Jumpcloud Microsoft 365 Sub-second propagation
DetectionJumpcloud notifies Stacksync of record changes through webhook events. No database-style change log.
DeliveryEach detected change is written to Microsoft 365 through its API, with automatic retries and rate-limit backoff.
Microsoft 365 Jumpcloud 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 Jumpcloud through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Jumpcloud: JumpCloud rate-limits API requests and returns HTTP 429 (Rate limit exceeded) when a client sends requests too quickly; its guidance is to back off and retry at a lower rate. Specific per-minute ceilings are not published, and the Directory Insights API is metered separately. Webhook deliveries are retried three times with exponential backoff on 5xx, 408, or 429 responses.
What ships with Jumpcloud ⇄ Microsoft 365
Connect Jumpcloud and Microsoft 365 for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Jumpcloud–Microsoft 365 connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Jumpcloud 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 Jumpcloud or Microsoft 365 record.
Observability
Monitoring
Track your Jumpcloud ⇄ 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 Jumpcloud and Microsoft 365.
How the Jumpcloud and Microsoft 365 connectors work
Jumpcloud
- Integration surface
- JumpCloud REST API - v1 (console.jumpcloud.com/api) for Systems, System Users, and Commands; v2 (/api/v2) for User Groups, System Groups, Applications, Policies, and resource associations; plus the Directory Insights API (api.jumpcloud.com/insights/directory/v1/events) and Webhook Channels for outbound events.
- Authentication
- Admin API key sent in the x-api-key header (keys are prefixed jca_, generated in the console with a 30-365 day expiry, and disabled for admins by default until enabled); an x-org-id header scopes calls to a single organization for MSP multi-tenant admins. System Context authorization (HMAC-signed) also exists for agent-run calls.
- Change detection
- No database-style change log. The Directory Insights API is queried by POST for login and admin events across SSO, LDAP, RADIUS, systems, MDM, and directory services - including the association_change event that records user-to-group and policy-to-device membership changes; Webhook Channels tied to Insights Rules POST JSON to a registered endpoint for near-real-time triggers.
- Capabilities
- read · write · webhooks
- Rate limits
- JumpCloud rate-limits API requests and returns HTTP 429 (Rate limit exceeded) when a client sends requests too quickly; its guidance is to back off and retry at a lower rate. Specific per-minute ceilings are not published, and the Directory Insights API is metered separately. Webhook deliveries are retried three times with exponential backoff on 5xx, 408, or 429 responses.
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 Jumpcloud 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 Jumpcloud 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.
Jumpcloud
connected
Microsoft 365
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Jumpcloud 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 · Jumpcloud ⇄ 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.
Jumpcloud Microsoft 365Company company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Jumpcloud and Microsoft 365 integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Jumpcloud and Microsoft 365: authenticate both systems, choose the objects to sync (such as Jumpcloud's System Users (Users) and User Groups), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
On the Microsoft 365 side: Calendar Events, Contacts, OneDrive Files (driveItems), SharePoint Sites & Lists, plus custom fields where Microsoft 365 exposes them. On the Jumpcloud side: System Users (Users), User Groups, Systems (devices), System Groups. 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 Jumpcloud and Microsoft 365: One record per person; Provision access when someone joins; Close access when someone leaves. People matched across both systems on email or an external ID stay linked, so every account and action in Microsoft 365 ties back to the right identity in Jumpcloud.
-
Jumpcloud: JumpCloud REST API - v1 (console.jumpcloud.com/api) for Systems, System Users, and Commands; v2 (/api/v2) for User Groups, System Groups, Applications, Policies, and resource associations; plus the Directory Insights API (api.jumpcloud.com/insights/directory/v1/events) and Webhook Channels for outbound events. Authentication: Admin API key sent in the x-api-key header (keys are prefixed jca_, generated in the console with a 30-365 day expiry, and disabled for admins by default until enabled); an x-org-id header scopes calls to a single organization for MSP multi-tenant admins. System Context authorization (HMAC-signed) also exists for agent-run calls. 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: Nearly all Microsoft 365 workloads (Exchange, SharePoint, OneDrive, Teams, Entra ID) are exposed through the single Microsoft Graph endpoint rather than per-product APIs. Jumpcloud: JumpCloud rate-limits requests and returns HTTP 429 when they arrive too fast, with no published numeric ceiling; webhook deliveries are retried three times with exponential backoff on 5xx, 408, or 429 responses. Stacksync's field mapping accounts for these differences between Jumpcloud 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 453 integrations available for Jumpcloud and Microsoft 365.
Popular · 8 of 453
-
Jumpcloud ⇄ Adobe Sign -
Jumpcloud ⇄ Asana -
Jumpcloud ⇄ Docusign -
Jumpcloud ⇄ Gatekeeper -
Microsoft 365 ⇄ Okta -
Microsoft 365 ⇄ Onelogin -
Microsoft 365 ⇄ Auth0 -
Microsoft 365 ⇄ Active Directory
No integrations match .
