Real-time
Two-way sync
Changes in Azure Active Directory or Kommo instantly reflect in both systems. No stale data, no manual imports.
Security and identity ⇄ CRM
Azure Active Directory to Kommo integration — real-time, two-way sync
Keep Azure 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 Azure Active Directory and Kommo
Keep the people Kommo and Azure Active Directory both track in agreement in real time: the internal users who own records in Kommo, and the customer login accounts in Azure Active Directory.
A CRM and an identity system usually describe different populations. Kommo tracks customers, contacts, and the deals in motion; Azure 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 Azure Active Directory provisions and disables, and when Azure Active Directory also runs the login accounts for your product, the customers in Kommo are the same users Azure Active Directory authenticates. Left unconnected, a departure in Azure Active Directory leaves stale ownership sitting in Kommo, and a signup in Azure Active Directory never reaches the account it belongs to.
Stacksync syncs Tasks, Notes, Custom Fields, Users in Kommo with Groups, Group memberships, Applications, Service principals in Azure 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 Replicate Kommo leads and contacts into a database or warehouse for reporting beyond built-in dashboards
- 02 Push web form and product signups into Kommo pipelines as they are submitted so messenger-based follow-up starts quickly
- 03 Replicate Groups and their Members into a Postgres warehouse for access reviews and entitlement reporting.
- 04 Mirror Applications and Service principals into a database or CMDB to track app ownership and credential expiry.
Common sync patterns
Where a closed deal should provision access: Kommo drives Azure Active Directory
A won or activated customer in Kommo can create or update the corresponding user or account in Azure Active Directory, so provisioning starts from the CRM record instead of a separate ticket.
Where Azure Active Directory governs your workforce: CRM users kept current
New employees in Azure 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 Azure 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.
What you can sync between Azure 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.
| Azure Active Directory objects | Kommo objects | How this pairing syncs | |
|---|---|---|---|
| Users /users in Microsoft Graph; synced two-way — profile attributes, accountEnabled, and assignedLicenses are read out while provisioning writes (create, update, disable, delete) are pushed back. | 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. | |
| Service principals /servicePrincipals (enterprise apps) plus appRoleAssignments; read for app inventory and access-posture reporting. | Notes Free-text and system notes attach context to synced leads and contacts. | Service principals is specific to Azure Active Directory and Notes to Kommo — each maps to any object or custom field on the other side. | |
| Directory roles /directoryRoles and roleManagement assignments; read for privileged-access reviews, with role-assignment writes where the granted scopes permit. | Custom Fields Per-entity custom fields hold data written from external databases and enrichment. | Directory roles is specific to Azure Active Directory and Custom Fields to Kommo — each maps to any object or custom field on the other side. | |
| Devices /devices registered or joined to the tenant; typically read-only into asset and security databases. | Chats Messenger conversations from WhatsApp, Instagram, and other channels attach to leads and contacts. | Devices is specific to Azure Active Directory and Chats to Kommo — each maps to any object or custom field on the other side. | |
| Groups /groups covering security and Microsoft 365 groups; created, updated, and deleted through Graph, and read into warehouses for entitlement reporting. | Leads The central pipeline record; external signups and form fills sync in as leads. | Groups is specific to Azure Active Directory and Leads to Kommo — each maps to any object or custom field on the other side. | |
| Group memberships Member and owner relationships on /groups/{id}/members; added and removed via the $ref endpoint and tracked for changes with delta query on $select=members. | Contacts Person records sync with other CRMs and databases for a shared contact file. | Group memberships is specific to Azure Active Directory and Contacts to Kommo — each maps to any object or custom field on the other side. |
How changes propagate between Azure 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.
Azure Active Directory Kommo Sub-second propagation
DetectionAzure Active Directory notifies Stacksync of record changes through webhook events. Microsoft Graph delta query (deltaLink tokens returning only changed users and groups, with @removed deletions) paired with change-notification.
DeliveryEach detected change is written to Kommo through its API, with automatic retries and rate-limit backoff.
Kommo Azure 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 Azure Active Directory through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Azure Active Directory: Resource-unit throttling: roughly 8,000 ResourceUnits per 10 seconds per app for reads on tenants over 500 users, writes near 3,000 requests per 2.5 minutes; 429 responses include a Retry-After header.
- Kommo: Subject to per-account request rate limits.
What ships with Azure Active Directory ⇄ Kommo
Connect Azure Active Directory and Kommo for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Azure Active Directory–Kommo connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Azure 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 Azure Active Directory or Kommo record.
Observability
Monitoring
Track your Azure 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 Azure Active Directory and Kommo.
How the Azure Active Directory and Kommo connectors work
Azure Active Directory
- Integration surface
- Microsoft Graph REST API (v1.0)
- Authentication
- OAuth 2.0 via the Microsoft identity platform using an Entra ID app registration; app-only (client credentials) or delegated flows, with directory scopes such as User.ReadWrite.All and Group.ReadWrite.All requiring tenant admin consent
- Change detection
- Microsoft Graph delta query (deltaLink tokens returning only changed users and groups, with @removed deletions) paired with change-notification webhook subscriptions for near-real-time push
- Capabilities
- read · write · webhooks
- Rate limits
- Resource-unit throttling: roughly 8,000 ResourceUnits per 10 seconds per app for reads on tenants over 500 users, writes near 3,000 requests per 2.5 minutes; 429 responses include a Retry-After header
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 Azure 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 Azure 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.
Azure Active Directory
connected
Kommo
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Azure 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 · Azure 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.
Azure Active Directory KommoCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Azure Active Directory and Kommo integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Azure Active Directory and Kommo: authenticate both systems, choose the objects to sync (such as Azure Active Directory's Users and Service principals), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
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 Azure Active Directory and Kommo: Where a closed deal should provision access: Kommo drives Azure Active Directory; Where Azure Active Directory governs your workforce: CRM users kept current; Deactivation and record hand-off. A won or activated customer in Kommo can create or update the corresponding user or account in Azure Active Directory, so provisioning starts from the CRM record instead of a separate ticket.
-
Azure Active Directory: Microsoft Graph REST API (v1.0). Authentication: OAuth 2.0 via the Microsoft identity platform using an Entra ID app registration; app-only (client credentials) or delegated flows, with directory scopes such as User.ReadWrite.All and Group.ReadWrite.All requiring tenant admin consent. Kommo: REST API. Authentication: OAuth 2.0 with refresh tokens. Stacksync manages authentication, retries, and rate limits on both sides.
-
Kommo: Kommo is the former amoCRM, and its data model centers on leads moving through configurable pipelines and statuses, with contacts and companies linked to each lead. Azure Active Directory: Hybrid identities synchronized from on-premises Active Directory via Entra Connect are mastered on-prem; many of their attributes are read-only in Entra ID and must be edited in AD DS. Stacksync's field mapping accounts for these differences between Azure Active Directory and Kommo without custom code.
-
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Azure Active Directory and Kommo records are not retained after a sync operation.
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 Azure Active Directory and Kommo.
Popular · 8 of 516
-
Azure Active Directory ⇄ Gorgias -
Azure Active Directory ⇄ Infor CRM -
Azure Active Directory ⇄ Insightly -
Azure Active Directory ⇄ Intercom -
Kommo ⇄ Onelogin -
Kommo ⇄ Auth0 -
Kommo ⇄ Jumpcloud - Kommo ⇄ Active Directory
No integrations match .
