Real-time
Two-way sync
Changes in Azure Active Directory or Twenty CRM instantly reflect in both systems. No stale data, no manual imports.
Security and identity ⇄ CRM
Azure Active Directory to Twenty CRM integration — real-time, two-way sync
Keep Azure Active Directory and Twenty CRM 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 Twenty CRM
Keep the people Twenty CRM and Azure Active Directory both track in agreement in real time: the internal users who own records in Twenty CRM, and the customer login accounts in Azure Active Directory.
A CRM and an identity system usually describe different populations. Twenty CRM 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 Twenty CRM 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 Twenty CRM are the same users Azure Active Directory authenticates. Left unconnected, a departure in Azure Active Directory leaves stale ownership sitting in Twenty CRM, and a signup in Azure Active Directory never reaches the account it belongs to.
Stacksync syncs Attachments, Workspace Members, People, Companies in Twenty CRM 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 Mirror support tickets or tasks between Twenty and an operations tool.
- 02 Run a continuous sync from a legacy CRM into Twenty during a migration so both systems stay usable through cutover.
- 03 Sync manager, department, and jobTitle from an HRIS back onto Entra ID User attributes to keep dynamic groups and Conditional Access accurate.
- 04 Replicate Groups and their Members into a Postgres warehouse for access reviews and entitlement reporting.
Common sync patterns
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 Twenty CRM, 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 Twenty CRM, 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: Twenty CRM drives Azure Active Directory
A won or activated customer in Twenty CRM 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.
What you can sync between Azure Active Directory and Twenty CRM
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 | Twenty CRM objects | How this pairing syncs | |
|---|---|---|---|
| Applications App registrations under /applications; usually read into a database or CMDB for app ownership and credential-expiry tracking. | Notes Free-form notes attached to records, useful for mirroring activity from other tools. | Applications is specific to Azure Active Directory and Notes to Twenty CRM — 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. | Custom Objects User-defined objects created in Twenty's data model settings, addressable through the same APIs as standard objects. | Service principals is specific to Azure Active Directory and Custom Objects to Twenty CRM — 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. | Attachments Files linked to records. | Directory roles is specific to Azure Active Directory and Attachments to Twenty CRM — 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. | Workspace Members User accounts used for record ownership and assignment mapping. | Devices is specific to Azure Active Directory and Workspace Members to Twenty CRM — 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. | People Individual contact records with emails, phones, and company links; a core target for contact syncs. | Users is specific to Azure Active Directory and People to Twenty CRM — 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. | Companies Account-level records that group people and opportunities. | Groups is specific to Azure Active Directory and Companies to Twenty CRM — each maps to any object or custom field on the other side. |
How changes propagate between Azure Active Directory and Twenty CRM
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 Twenty CRM 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 Twenty CRM through its API, with automatic retries and rate-limit backoff.
Twenty CRM Azure Active Directory Sub-second propagation
DetectionTwenty CRM notifies Stacksync of record changes through webhook events. Webhooks on record create, update, and delete events, or polling on record update timestamps.
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.
- Twenty CRM: Subject to the platform's API rate limits; self-hosted deployments control their own limits.
What ships with Azure Active Directory ⇄ Twenty CRM
Connect Azure Active Directory and Twenty CRM for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Azure Active Directory–Twenty CRM connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Azure Active Directory or Twenty CRM 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 Twenty CRM record.
Observability
Monitoring
Track your Azure Active Directory ⇄ Twenty CRM 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 Twenty CRM.
How the Azure Active Directory and Twenty CRM 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
Twenty CRM
- Integration surface
- GraphQL and REST APIs
- Authentication
- API key
- Change detection
- Webhooks on record create, update, and delete events, or polling on record update timestamps
- Capabilities
- read · write · webhooks
- Rate limits
- Subject to the platform's API rate limits; self-hosted deployments control their own limits.
How it works
How to connect Azure Active Directory to Twenty CRM — 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 Twenty CRM 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
Twenty CRM
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Azure Active Directory and Twenty CRM 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 ⇄ Twenty CRMCustomers 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 Twenty CRMCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Azure Active Directory and Twenty CRM integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Azure Active Directory and Twenty CRM: authenticate both systems, choose the objects to sync (such as Azure Active Directory's Applications and Service principals), 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 Azure Active Directory and Twenty CRM connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Azure Active Directory–Twenty CRM integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Azure Active Directory and Twenty CRM. 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 Twenty CRM: Webhooks on record create, update, and delete events, or polling on record update timestamps. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Twenty CRM side: Attachments, Workspace Members, People, Companies, plus custom fields where Twenty CRM exposes them. On the Azure Active Directory side: Groups, Group memberships, Applications, Service principals. 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 433 integrations available for Azure Active Directory and Twenty CRM.
Popular · 7 of 433
-
Azure Active Directory ⇄ Close -
Azure Active Directory ⇄ Copper CRM -
Azure Active Directory ⇄ Creatio CRM -
Twenty CRM ⇄ Okta -
Twenty CRM ⇄ Onelogin -
Twenty CRM ⇄ Auth0 -
Twenty CRM ⇄ Jumpcloud
No integrations match .
