Real-time
Two-way sync
Changes in Azure Active Directory or Kustomer instantly reflect in both systems. No stale data, no manual imports.
Security and identity ⇄ CRM
Azure Active Directory to Kustomer integration — real-time, two-way sync
Keep Azure 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 Azure Active Directory and Kustomer
Keep the people Kustomer and Azure Active Directory both track in agreement in real time: the internal users who own records in Kustomer, and the customer login accounts in Azure Active Directory.
A CRM and an identity system usually describe different populations. Kustomer 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 Kustomer 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 Kustomer are the same users Azure Active Directory authenticates. Left unconnected, a departure in Azure Active Directory leaves stale ownership sitting in Kustomer, and a signup in Azure Active Directory never reaches the account it belongs to.
Stacksync syncs Custom Objects (Klasses), Users, Teams, Tags in Kustomer with Service principals, Directory roles, Devices, Users 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 Push order and shipment records from commerce systems into Kustomer custom objects so agents answer order-status questions without switching tools
- 02 Mirror conversations and satisfaction data into a warehouse for support analytics and agent performance reporting
- 03 Provision and deprovision Entra ID Users and Group memberships from an HR system of record so account enablement follows employment status.
- 04 Sync manager, department, and jobTitle from an HRIS back onto Entra ID User attributes to keep dynamic groups and Conditional Access accurate.
Common sync patterns
Group and entitlement membership as CRM fields
Membership of a directory group or an entitlement in Azure Active Directory maps to fields in Kustomer, such as product tier, plan, or internal team, so segmentation reflects real access rather than a manual guess.
Where a closed deal should provision access: Kustomer drives Azure Active Directory
A won or activated customer in Kustomer 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 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.
What you can sync between Azure 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.
| Azure Active Directory objects | Kustomer 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 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 /devices registered or joined to the tenant; typically read-only into asset and security databases. | Companies Organization records group customers and map to CRM accounts. | Devices is specific to Azure Active Directory and Companies to Kustomer — 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. | Custom Objects (Klasses) Structured external records such as orders and subscriptions synced in to appear on the customer timeline. | Groups is specific to Azure Active Directory and Custom Objects (Klasses) to Kustomer — 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. | Teams Team assignments support routing parity and reporting. | Group memberships is specific to Azure Active Directory and Teams to Kustomer — each maps to any object or custom field on the other side. | |
| Applications App registrations under /applications; usually read into a database or CMDB for app ownership and credential-expiry tracking. | Tags Labels on conversations and customers sync for categorization and analytics. | Applications is specific to Azure Active Directory and Tags to Kustomer — each maps to any object or custom field on the other side. | |
| Service principals /servicePrincipals (enterprise apps) plus appRoleAssignments; read for app inventory and access-posture reporting. | Notes Internal annotations carry context alongside synced conversations. | Service principals is specific to Azure Active Directory and Notes to Kustomer — each maps to any object or custom field on the other side. |
How changes propagate between Azure 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.
Azure Active Directory Kustomer 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 Kustomer through its API, with automatic retries and rate-limit backoff.
Kustomer Azure 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 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.
- Kustomer: Subject to the platform's API rate limits.
What ships with Azure Active Directory ⇄ Kustomer
Connect Azure Active Directory and Kustomer for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Azure Active Directory–Kustomer connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Azure 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 Azure Active Directory or Kustomer record.
Observability
Monitoring
Track your Azure 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 Azure Active Directory and Kustomer.
How the Azure Active Directory and Kustomer 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
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 Azure 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 Azure 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.
Azure Active Directory
connected
Kustomer
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Azure 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 · Azure 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.
Azure Active Directory KustomerCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Azure Active Directory and Kustomer integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Azure Active Directory and Kustomer: authenticate both systems, choose the objects to sync (such as Azure Active Directory's Users and Devices), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Kustomer: API keys are issued as role-scoped bearer tokens, so integration access can be limited to the specific object types a sync touches. 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 Kustomer 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 Kustomer records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Azure Active Directory and Kustomer connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Azure Active Directory–Kustomer integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Azure 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 Azure Active Directory: 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. 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.
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 Azure Active Directory and Kustomer.
Popular · 6 of 416
-
Azure Active Directory ⇄ Affinity -
Azure Active Directory ⇄ Apollo.io - Kustomer ⇄ Active Directory
-
Kustomer ⇄ Okta -
Kustomer ⇄ Onelogin -
Kustomer ⇄ Auth0
No integrations match .
