Real-time
Two-way sync
Changes in Active Directory or Kustomer instantly reflect in both systems. No stale data, no manual imports.
Security and identity ⇄ CRM
Active Directory to Kustomer integration — real-time, two-way sync
Keep Active Directory and Kustomer 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 Active Directory and Kustomer
Keep the people Kustomer and Active Directory both track in agreement in real time: the internal users who own records in Kustomer, and the customer login accounts in Active Directory.
A CRM and an identity system usually describe different populations. Kustomer tracks customers, contacts, and the deals in motion; Active Directory governs who is allowed to sign in and what they can reach. Where the two meet is people. The reps who own records in Kustomer are the same employees Active Directory provisions and disables, and when Active Directory also runs the login accounts for your product, the customers in Kustomer are the same users Active Directory authenticates. Left unconnected, a departure in Active Directory leaves stale ownership sitting in Kustomer, and a signup in Active Directory never reaches the account it belongs to.
Stacksync syncs Notes, Customers, Conversations, Messages in Kustomer with Groups, Group memberships, Devices, Directory roles in Active Directory in real time and in both directions, matching on email or an external ID and mapping field by field. You decide which system owns which fields, and new users, role and group changes, deactivations, and account status move within seconds instead of waiting on a quarterly access review or a manual export.
Common use cases
- 01 Mirror conversations and satisfaction data into a warehouse for support analytics and agent performance reporting
- 02 Keep customer attributes updated from billing systems so routing rules and SLAs reflect account value
- 03 Keep security-group memberships aligned with application entitlement tables so access reflects the right teams as they change.
- 04 Read Devices and service principals into a database for identity, asset, and license inventory across the tenant.
Common sync patterns
Where a closed deal should provision access: Kustomer drives Active Directory
A won or activated customer in Kustomer can create or update the corresponding user or account in Active Directory, so provisioning starts from the CRM record instead of a separate ticket.
Where Active Directory governs your workforce: CRM users kept current
New employees in Active Directory become active users in Kustomer with the right role, and group or department changes update their access and team, so the CRM's user list matches the directory without an admin re-keying it.
Deactivation and record hand-off
When someone is disabled in Active Directory, the matching user in Kustomer is deactivated too, and the accounts, contacts, and deals they owned are flagged for reassignment, so nothing goes unattended after they leave.
What you can sync between Active Directory and Kustomer
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.
| Active Directory objects | Kustomer objects | How this pairing syncs | |
|---|---|---|---|
| Users User accounts in Entra ID and on-prem AD DS; synced two-way to create, update attributes, and enable or disable accounts. | Users Agent records map conversation ownership to people in other systems. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Devices Registered and joined device objects; typically read into a database for inventory and compliance reporting. | Notes Internal annotations carry context alongside synced conversations. | Devices is specific to Active Directory and Notes to Kustomer — each maps to any object or custom field on the other side. | |
| Directory roles Admin role assignments (directoryRole); read for access reviews and least-privilege governance. | Customers The central record whose timeline aggregates every interaction; external attributes sync onto it. | Directory roles is specific to Active Directory and Customers to Kustomer — each maps to any object or custom field on the other side. | |
| Service principals & applications App registrations and enterprise apps; read-mostly for entitlement and license inventory. | Conversations Support threads across channels sync outward for analytics and CRM context. | Service principals & applications is specific to Active Directory and Conversations to Kustomer — each maps to any object or custom field on the other side. | |
| Organizational units On-prem AD DS containers (LDAP organizationalUnit) used to scope which users and groups a sync includes. | Messages Individual messages within conversations support full-thread replication. | Organizational units is specific to Active Directory and Messages to Kustomer — each maps to any object or custom field on the other side. | |
| Organizational contacts Directory contact objects (orgContact); synced for shared address-book and CRM person records. | Companies Organization records group customers and map to CRM accounts. | Organizational contacts is specific to Active Directory and Companies to Kustomer — each maps to any object or custom field on the other side. |
How changes propagate between Active Directory and Kustomer
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.
Active Directory Kustomer Sub-second propagation
DetectionActive Directory notifies Stacksync of record changes through webhook events. Microsoft Graph delta query (change tracking) for Users and Groups, plus change-notification subscriptions (webhooks) for near-real-time triggers.
DeliveryEach detected change is written to Kustomer through its API, with automatic retries and rate-limit backoff.
Kustomer Active Directory Sub-second propagation
DetectionKustomer notifies Stacksync of record changes through webhook events. Outbound webhooks on record events, plus polling for backfill.
DeliveryEach detected change is written to Active Directory through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Active Directory: Graph throttles by resource-unit cost per app per tenant in 10-second windows (about 3,500–8,000 units by tenant size); directory delta tokens expire after ~7 days.
- Kustomer: Subject to the platform's API rate limits.
What ships with Active Directory ⇄ Kustomer
Connect Active Directory and Kustomer for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Active Directory–Kustomer connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Active Directory or Kustomer 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 Active Directory or Kustomer record.
Observability
Monitoring
Track your Active Directory ⇄ Kustomer sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Active Directory and Kustomer.
How the Active Directory and Kustomer connectors work
Active Directory
- Integration surface
- Microsoft Graph REST API (Entra ID / cloud) and LDAP/LDAPS (on-premises AD DS)
- Authentication
- OAuth 2.0 via the Microsoft identity platform — an app registration with application or delegated permissions (e.g. User.ReadWrite.All, Group.ReadWrite.All) and admin consent; on-prem AD DS uses a bound service account over LDAPS.
- Change detection
- Microsoft Graph delta query (change tracking) for Users and Groups, plus change-notification subscriptions (webhooks) for near-real-time triggers; on-prem AD DS uses the DirSync control and uSNChanged polling.
- Capabilities
- read · write · webhooks
- Rate limits
- Graph throttles by resource-unit cost per app per tenant in 10-second windows (about 3,500–8,000 units by tenant size); directory delta tokens expire after ~7 days.
Kustomer
- Integration surface
- REST API
- Authentication
- API key used as a bearer token, scoped by role
- Change detection
- Outbound webhooks on record events, plus polling for backfill
- Capabilities
- read · write · webhooks
- Rate limits
- Subject to the platform's API rate limits
How it works
How to connect Active Directory to Kustomer — 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 Active Directory and Kustomer with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Active Directory
connected
Kustomer
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Active Directory and Kustomer 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 · Active Directory ⇄ KustomerCustomers 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.
Active Directory KustomerCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Active Directory and Kustomer integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Active Directory and Kustomer: authenticate both systems, choose the objects to sync (such as Active Directory's Users and Devices), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Active Directory and Kustomer connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Active Directory–Kustomer integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Active Directory and Kustomer. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Active Directory: Microsoft Graph delta query (change tracking) for Users and Groups, plus change-notification subscriptions (webhooks) for near-real-time triggers; on-prem AD DS uses the DirSync control and uSNChanged polling. On Kustomer: Outbound webhooks on record events, plus polling for backfill. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Kustomer side: Notes, Customers, Conversations, Messages, plus custom fields where Kustomer exposes them. On the Active Directory side: Groups, Group memberships, Devices, Directory roles. 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.
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 416 integrations available for Active Directory and Kustomer.
Popular · 8 of 416
-
Active Directory ⇄ Pipedrive -
Active Directory ⇄ Zoho CRM -
Active Directory ⇄ Shopify -
Active Directory ⇄ Affinity -
Kustomer ⇄ Auth0 -
Kustomer ⇄ Jumpcloud - Kustomer ⇄ Azure Active Directory
-
Kustomer ⇄ Okta
No integrations match .
