Real-time
Two-way sync
Changes in Azure Active Directory or Intercom instantly reflect in both systems. No stale data, no manual imports.
Security and identity ⇄ CRM
Azure Active Directory to Intercom integration — real-time, two-way sync
Keep Azure Active Directory and Intercom 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 Intercom
Keep the people Intercom and Azure Active Directory both track in agreement in real time: the internal users who own records in Intercom, and the customer login accounts in Azure Active Directory.
A CRM and an identity system usually describe different populations. Intercom 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 Intercom 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 Intercom are the same users Azure Active Directory authenticates. Left unconnected, a departure in Azure Active Directory leaves stale ownership sitting in Intercom, and a signup in Azure Active Directory never reaches the account it belongs to.
Stacksync syncs Companies, Conversations, Tickets, Data Events in Intercom with Group memberships, Applications, Service principals, Directory roles 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 Sync contacts and companies bi-directionally with the CRM so support sees deal context and sales sees conversation history
- 02 Push product usage events from an application database into Intercom to trigger onboarding and retention messages
- 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
Deactivation and record hand-off
When someone is disabled in Azure Active Directory, the matching user in Intercom is deactivated too, and the accounts, contacts, and deals they owned are flagged for reassignment, so nothing goes unattended after they leave.
Where Azure Active Directory runs customer login accounts: identity on the customer record
Signup, account status, multi-factor enrollment, and last-login from Azure Active Directory land on the matching contact or account in Intercom, so go-to-market teams see who has actually activated and who has gone dormant.
Group and entitlement membership as CRM fields
Membership of a directory group or an entitlement in Azure Active Directory maps to fields in Intercom, such as product tier, plan, or internal team, so segmentation reflects real access rather than a manual guess.
What you can sync between Azure Active Directory and Intercom
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 | Intercom objects | How this pairing syncs | |
|---|---|---|---|
| Service principals /servicePrincipals (enterprise apps) plus appRoleAssignments; read for app inventory and access-posture reporting. | Companies Company records group contacts and carry plan and account attributes used in segmentation. | Service principals is specific to Azure Active Directory and Companies to Intercom — 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. | Conversations Support and sales threads sync outward for analytics and CRM context. | Directory roles is specific to Azure Active Directory and Conversations to Intercom — 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. | Tickets Structured ticket records track issues alongside conversational threads. | Devices is specific to Azure Active Directory and Tickets to Intercom — each maps to any object or custom field on the other side. | |
| 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. | Data Events Behavioral events pushed in from product databases trigger messages and flows. | Users is specific to Azure Active Directory and Data Events to Intercom — 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 Data Attributes Typed custom fields on contacts and companies hold synced billing and usage data. | Groups is specific to Azure Active Directory and Custom Data Attributes to Intercom — 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. | Tags Labels applied to contacts, companies, and conversations sync for routing and reporting. | Group memberships is specific to Azure Active Directory and Tags to Intercom — each maps to any object or custom field on the other side. |
How changes propagate between Azure Active Directory and Intercom
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 Intercom 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 Intercom through its API, with automatic retries and rate-limit backoff.
Intercom Azure Active Directory Sub-second propagation
DetectionIntercom notifies Stacksync of record changes through webhook events. Webhook topic subscriptions for contact, company, and conversation 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.
- Intercom: Subject to per-app rate limits on the Intercom API.
What ships with Azure Active Directory ⇄ Intercom
Connect Azure Active Directory and Intercom for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Azure Active Directory–Intercom connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Azure Active Directory or Intercom 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 Intercom record.
Observability
Monitoring
Track your Azure Active Directory ⇄ Intercom 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 Intercom.
How the Azure Active Directory and Intercom 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
Intercom
- Integration surface
- REST API
- Authentication
- OAuth 2.0 for public apps or a workspace access token
- Change detection
- Webhook topic subscriptions for contact, company, and conversation events, plus polling for backfill
- Capabilities
- read · write · webhooks
- Rate limits
- Subject to per-app rate limits on the Intercom API
How it works
How to connect Azure Active Directory to Intercom — 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 Intercom 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
Intercom
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Azure Active Directory and Intercom 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 ⇄ IntercomCustomers 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 IntercomCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Azure Active Directory and Intercom integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Azure Active Directory and Intercom: authenticate both systems, choose the objects to sync (such as Azure Active Directory's Service principals and Directory roles), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Yes — Stacksync ships production-grade connectors for both Azure Active Directory and Intercom. 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 Intercom: Webhook topic subscriptions for contact, company, and conversation 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 Intercom side: Companies, Conversations, Tickets, Data Events, plus custom fields where Intercom exposes them. On the Azure Active Directory side: Group memberships, Applications, Service principals, 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.
-
Common patterns for Azure Active Directory and Intercom: Deactivation and record hand-off; Where Azure Active Directory runs customer login accounts: identity on the customer record; Group and entitlement membership as CRM fields. When someone is disabled in Azure Active Directory, the matching user in Intercom is deactivated too, and the accounts, contacts, and deals they owned are flagged for reassignment, so nothing goes unattended after they leave.
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 511 integrations available for Azure Active Directory and Intercom.
Popular · 6 of 511
-
Azure Active Directory ⇄ Affinity -
Azure Active Directory ⇄ Apollo.io - Intercom ⇄ Active Directory
-
Intercom ⇄ Okta -
Intercom ⇄ Onelogin -
Intercom ⇄ Auth0
No integrations match .
