Real-time
Two-way sync
Changes in Active Directory or Azure Cosmos DB instantly reflect in both systems. No stale data, no manual imports.
Security and identity ⇄ Database
Active Directory to Azure Cosmos DB integration — real-time, two-way sync
Keep Active Directory and Azure Cosmos DB 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 Azure Cosmos DB
Close the gap between your application data and your directory: Azure Cosmos DB and Active Directory share users, groups, and access in real time, in both directions.
Active Directory is the system of record for who people are and what they can reach: users, the groups they belong to, and the applications assigned to them. Azure Cosmos DB holds the operational data those same people show up in, whether an employee or member table that decides who should have an account at all, a customers list, or the rows an application checks before it authorizes an action. The two describe overlapping users and groups, and when a nightly export or a hand-run script is all that connects them, accounts lag joiners and leavers and the application authorizes against a stale picture of who has access.
Stacksync syncs Containers, Items (JSON documents), Partition keys, Change feed entries in Azure Cosmos DB with Service principals & applications, Organizational units, Organizational contacts, Users in Active Directory field by field, in real time, and in both directions. You decide which system owns which fields, with the directory holding credentials and group membership and the database holding the source list of people who should exist at all, and Stacksync keeps every copy consistent, resolving conflicts by rules you set. A person added to a table becomes an account within seconds, a departure disables one just as fast, and the directory's users and groups are always present in your tables as ordinary rows.
Common use cases
- 01 Sync CRM or ERP records into a Cosmos DB container that backs a customer-facing application.
- 02 Mirror Cosmos DB items into Postgres so teams can query operational data with standard SQL.
- 03 Keep security-group memberships aligned with application entitlement tables so access reflects the right teams as they change.
- 04 Read Devices and service principals into a database for identity, asset, and license inventory across the tenant.
Common sync patterns
Read users and groups as ordinary tables
Users, groups, and their memberships from Active Directory land in Azure Cosmos DB as rows your application and queries can join, so authorization checks and access reporting run against the database instead of the directory API.
Keep group and role membership aligned
A group or role change made in either system updates the other, so the entitlements an application enforces match what the directory grants.
One profile, kept current
A name, department, email, or manager corrected in either system updates the other, so the profile the directory shows and the data the application reads stop drifting apart.
What you can sync between Active Directory and Azure Cosmos DB
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 | Azure Cosmos DB objects | How this pairing syncs | |
|---|---|---|---|
| Devices Registered and joined device objects; typically read into a database for inventory and compliance reporting. | Partition keys Determine data distribution and must be included on writes for the sync to route items correctly. | Devices is specific to Active Directory and Partition keys to Azure Cosmos DB — 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. | Change feed entries Ordered record of inserts and updates per partition, consumed for incremental sync. | Directory roles is specific to Active Directory and Change feed entries to Azure Cosmos DB — 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. | Stored procedures and triggers Server-side logic scoped to a partition; relevant when writes must respect existing validation. | Service principals & applications is specific to Active Directory and Stored procedures and triggers to Azure Cosmos DB — each maps to any object or custom field on the other side. | |
| Organizational units On-prem AD DS containers (LDAP organizationalUnit) used to scope which users and groups a sync includes. | Databases Top-level namespaces that scope containers and throughput provisioning. | Organizational units is specific to Active Directory and Databases to Azure Cosmos DB — each maps to any object or custom field on the other side. | |
| Organizational contacts Directory contact objects (orgContact); synced for shared address-book and CRM person records. | Containers The unit of partitioning and throughput; each container maps to a synced collection. | Organizational contacts is specific to Active Directory and Containers to Azure Cosmos DB — each maps to any object or custom field on the other side. | |
| Users User accounts in Entra ID and on-prem AD DS; synced two-way to create, update attributes, and enable or disable accounts. | Items (JSON documents) Schema-flexible JSON records read and written during sync; nested structures are flattened or mapped as needed. | Users is specific to Active Directory and Items (JSON documents) to Azure Cosmos DB — each maps to any object or custom field on the other side. |
How changes propagate between Active Directory and Azure Cosmos DB
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 Azure Cosmos DB 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 applied to Azure Cosmos DB as a row-level write, with types converted between the two schemas.
Azure Cosmos DB Active Directory Sub-second propagation
DetectionChanges in Azure Cosmos DB are captured at the source via change data capture — no polling loop against its API. Built-in change feed exposing inserts and updates in order within each partition key range.
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.
What ships with Active Directory ⇄ Azure Cosmos DB
Connect Active Directory and Azure Cosmos DB for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Active Directory–Azure Cosmos DB connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Active Directory or Azure Cosmos DB 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 Azure Cosmos DB record.
Observability
Monitoring
Track your Active Directory ⇄ Azure Cosmos DB 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 Azure Cosmos DB.
How the Active Directory and Azure Cosmos DB 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.
Azure Cosmos DB
- Integration surface
- REST API and SDKs over HTTPS (API for NoSQL, formerly the SQL API); also MongoDB, Cassandra, Gremlin, and Table API surfaces
- Authentication
- Account keys, resource tokens, or Microsoft Entra ID role-based access
- Change detection
- Built-in change feed exposing inserts and updates in order within each partition key range
- Capabilities
- read · write · CDC
How it works
How to connect Active Directory to Azure Cosmos DB — 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 Azure Cosmos DB 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
Azure Cosmos DB
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Active Directory and Azure Cosmos DB 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 ⇄ Azure Cosmos DBCustomers 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 Azure Cosmos DBCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Active Directory and Azure Cosmos DB integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Active Directory and Azure Cosmos DB: authenticate both systems, choose the objects to sync (such as Active Directory's Devices and Directory roles), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
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 Active Directory and Azure Cosmos DB records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Active Directory and Azure Cosmos DB connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Active Directory–Azure Cosmos DB integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Active Directory and Azure Cosmos DB. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Active Directory: 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. On Azure Cosmos DB: Built-in change feed exposing inserts and updates in order within each partition key range. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Azure Cosmos DB side: Containers, Items (JSON documents), Partition keys, Change feed entries, plus custom fields where Azure Cosmos DB exposes them. On the Active Directory side: Service principals & applications, Organizational units, Organizational contacts, Users. Stacksync auto-detects both schemas and converts types between the two systems.
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 436 integrations available for Active Directory and Azure Cosmos DB.
Popular · 8 of 436
-
Active Directory ⇄ Apache Cassandra -
Active Directory ⇄ Azure SQL Database -
Active Directory ⇄ Citus -
Active Directory ⇄ Couchbase - Azure Cosmos DB ⇄ Azure Active Directory
-
Azure Cosmos DB ⇄ Okta -
Azure Cosmos DB ⇄ Onelogin -
Azure Cosmos DB ⇄ Auth0
No integrations match .
