Real-time
Two-way sync
Changes in Azure Active Directory or Azure Cosmos DB instantly reflect in both systems. No stale data, no manual imports.
Security and identity ⇄ Database
Azure Active Directory to Azure Cosmos DB integration — real-time, two-way sync
Keep Azure 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 Azure Active Directory and Azure Cosmos DB
Close the gap between your application data and your directory: Azure Cosmos DB and Azure Active Directory share users, groups, and access in real time, in both directions.
Azure 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 Groups, Group memberships, Applications, Service principals in Azure 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 Consolidate documents from multiple containers into a single reporting store.
- 02 Stream operational documents from Cosmos DB into a SQL warehouse via the change feed for analytics without hitting request-unit budgets with full scans.
- 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
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.
Provision accounts from the source of truth
When a person is added to the employee, member, or customer table in Azure Cosmos DB, Stacksync creates the matching user in Azure Active Directory with the right attributes, so access starts from live data instead of a manual ticket.
Deprovision the moment the record changes
When someone is marked inactive or removed in Azure Cosmos DB, the matching account in Azure Active Directory is disabled within seconds, closing the window between a departure and a login that still works.
What you can sync between Azure 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.
| Azure Active Directory objects | Azure Cosmos DB objects | How this pairing syncs | |
|---|---|---|---|
| Applications App registrations under /applications; usually read into a database or CMDB for app ownership and credential-expiry tracking. | Databases Top-level namespaces that scope containers and throughput provisioning. | Applications is specific to Azure Active Directory and Databases to Azure Cosmos DB — 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. | Containers The unit of partitioning and throughput; each container maps to a synced collection. | Service principals is specific to Azure Active Directory and Containers to Azure Cosmos DB — 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. | Items (JSON documents) Schema-flexible JSON records read and written during sync; nested structures are flattened or mapped as needed. | Directory roles is specific to Azure Active Directory and Items (JSON documents) to Azure Cosmos DB — 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. | Partition keys Determine data distribution and must be included on writes for the sync to route items correctly. | Devices is specific to Azure Active Directory and Partition keys to Azure Cosmos DB — 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. | Change feed entries Ordered record of inserts and updates per partition, consumed for incremental sync. | Users is specific to Azure Active Directory and Change feed entries to Azure Cosmos DB — 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. | Stored procedures and triggers Server-side logic scoped to a partition; relevant when writes must respect existing validation. | Groups is specific to Azure Active Directory and Stored procedures and triggers to Azure Cosmos DB — each maps to any object or custom field on the other side. |
How changes propagate between Azure 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.
Azure Active Directory Azure Cosmos DB 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 applied to Azure Cosmos DB as a row-level write, with types converted between the two schemas.
Azure Cosmos DB Azure 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 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.
What ships with Azure Active Directory ⇄ Azure Cosmos DB
Connect Azure Active Directory and Azure Cosmos DB for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Azure Active Directory–Azure Cosmos DB connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Azure 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 Azure Active Directory or Azure Cosmos DB record.
Observability
Monitoring
Track your Azure 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 Azure Active Directory and Azure Cosmos DB.
How the Azure Active Directory and Azure Cosmos DB 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
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 Azure 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 Azure 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.
Azure Active Directory
connected
Azure Cosmos DB
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Azure 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 · Azure 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.
Azure Active Directory Azure Cosmos DBCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Azure Active Directory and Azure Cosmos DB integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Azure Active Directory and Azure Cosmos DB: 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 Azure Cosmos DB connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Azure Active Directory–Azure Cosmos DB integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Azure 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 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 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 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 436 integrations available for Azure Active Directory and Azure Cosmos DB.
Popular · 8 of 436
-
Azure Active Directory ⇄ Amazon RDS -
Azure Active Directory ⇄ Supabase -
Azure Active Directory ⇄ MySQL -
Azure Active Directory ⇄ MariaDB -
Azure Cosmos DB ⇄ Jumpcloud - Azure Cosmos DB ⇄ Active Directory
-
Azure Cosmos DB ⇄ Okta -
Azure Cosmos DB ⇄ Onelogin
No integrations match .
