Real-time
Two-way sync
Changes in Azure Active Directory or Nutshell instantly reflect in both systems. No stale data, no manual imports.
Security and identity ⇄ CRM
Azure Active Directory to Nutshell integration — real-time, two-way sync
Keep Azure Active Directory and Nutshell 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 Nutshell
Keep the people Nutshell and Azure Active Directory both track in agreement in real time: the internal users who own records in Nutshell, and the customer login accounts in Azure Active Directory.
A CRM and an identity system usually describe different populations. Nutshell 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 Nutshell 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 Nutshell are the same users Azure Active Directory authenticates. Left unconnected, a departure in Azure Active Directory leaves stale ownership sitting in Nutshell, and a signup in Azure Active Directory never reaches the account it belongs to.
Stacksync syncs Notes, Products, Tags, Users in Nutshell with Group memberships, Applications, Service principals, Directory roles 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 Keep People and Companies consistent between Nutshell and email marketing or outreach tools.
- 02 Write subscription or product data from internal systems into Nutshell so reps see account context.
- 03 Mirror Applications and Service principals into a database or CMDB to track app ownership and credential expiry.
- 04 Reconcile Entra ID Users and assignedLicenses with an ITSM or finance database to audit license allocation and reclaim unused seats.
Common sync patterns
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 Nutshell, 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 Azure Active Directory maps to fields in Nutshell, 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: Nutshell drives Azure Active Directory
A won or activated customer in Nutshell 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.
What you can sync between Azure Active Directory and Nutshell
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 | Nutshell objects | How this pairing syncs | |
|---|---|---|---|
| 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. | Users Rep records used to resolve ownership when syncing assignments | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Devices /devices registered or joined to the tenant; typically read-only into asset and security databases. | Tags Segmentation labels mapped to lists or filters in downstream tools | Devices is specific to Azure Active Directory and Tags to Nutshell — 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 Nutshell's deal object; synced as the pipeline record linked to people and companies | Groups is specific to Azure Active Directory and Leads to Nutshell — 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. | People Individual contacts, kept consistent with marketing and outreach tools | Group memberships is specific to Azure Active Directory and People to Nutshell — each maps to any object or custom field on the other side. | |
| Applications App registrations under /applications; usually read into a database or CMDB for app ownership and credential-expiry tracking. | Companies Account records that group people and leads for account-level syncs | Applications is specific to Azure Active Directory and Companies to Nutshell — 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. | Activities Logged calls, meetings, and emails used for engagement reporting | Service principals is specific to Azure Active Directory and Activities to Nutshell — each maps to any object or custom field on the other side. |
How changes propagate between Azure Active Directory and Nutshell
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 Nutshell 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 Nutshell through its API, with automatic retries and rate-limit backoff.
Nutshell Azure Active Directory Sub-second propagation
DetectionNutshell notifies Stacksync of record changes through webhook events. Webhook subscriptions for record events, with polling as fallback.
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.
- Nutshell: Subject to the platform's API rate limits.
What ships with Azure Active Directory ⇄ Nutshell
Connect Azure Active Directory and Nutshell for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Azure Active Directory–Nutshell connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Azure Active Directory or Nutshell 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 Nutshell record.
Observability
Monitoring
Track your Azure Active Directory ⇄ Nutshell 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 Nutshell.
How the Azure Active Directory and Nutshell 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
Nutshell
- Integration surface
- JSON-RPC API over HTTPS; a newer REST API is also offered
- Authentication
- HTTP Basic with account email and API key
- Change detection
- webhook subscriptions for record events, with polling as fallback
- Capabilities
- read · write · webhooks
- Rate limits
- subject to the platform's API rate limits
How it works
How to connect Azure Active Directory to Nutshell — 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 Nutshell 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
Nutshell
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Azure Active Directory and Nutshell 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 ⇄ NutshellCustomers 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 NutshellCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Azure Active Directory and Nutshell integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Azure Active Directory and Nutshell: authenticate both systems, choose the objects to sync (such as Azure Active Directory's Users and Devices), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
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 Nutshell 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 Nutshell connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Azure Active Directory–Nutshell integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Azure Active Directory and Nutshell. 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 Nutshell: Webhook subscriptions for record events, with polling as fallback. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Nutshell side: Notes, Products, Tags, Users, plus custom fields where Nutshell exposes them. On the Azure Active Directory side: Group memberships, Applications, Service principals, Directory roles. Stacksync auto-detects both schemas and converts types between the two systems.
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 418 integrations available for Azure Active Directory and Nutshell.
Popular · 8 of 418
-
Azure Active Directory ⇄ Gladly -
Azure Active Directory ⇄ Gorgias -
Azure Active Directory ⇄ Infor CRM -
Azure Active Directory ⇄ Insightly -
Nutshell ⇄ Auth0 -
Nutshell ⇄ Jumpcloud - Nutshell ⇄ Active Directory
-
Nutshell ⇄ Okta
No integrations match .
