Real-time
Two-way sync
Changes in Active Directory or ServiceNow instantly reflect in both systems. No stale data, no manual imports.
Security and identity ⇄ Business productivity
Active Directory to ServiceNow integration — real-time, two-way sync
Keep Active Directory and ServiceNow 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 ServiceNow
Keep the users, groups, and profile details that ServiceNow and Active Directory share consistent in real time, so who can work in ServiceNow always matches who your directory in Active Directory says belongs there.
Active Directory is where a company records who its people are: their accounts, the groups and roles they hold, and the attributes attached to each one. ServiceNow is where a slice of those same people do their work, as agents, members, or seats, and every one of them needs a matching account with the right access. When a directory and a productivity tool are maintained by hand, someone added, moved, or offboarded in one becomes a stale entry in the other within the hour.
Stacksync syncs Incidents, Change Requests, Problems, Service Catalog Requests in ServiceNow with Group memberships, Devices, Directory roles, Service principals & applications in Active Directory bi-directionally and in real time. A user created, renamed, moved between groups, or deactivated in either system updates the matching record in the other within seconds, with field-level mapping and conflict resolution in place of CSV uploads and nightly IT batch jobs.
That matters most at the edges of employment. When both systems agree on who has an account, which groups they belong to, and whether they are still active, granting access on day one and revoking it on the last day stops being a manual checklist that trails the directory.
Common use cases
- 01 Create ServiceNow tickets automatically from CRM cases and sync status back as agents work them
- 02 Bi-directional sync of incidents with engineering issue trackers so IT and engineering work the same ticket without re-keying
- 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
One record per person
People matched across both systems on email or an external ID stay linked, so every account and action in ServiceNow ties back to the right identity in Active Directory.
Provision access when someone joins
A user added to Active Directory, or moved into a group inside it, gets the matching account or membership created in ServiceNow, so a new hire can start working without a separate setup ticket.
Close access when someone leaves
When a user is disabled or removed in Active Directory, their account in ServiceNow is deactivated in step, so offboarding shuts down access everywhere instead of leaving a live login behind.
What you can sync between Active Directory and ServiceNow
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 | ServiceNow objects | How this pairing syncs | |
|---|---|---|---|
| Organizational units On-prem AD DS containers (LDAP organizationalUnit) used to scope which users and groups a sync includes. | Tasks The base task table that incidents, changes, and requests extend. | Organizational units is specific to Active Directory and Tasks to ServiceNow — 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. | Knowledge Articles Support content that can be mirrored to help centers or search indexes. | Organizational contacts is specific to Active Directory and Knowledge Articles to ServiceNow — 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. | Custom Tables Scoped or u_-prefixed tables are addressable through the same Table API as standard ones. | Users is specific to Active Directory and Custom Tables to ServiceNow — each maps to any object or custom field on the other side. | |
| Groups Security and Microsoft 365 groups; synced two-way including name, type, and owner, with membership tracked separately. | Incidents The core ITSM ticket; commonly synced with engineering trackers and CRMs. | Groups is specific to Active Directory and Incidents to ServiceNow — 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. | Change Requests Track planned changes; synced to deployment and release tooling. | Group memberships is specific to Active Directory and Change Requests to ServiceNow — 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. | Problems Root-cause records linked to incidents, useful in cross-system reporting. | Devices is specific to Active Directory and Problems to ServiceNow — each maps to any object or custom field on the other side. |
How changes propagate between Active Directory and ServiceNow
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 ServiceNow 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 ServiceNow through its API, with automatic retries and rate-limit backoff.
ServiceNow Active Directory Interval-based propagation
DetectionStacksync polls ServiceNow for changes on an incremental schedule, reading only records changed since the previous pass. Polling on sys_updated_on timestamps.
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.
- ServiceNow: Subject to instance-level API rate limits and concurrency semaphores configured by administrators.
What ships with Active Directory ⇄ ServiceNow
Connect Active Directory and ServiceNow for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Active Directory–ServiceNow connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Active Directory or ServiceNow 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 ServiceNow record.
Observability
Monitoring
Track your Active Directory ⇄ ServiceNow 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 ServiceNow.
How the Active Directory and ServiceNow 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.
ServiceNow
- Integration surface
- REST API (Table, Import Set, and Aggregate APIs); SOAP remains for legacy integrations
- Authentication
- OAuth 2.0 or basic authentication against the instance
- Change detection
- Polling on sys_updated_on timestamps; instance admins can configure outbound push through business rules or Flow Designer
- Capabilities
- read · write
- Rate limits
- Subject to instance-level API rate limits and concurrency semaphores configured by administrators
How it works
How to connect Active Directory to ServiceNow — 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 ServiceNow 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
ServiceNow
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Active Directory and ServiceNow 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 ⇄ ServiceNowCustomers 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 ServiceNowCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Active Directory and ServiceNow integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Active Directory and ServiceNow: authenticate both systems, choose the objects to sync (such as Active Directory's Organizational units and Organizational contacts), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
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. ServiceNow: REST API (Table, Import Set, and Aggregate APIs); SOAP remains for legacy integrations. Authentication: OAuth 2.0 or basic authentication against the instance. Stacksync manages authentication, retries, and rate limits on both sides.
-
ServiceNow: Reference fields return sys_ids by default; the sysparm_display_value parameter switches to human-readable values, which affects field mapping. Active Directory: Writes require matching Graph application permissions (e.g. User.ReadWrite.All, Group.ReadWrite.All) with tenant admin consent; delegated and application scopes differ. Stacksync's field mapping accounts for these differences between Active Directory and ServiceNow 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 Active Directory and ServiceNow 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 ServiceNow connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Active Directory–ServiceNow integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Active Directory and ServiceNow. 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 483 integrations available for Active Directory and ServiceNow.
Popular · 8 of 483
-
Active Directory ⇄ Servicemax -
Active Directory ⇄ Adobe Sign -
Active Directory ⇄ Asana -
Active Directory ⇄ Docusign -
ServiceNow ⇄ Onelogin -
ServiceNow ⇄ Auth0 -
ServiceNow ⇄ Jumpcloud - ServiceNow ⇄ Azure Active Directory
No integrations match .
