Real-time
Two-way sync
Changes in Azure Active Directory or Freshsales instantly reflect in both systems. No stale data, no manual imports.
Security and identity ⇄ CRM
Azure Active Directory to Freshsales integration — real-time, two-way sync
Keep Azure Active Directory and Freshsales 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 Freshsales
Keep the people Freshsales and Azure Active Directory both track in agreement in real time: the internal users who own records in Freshsales, and the customer login accounts in Azure Active Directory.
A CRM and an identity system usually describe different populations. Freshsales 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 Freshsales 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 Freshsales are the same users Azure Active Directory authenticates. Left unconnected, a departure in Azure Active Directory leaves stale ownership sitting in Freshsales, and a signup in Azure Active Directory never reaches the account it belongs to.
Stacksync syncs Appointments, Notes, Sales activities, Products in Freshsales with Service principals, Directory roles, Devices, Users 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 Push product-qualified leads from the warehouse into Freshsales as contacts with lifecycle stages set.
- 02 Keep Freshsales accounts aligned with a billing system so plan and revenue fields stay current.
- 03 Sync manager, department, and jobTitle from an HRIS back onto Entra ID User attributes to keep dynamic groups and Conditional Access accurate.
- 04 Replicate Groups and their Members into a Postgres warehouse for access reviews and entitlement reporting.
Common sync patterns
Where Azure Active Directory governs your workforce: CRM users kept current
New employees in Azure Active Directory become active users in Freshsales 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.
Deactivation and record hand-off
When someone is disabled in Azure Active Directory, the matching user in Freshsales is deactivated too, and the accounts, contacts, and deals they owned are flagged for reassignment, so nothing goes unattended after they leave.
Where Azure Active Directory runs customer login accounts: identity on the customer record
Signup, account status, multi-factor enrollment, and last-login from Azure Active Directory land on the matching contact or account in Freshsales, so go-to-market teams see who has actually activated and who has gone dormant.
What you can sync between Azure Active Directory and Freshsales
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 | Freshsales objects | How this pairing syncs | |
|---|---|---|---|
| Service principals /servicePrincipals (enterprise apps) plus appRoleAssignments; read for app inventory and access-posture reporting. | Products Catalog items attached to deals for line-level revenue data. | Service principals is specific to Azure Active Directory and Products to Freshsales — 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. | Contacts Person records carrying lifecycle stages; the main entity for two-way CRM syncs. | Directory roles is specific to Azure Active Directory and Contacts to Freshsales — 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 kept aligned with billing, ERP, and warehouse tables. | Devices is specific to Azure Active Directory and Accounts to Freshsales — 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. | Deals Pipeline records synced to a warehouse for revenue reporting. | Users is specific to Azure Active Directory and Deals to Freshsales — 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. | Tasks Rep to-dos created from external triggers or synced for productivity reporting. | Groups is specific to Azure Active Directory and Tasks to Freshsales — 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. | Appointments Scheduled meetings readable for activity analytics. | Group memberships is specific to Azure Active Directory and Appointments to Freshsales — each maps to any object or custom field on the other side. |
How changes propagate between Azure Active Directory and Freshsales
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 Freshsales 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 Freshsales through its API, with automatic retries and rate-limit backoff.
Freshsales Azure Active Directory Sub-second propagation
DetectionFreshsales notifies Stacksync of record changes through webhook events. Polling with updated-at filters through views.
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.
- Freshsales: Subject to per-account API rate limits that vary by Freshworks plan.
What ships with Azure Active Directory ⇄ Freshsales
Connect Azure Active Directory and Freshsales for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Azure Active Directory–Freshsales connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Azure Active Directory or Freshsales 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 Freshsales record.
Observability
Monitoring
Track your Azure Active Directory ⇄ Freshsales 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 Freshsales.
How the Azure Active Directory and Freshsales 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
Freshsales
- Integration surface
- REST API
- Authentication
- API key sent as a Token authorization header
- Change detection
- Polling with updated-at filters through views; outbound webhooks can be configured via workflow automations
- Capabilities
- read · write · webhooks
- Rate limits
- Subject to per-account API rate limits that vary by Freshworks plan
How it works
How to connect Azure Active Directory to Freshsales — 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 Freshsales 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
Freshsales
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Azure Active Directory and Freshsales 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 ⇄ FreshsalesCustomers 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 FreshsalesCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Azure Active Directory and Freshsales integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Azure Active Directory and Freshsales: 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.
-
Freshsales: Current Freshsales versions use lifecycle stages on contacts instead of a separate lead object, so lead routing maps to a stage field. Azure Active Directory: Throttling is metered in resource units, not request counts: a tenant over 500 users allows about 8,000 ResourceUnits per 10 seconds per app for reads, and writes are capped near 3,000 requests per 2.5 minutes per app; over-limit calls return 429 with a Retry-After header. Stacksync's field mapping accounts for these differences between Azure Active Directory and Freshsales 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 Azure Active Directory and Freshsales records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Azure Active Directory and Freshsales connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Azure Active Directory–Freshsales integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Azure Active Directory and Freshsales. 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 Freshsales: Polling with updated-at filters through views; outbound webhooks can be configured via workflow automations. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
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 520 integrations available for Azure Active Directory and Freshsales.
Popular · 7 of 520
-
Azure Active Directory ⇄ Copper CRM -
Azure Active Directory ⇄ Creatio CRM -
Azure Active Directory ⇄ Folk CRM -
Freshsales ⇄ Okta -
Freshsales ⇄ Onelogin -
Freshsales ⇄ Auth0 -
Freshsales ⇄ Jumpcloud
No integrations match .
