Real-time
Two-way sync
Changes in Azure Active Directory or Close instantly reflect in both systems. No stale data, no manual imports.
Security and identity ⇄ CRM
Azure Active Directory to Close integration — real-time, two-way sync
Keep Azure 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 Azure Active Directory and Close
Keep the people Close and Azure Active Directory both track in agreement in real time: the internal users who own records in Close, and the customer login accounts in Azure Active Directory.
A CRM and an identity system usually describe different populations. Close 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 Close 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 Close are the same users Azure Active Directory authenticates. Left unconnected, a departure in Azure Active Directory leaves stale ownership sitting in Close, and a signup in Azure Active Directory never reaches the account it belongs to.
Stacksync syncs Activities, Tasks, Custom Activities, Custom Fields in Close with Users, Groups, Group memberships, Applications 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 Write product usage or firmographic data from an internal database onto Close lead custom fields to prioritize follow-up.
- 02 Sync Close leads and opportunities into Postgres or a warehouse for pipeline reporting outside Close's built-in reports.
- 03 Reconcile Entra ID Users and assignedLicenses with an ITSM or finance database to audit license allocation and reclaim unused seats.
- 04 Provision and deprovision Entra ID Users and Group memberships from an HR system of record so account enablement follows employment status.
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 Close, 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: Close drives Azure Active Directory
A won or activated customer in Close 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 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.
What you can sync between Azure 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.
| Azure Active Directory objects | Close 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 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. | |
| Devices /devices registered or joined to the tenant; typically read-only into asset and security databases. | Custom Activities User-defined activity types with their own custom fields, mapped like standard activities. | Devices is specific to Azure Active Directory and Custom Activities to Close — 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 Fields Org-specific fields on leads, contacts, and opportunities; addressed by stable field ids in syncs. | Groups is specific to Azure Active Directory and Custom Fields to Close — 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. | Smart Views Saved lead searches that can scope which records a segment-based sync pulls. | Group memberships is specific to Azure Active Directory and Smart Views to Close — 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. | Leads The top-level record in Close; represents a company and holds its contacts, opportunities, and activity history. | Applications is specific to Azure Active Directory and Leads to Close — 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. | Contacts People nested under a lead, with emails and phone numbers used for outreach syncs. | Service principals is specific to Azure Active Directory and Contacts to Close — each maps to any object or custom field on the other side. |
How changes propagate between Azure 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.
Azure Active Directory Close 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 Close through its API, with automatic retries and rate-limit backoff.
Close Azure 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 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.
- Close: Subject to per-endpoint rate limits communicated in response headers.
What ships with Azure Active Directory ⇄ Close
Connect Azure Active Directory and Close for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Azure Active Directory–Close connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Azure 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 Azure Active Directory or Close record.
Observability
Monitoring
Track your Azure 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 Azure Active Directory and Close.
How the Azure Active Directory and Close 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
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 Azure 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 Azure 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.
Azure Active Directory
connected
Close
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Azure 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 · Azure 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.
Azure Active Directory CloseCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Azure Active Directory and Close integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Azure Active Directory and Close: 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.
-
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. Close: REST API. Authentication: API key (sent via HTTP Basic auth). Stacksync manages authentication, retries, and rate limits on both sides.
-
Close: Custom fields are addressed by stable ids rather than display names, so field mappings survive renames. Azure Active Directory: Change-notification webhook subscriptions on users and groups deliver near-real-time pushes but have a maximum lifetime and must be renewed before they expire. Stacksync's field mapping accounts for these differences between Azure Active Directory and Close 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 Close 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 Close connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Azure Active Directory–Close integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Azure Active Directory and Close. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
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 Azure Active Directory and Close.
Popular · 8 of 527
-
Azure Active Directory ⇄ Salesforce -
Azure Active Directory ⇄ HubSpot -
Azure Active Directory ⇄ Microsoft Dynamics 365 Sales -
Azure Active Directory ⇄ Attio -
Close ⇄ Jumpcloud - Close ⇄ Active Directory
-
Close ⇄ Okta -
Close ⇄ Onelogin
No integrations match .
