Skip to content
Security and identity ⇄ CRM

Active Directory to Veeva CRM integration — real-time, two-way sync

Keep Active Directory and Veeva CRM 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 Veeva CRM

Keep the people Veeva CRM and Active Directory both track in agreement in real time: the internal users who own records in Veeva CRM, and the customer login accounts in Active Directory.

A CRM and an identity system usually describe different populations. Veeva CRM 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 Veeva CRM are the same employees Active Directory provisions and disables, and when Active Directory also runs the login accounts for your product, the customers in Veeva CRM are the same users Active Directory authenticates. Left unconnected, a departure in Active Directory leaves stale ownership sitting in Veeva CRM, and a signup in Active Directory never reaches the account it belongs to.

Stacksync syncs Sample Transactions, Consent Records, Key Messages and CLM Content, Territories and Alignments in Veeva CRM with Group memberships, Devices, Directory roles, Service principals & applications 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 Replicate call and activity data into a warehouse for field-force effectiveness reporting.
  • 02 Keep consent records aligned between Veeva and marketing platforms so channel opt-outs are enforced everywhere.
  • 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

Deactivation and record hand-off

When someone is disabled in Active Directory, the matching user in Veeva CRM is deactivated too, and the accounts, contacts, and deals they owned are flagged for reassignment, so nothing goes unattended after they leave.

Where Active Directory runs customer login accounts: identity on the customer record

Signup, account status, multi-factor enrollment, and last-login from Active Directory land on the matching contact or account in Veeva CRM, so go-to-market teams see who has actually activated and who has gone dormant.

Group and entitlement membership as CRM fields

Membership of a directory group or an entitlement in Active Directory maps to fields in Veeva CRM, such as product tier, plan, or internal team, so segmentation reflects real access rather than a manual guess.

What you can sync between Active Directory and Veeva CRM

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 Veeva CRM objects How this pairing syncs
Group memberships Member and owner links between users and groups; membership add/remove changes are surfaced by delta query. Approved Email Activity Sent-email records from Veeva Approved Email, used in engagement reporting. Group memberships is specific to Active Directory and Approved Email Activity to Veeva CRM — 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. Accounts (HCPs and HCOs) Healthcare professionals and organizations; the central entity most syncs key on. Devices is specific to Active Directory and Accounts (HCPs and HCOs) to Veeva CRM — 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. Calls Recorded visits and interactions with HCPs, including samples dropped and key messages shown. Directory roles is specific to Active Directory and Calls to Veeva CRM — 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. Medical Inquiries Information requests captured in the field and routed to medical affairs. Service principals & applications is specific to Active Directory and Medical Inquiries to Veeva CRM — 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. Sample Transactions Sample disbursement records tracked for regulatory compliance. Organizational units is specific to Active Directory and Sample Transactions to Veeva CRM — 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. Consent Records Channel-level communication consent for HCPs, synced to enforce opt-outs across systems. Organizational contacts is specific to Active Directory and Consent Records to Veeva CRM — each maps to any object or custom field on the other side.

How changes propagate between Active Directory and Veeva CRM

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 Veeva CRM 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 Veeva CRM through its API, with automatic retries and rate-limit backoff.

Veeva CRM Active Directory Interval-based propagation

DetectionStacksync polls Veeva CRM for changes on an incremental schedule, reading only records changed since the previous pass. Polling on record modification 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.
  • Veeva CRM: Subject to the underlying platform's API request allocations, which are contract-dependent.
What ships with Active Directory ⇄ Veeva CRM

Connect Active Directory and Veeva CRM for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Active Directory–Veeva CRM connection.

Real-time

Two-way sync

Changes in Active Directory or Veeva CRM instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Active Directory or Veeva CRM 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 Veeva CRM record.

Observability

Monitoring

Track your Active Directory ⇄ Veeva CRM 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 Veeva CRM.

How the Active Directory and Veeva CRM 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.

Veeva CRM

Integration surface
Salesforce-platform APIs (REST, SOAP, Bulk) for classic Veeva CRM; Vault REST API for Vault CRM
Authentication
OAuth 2.0
Change detection
Polling on record modification timestamps; platform event streams where the underlying org enables them
Capabilities
read · write
Rate limits
Subject to the underlying platform's API request allocations, which are contract-dependent.
How it works

How to connect Active Directory to Veeva CRM — 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.

  1. 01

    Connect your apps

    Authenticate Active Directory and Veeva CRM with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Active Directory connected
    Veeva CRM connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Active Directory and Veeva CRM 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Active Directory ⇄ Veeva CRM
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Active Directory Veeva CRM
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Active Directory and Veeva CRM integration FAQ

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.

Learn more about security
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:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 503 integrations available for Active Directory and Veeva CRM.

Popular · 8 of 503
All Active Directory integrations All Veeva CRM integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own