Real-time
Two-way sync
Changes in Active Directory or Kommo instantly reflect in both systems. No stale data, no manual imports.
Security and identity ⇄ CRM
Active Directory to Kommo integration — real-time, two-way sync
Keep Active Directory and Kommo 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 Kommo
Keep the people Kommo and Active Directory both track in agreement in real time: the internal users who own records in Kommo, and the customer login accounts in Active Directory.
A CRM and an identity system usually describe different populations. Kommo 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 Kommo are the same employees Active Directory provisions and disables, and when Active Directory also runs the login accounts for your product, the customers in Kommo are the same users Active Directory authenticates. Left unconnected, a departure in Active Directory leaves stale ownership sitting in Kommo, and a signup in Active Directory never reaches the account it belongs to.
Stacksync syncs Companies, Pipelines & Statuses, Tasks, Notes in Kommo with Organizational units, Organizational contacts, Users, Groups 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 Push web form and product signups into Kommo pipelines as they are submitted so messenger-based follow-up starts quickly
- 02 Keep customer records consistent between Kommo and invoicing or ERP systems
- 03 Two-way sync Users and Groups between Microsoft Entra ID and an HRIS or Postgres so joiners, movers, and leavers provision and deprovision automatically.
- 04 Read Users, Groups, and directoryRole assignments into a warehouse for periodic access reviews and SOC 2 audit evidence.
Common sync patterns
Where Active Directory governs your workforce: CRM users kept current
New employees in Active Directory become active users in Kommo 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 Kommo is deactivated too, and the accounts, contacts, and deals they owned are flagged for reassignment, so nothing goes unattended after they leave.
Where Active Directory runs customer login accounts: identity on the customer record
Signup, account status, multi-factor enrollment, and last-login from Active Directory land on the matching contact or account in Kommo, so go-to-market teams see who has actually activated and who has gone dormant.
What you can sync between Active Directory and Kommo
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 | Kommo 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 Account users map lead ownership to people in other systems. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Groups Security and Microsoft 365 groups; synced two-way including name, type, and owner, with membership tracked separately. | Custom Fields Per-entity custom fields hold data written from external databases and enrichment. | Groups is specific to Active Directory and Custom Fields to Kommo — each maps to any object or custom field on the other side. | |
| Group memberships Member and owner links between users and groups; membership add/remove changes are surfaced by delta query. | Chats Messenger conversations from WhatsApp, Instagram, and other channels attach to leads and contacts. | Group memberships is specific to Active Directory and Chats to Kommo — each maps to any object or custom field on the other side. | |
| Devices Registered and joined device objects; typically read into a database for inventory and compliance reporting. | Leads The central pipeline record; external signups and form fills sync in as leads. | Devices is specific to Active Directory and Leads to Kommo — 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. | Contacts Person records sync with other CRMs and databases for a shared contact file. | Directory roles is specific to Active Directory and Contacts to Kommo — 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. | Companies Organization records map to accounts in ERPs and invoicing tools. | Service principals & applications is specific to Active Directory and Companies to Kommo — each maps to any object or custom field on the other side. |
How changes propagate between Active Directory and Kommo
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 Kommo 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 Kommo through its API, with automatic retries and rate-limit backoff.
Kommo Active Directory Sub-second propagation
DetectionKommo notifies Stacksync of record changes through webhook events. Webhooks on record add and update 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.
- Kommo: Subject to per-account request rate limits.
What ships with Active Directory ⇄ Kommo
Connect Active Directory and Kommo for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Active Directory–Kommo connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Active Directory or Kommo 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 Kommo record.
Observability
Monitoring
Track your Active Directory ⇄ Kommo 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 Kommo.
How the Active Directory and Kommo 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.
Kommo
- Integration surface
- REST API
- Authentication
- OAuth 2.0 with refresh tokens
- Change detection
- Webhooks on record add and update events, plus polling for backfill
- Capabilities
- read · write · webhooks
- Rate limits
- Subject to per-account request rate limits
How it works
How to connect Active Directory to Kommo — 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 Kommo 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
Kommo
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Active Directory and Kommo 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 ⇄ KommoCustomers 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 KommoCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Active Directory and Kommo integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Active Directory and Kommo: authenticate both systems, choose the objects to sync (such as Active Directory's Users and Groups), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Yes — Stacksync ships production-grade connectors for both Active Directory and Kommo. 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 Kommo: Webhooks on record add and update 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 Kommo side: Companies, Pipelines & Statuses, Tasks, Notes, plus custom fields where Kommo exposes them. On the Active Directory side: Organizational units, Organizational contacts, Users, 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 Active Directory and Kommo: Where Active Directory governs your workforce: CRM users kept current; Deactivation and record hand-off; Where Active Directory runs customer login accounts: identity on the customer record. New employees in Active Directory become active users in Kommo 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.
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 516 integrations available for Active Directory and Kommo.
Popular · 7 of 516
-
Active Directory ⇄ Seismic -
Active Directory ⇄ Xactly -
Active Directory ⇄ Gong - Kommo ⇄ Azure Active Directory
-
Kommo ⇄ Okta -
Kommo ⇄ Onelogin -
Kommo ⇄ Auth0
No integrations match .
