Real-time
Two-way sync
Changes in Active Directory or Close instantly reflect in both systems. No stale data, no manual imports.
Security and identity ⇄ CRM
Active Directory to Close integration — real-time, two-way sync
Keep Active Directory and Close 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 Close
Keep the people Close and Active Directory both track in agreement in real time: the internal users who own records in Close, and the customer login accounts in Active Directory.
A CRM and an identity system usually describe different populations. Close 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 Close are the same employees Active Directory provisions and disables, and when Active Directory also runs the login accounts for your product, the customers in Close are the same users Active Directory authenticates. Left unconnected, a departure in Active Directory leaves stale ownership sitting in Close, and a signup in Active Directory never reaches the account it belongs to.
Stacksync syncs Contacts, Opportunities, Activities, Tasks in Close with Users, Groups, Group memberships, Devices 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 Sync Close leads and opportunities into Postgres or a warehouse for pipeline reporting outside Close's built-in reports.
- 02 Two-way sync between Close and a billing or ERP system so closed-won opportunities create customers and invoices automatically.
- 03 Read Users, Groups, and directoryRole assignments into a warehouse for periodic access reviews and SOC 2 audit evidence.
- 04 Keep security-group memberships aligned with application entitlement tables so access reflects the right teams as they change.
Common sync patterns
Where a closed deal should provision access: Close drives Active Directory
A won or activated customer in Close can create or update the corresponding user or account in Active Directory, so provisioning starts from the CRM record instead of a separate ticket.
Where Active Directory governs your workforce: CRM users kept current
New employees in Active Directory become active users in Close 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 Close 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 Active Directory and Close
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 | Close 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 Sales reps referenced as owners on leads, opportunities, and activities. | 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. | Smart Views Saved lead searches that can scope which records a segment-based sync pulls. | Groups is specific to Active Directory and Smart Views to Close — 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. | Leads The top-level record in Close; represents a company and holds its contacts, opportunities, and activity history. | Group memberships is specific to Active Directory and Leads to Close — 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. | Contacts People nested under a lead, with emails and phone numbers used for outreach syncs. | Devices is specific to Active Directory and Contacts to Close — 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. | Opportunities Deal records with value, confidence, and status; commonly synced to reporting and billing systems. | Directory roles is specific to Active Directory and Opportunities to Close — 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. | Activities Calls, emails, SMS, notes, and meetings logged against a lead; the source for engagement analytics. | Service principals & applications is specific to Active Directory and Activities to Close — each maps to any object or custom field on the other side. |
How changes propagate between Active Directory and Close
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 Close 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 Close through its API, with automatic retries and rate-limit backoff.
Close Active Directory Sub-second propagation
DetectionClose notifies Stacksync of record changes through webhook events. Webhook subscriptions for record events, with polling on date_updated fields for backfills.
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.
- Close: Subject to per-endpoint rate limits communicated in response headers.
What ships with Active Directory ⇄ Close
Connect Active Directory and Close for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Active Directory–Close connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Active Directory or Close 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 Close record.
Observability
Monitoring
Track your Active Directory ⇄ Close 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 Close.
How the Active Directory and Close 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.
Close
- Integration surface
- REST API
- Authentication
- API key (sent via HTTP Basic auth)
- Change detection
- Webhook subscriptions for record events, with polling on date_updated fields for backfills
- Capabilities
- read · write · webhooks
- Rate limits
- Subject to per-endpoint rate limits communicated in response headers
How it works
How to connect Active Directory to Close — 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 Close 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
Close
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Active Directory and Close 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 ⇄ CloseCustomers 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 CloseCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Active Directory and Close integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Active Directory and Close: 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.
-
On the Close side: Contacts, Opportunities, Activities, Tasks, plus custom fields where Close exposes them. On the Active Directory side: Users, Groups, Group memberships, Devices. 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 Close: Where a closed deal should provision access: Close drives Active Directory; Where Active Directory governs your workforce: CRM users kept current; Deactivation and record hand-off. A won or activated customer in Close can create or update the corresponding user or account in Active Directory, so provisioning starts from the CRM record instead of a separate ticket.
-
Active Directory: 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. Close: REST API. Authentication: API key (sent via HTTP Basic auth). Stacksync manages authentication, retries, and rate limits on both sides.
-
Close: Webhook subscriptions can be created via the API to receive create, update, and delete events on leads, contacts, opportunities, and activities. Active Directory: DirectoryRole, servicePrincipal, and device objects are effectively read-only for sync; Users, Groups, and memberships are the writable surface. Stacksync's field mapping accounts for these differences between Active Directory and Close without custom code.
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 527 integrations available for Active Directory and Close.
Popular · 8 of 527
-
Active Directory ⇄ Nimble -
Active Directory ⇄ Nutshell -
Active Directory ⇄ Oracle CX Sales -
Active Directory ⇄ Outreach -
Close ⇄ Onelogin -
Close ⇄ Auth0 -
Close ⇄ Jumpcloud - Close ⇄ Azure Active Directory
No integrations match .
