Real-time
Two-way sync
Changes in Azure Active Directory or Salesforce instantly reflect in both systems. No stale data, no manual imports.
Security and identity ⇄ CRM
Azure Active Directory to Salesforce integration — real-time, two-way sync
Keep Azure Active Directory and Salesforce 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 Salesforce
Keep the people Salesforce and Azure Active Directory both track in agreement in real time: the internal users who own records in Salesforce, and the customer login accounts in Azure Active Directory.
A CRM and an identity system usually describe different populations. Salesforce 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 Salesforce 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 Salesforce are the same users Azure Active Directory authenticates. Left unconnected, a departure in Azure Active Directory leaves stale ownership sitting in Salesforce, and a signup in Azure Active Directory never reaches the account it belongs to.
Stacksync syncs Campaigns, Tasks and Events, Products and Price Books, Custom Objects in Salesforce with Applications, Service principals, Directory roles, Devices 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 metrics computed in a warehouse onto Account and Contact fields so reps see adoption signals on the record.
- 02 Trigger provisioning or billing changes in an operational database when an Opportunity moves to closed-won.
- 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 Salesforce, 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: Salesforce drives Azure Active Directory
A won or activated customer in Salesforce 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 Salesforce 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 Salesforce
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 | Salesforce objects | How this pairing syncs | |
|---|---|---|---|
| Service principals /servicePrincipals (enterprise apps) plus appRoleAssignments; read for app inventory and access-posture reporting. | Products and Price Books Catalog and pricing data; commonly mastered in an ERP and written into Salesforce. | Service principals is specific to Azure Active Directory and Products and Price Books to Salesforce — 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. | Custom Objects Org-specific tables with the __c suffix; discoverable via describe metadata so field mappings can be generated. | Directory roles is specific to Azure Active Directory and Custom Objects to Salesforce — 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. | Accounts Company records that anchor most syncs; typically mapped to customer tables in a database or ERP. | Devices is specific to Azure Active Directory and Accounts to Salesforce — 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. | Contacts People linked to Accounts; synced two-way with marketing, support, and warehouse person records. | Users is specific to Azure Active Directory and Contacts to Salesforce — 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. | Leads Unqualified prospects; often written into Salesforce from enrichment or product-signup pipelines. | Groups is specific to Azure Active Directory and Leads to Salesforce — 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. | Opportunities Deal records with stage and amount; synced to databases for pipeline reporting and to ERPs at close. | Group memberships is specific to Azure Active Directory and Opportunities to Salesforce — each maps to any object or custom field on the other side. |
How changes propagate between Azure Active Directory and Salesforce
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 Salesforce 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 Salesforce through its API, with automatic retries and rate-limit backoff.
Salesforce Azure Active Directory Sub-second propagation
DetectionChanges in Salesforce are captured at the source via change data capture — no polling loop against its API. Apex triggers are used whenever possible (Salesforce actively notifies Stacksync via an Apex trigger + callout class + remote site setting).
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.
- Salesforce: Daily API request allocations vary by edition and license count.
What ships with Azure Active Directory ⇄ Salesforce
Connect Azure Active Directory and Salesforce for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Azure Active Directory–Salesforce connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Azure Active Directory or Salesforce 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 Salesforce record.
Observability
Monitoring
Track your Azure Active Directory ⇄ Salesforce 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 Salesforce.
How the Azure Active Directory and Salesforce 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
Salesforce
- Integration surface
- REST, SOAP, and Bulk APIs
- Authentication
- OAuth login via a Salesforce user (browser-based authorization flow); requires "API Enabled" permission for polling mode, plus "Author Apex" and "Customize Application" OR "Modify All Data" for trigger mode
- Change detection
- Apex triggers are used whenever possible (Salesforce actively notifies Stacksync via an Apex trigger + callout class + remote site setting)
- Capabilities
- read · write · CDC
- Rate limits
- Daily API request allocations vary by edition and license count.
How it works
How to connect Azure Active Directory to Salesforce — 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 Salesforce 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
Salesforce
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Azure Active Directory and Salesforce 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 ⇄ SalesforceCustomers 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 SalesforceCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Azure Active Directory and Salesforce integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Azure Active Directory and Salesforce: authenticate both systems, choose the objects to sync (such as Azure Active Directory's Service principals and Directory roles), 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 Salesforce connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Azure Active Directory–Salesforce integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Azure Active Directory and Salesforce. 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 Salesforce: Apex triggers are used whenever possible (Salesforce actively notifies Stacksync via an Apex trigger + callout class + remote site setting). Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Salesforce side: Campaigns, Tasks and Events, Products and Price Books, Custom Objects, plus custom fields where Salesforce exposes them. On the Azure Active Directory side: Applications, Service principals, Directory roles, Devices. 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 535 integrations available for Azure Active Directory and Salesforce.
Popular · 8 of 535
-
Azure Active Directory ⇄ Freshworks CRM -
Azure Active Directory ⇄ Gladly -
Azure Active Directory ⇄ Gorgias -
Azure Active Directory ⇄ Infor CRM -
Salesforce ⇄ Jumpcloud - Salesforce ⇄ Active Directory
-
Salesforce ⇄ Okta -
Salesforce ⇄ Onelogin
No integrations match .
