Real-time
Two-way sync
Changes in Azure Active Directory or Linnworks instantly reflect in both systems. No stale data, no manual imports.
Security and identity ⇄ ERP
Azure Active Directory to Linnworks integration — real-time, two-way sync
Keep Azure Active Directory and Linnworks 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 Linnworks
Keep the employee, group, and account records that Linnworks and Azure Active Directory share aligned in real time, so a person added, moved, or offboarded in one system shows up correctly in the other within seconds.
An ERP and an identity system describe the same workforce from two angles. Linnworks holds the authoritative record of who works at the company, and often their department, title, manager, and cost center. Azure Active Directory controls the accounts, groups, and access those same people use every day. When the two aren't connected, every hire, transfer, and departure has to be keyed twice, and the window between someone leaving in Linnworks and their account still being active in Azure Active Directory is a real security exposure.
Stacksync syncs Stock Levels, Locations, Purchase Orders, Suppliers in Linnworks with Group memberships, Applications, Service principals, Directory roles in Azure Active Directory in real time, with field-level mapping and conflict resolution in place of CSV exports and nightly jobs. A new hire, a department change, or a termination propagates within seconds, and where you want changes to flow both ways — the ERP's org data into the directory, account status back into the ERP — the same mapping handles it.
That matters most at offboarding and audit time. When the directory reflects the ERP's current headcount and org structure, disabling access no longer depends on someone remembering to update a second system, and access reviews start from a roster both sides already agree on.
Common use cases
- 01 Keep stock levels consistent between Linnworks and external systems so multichannel listings stay aligned with sellable stock
- 02 Mirror processed orders, refunds, and returns into a warehouse for margin reporting across channels
- 03 Provision and deprovision Entra ID Users and Group memberships from an HR system of record so account enablement follows employment status.
- 04 Sync manager, department, and jobTitle from an HRIS back onto Entra ID User attributes to keep dynamic groups and Conditional Access accurate.
Common sync patterns
Keep profile attributes current
A name, email, title, manager, or department corrected in either system updates the other, so directory entries and employee records don't drift apart.
Align group and department membership
When someone changes team or department, their group or organizational-unit membership updates to match, keeping access tied to their current role.
One roster on a shared key
People are matched across both systems on an identifier you choose, such as work email or employee ID, so there is a single accurate list of who is active.
What you can sync between Azure Active Directory and Linnworks
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 | Linnworks objects | How this pairing syncs | |
|---|---|---|---|
| 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. | Stock Levels Per-location quantities sync outward so channels and planning tools reflect current availability. | Group memberships is specific to Azure Active Directory and Stock Levels to Linnworks — 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. | Locations Warehouse and fulfillment location records scope stock data during mapping. | Applications is specific to Azure Active Directory and Locations to Linnworks — 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. | Purchase Orders Replenishment POs sync with suppliers and accounting systems. | Service principals is specific to Azure Active Directory and Purchase Orders to Linnworks — 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. | Suppliers Vendor records keep procurement data consistent across tools. | Directory roles is specific to Azure Active Directory and Suppliers to Linnworks — 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. | Channel Listings Marketplace and webstore listing mappings tie channel products to internal SKUs. | Devices is specific to Azure Active Directory and Channel Listings to Linnworks — 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. | Returns & Refunds Post-sale records flow to finance and support systems. | Users is specific to Azure Active Directory and Returns & Refunds to Linnworks — each maps to any object or custom field on the other side. |
How changes propagate between Azure Active Directory and Linnworks
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 Linnworks 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 Linnworks through its API, with automatic retries and rate-limit backoff.
Linnworks Azure Active Directory Interval-based propagation
DetectionStacksync polls Linnworks for changes on an incremental schedule, reading only records changed since the previous pass. Polling on order and stock endpoints.
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.
- Linnworks: Per-endpoint rate limits apply on the Linnworks API.
What ships with Azure Active Directory ⇄ Linnworks
Connect Azure Active Directory and Linnworks for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Azure Active Directory–Linnworks connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Azure Active Directory or Linnworks 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 Linnworks record.
Observability
Monitoring
Track your Azure Active Directory ⇄ Linnworks 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 Linnworks.
How the Azure Active Directory and Linnworks 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
Linnworks
- Integration surface
- REST API
- Authentication
- Application credentials and an install token exchanged for a session token
- Change detection
- Polling on order and stock endpoints
- Capabilities
- read · write
- Rate limits
- Per-endpoint rate limits apply on the Linnworks API
How it works
How to connect Azure Active Directory to Linnworks — 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 Linnworks 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
Linnworks
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Azure Active Directory and Linnworks 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 ⇄ LinnworksCustomers 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 LinnworksCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Azure Active Directory and Linnworks integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Azure Active Directory and Linnworks: authenticate both systems, choose the objects to sync (such as Azure Active Directory's Group memberships and Applications), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
On the Linnworks side: Stock Levels, Locations, Purchase Orders, Suppliers, plus custom fields where Linnworks 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.
-
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.
-
Common patterns for Azure Active Directory and Linnworks: Keep profile attributes current; Align group and department membership; One roster on a shared key. A name, email, title, manager, or department corrected in either system updates the other, so directory entries and employee records don't drift apart.
-
Azure Active Directory: 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. Linnworks: REST API. Authentication: Application credentials and an install token exchanged for a session token. Stacksync manages authentication, retries, and rate limits on both sides.
-
Linnworks: Stock is tracked per location, and channel listings are mapped to internal SKUs, which is the join integrations rely on when reconciling marketplace data. Azure Active Directory: Hybrid identities synchronized from on-premises Active Directory via Entra Connect are mastered on-prem; many of their attributes are read-only in Entra ID and must be edited in AD DS. Stacksync's field mapping accounts for these differences between Azure Active Directory and Linnworks without custom code.
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 502 integrations available for Azure Active Directory and Linnworks.
Popular · 6 of 502
-
Azure Active Directory ⇄ Epicor ERP -
Azure Active Directory ⇄ Extensiv (3PL Central) - Linnworks ⇄ Active Directory
-
Linnworks ⇄ Okta -
Linnworks ⇄ Onelogin -
Linnworks ⇄ Auth0
No integrations match .
