Skip to content
ERP ⇄ Security and identity

Acumatica to Azure Active Directory integration — real-time, two-way sync

Keep Acumatica and Azure Active Directory 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 Acumatica and Azure Active Directory

Keep the employee, group, and account records that Acumatica 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. Acumatica 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 Acumatica and their account still being active in Azure Active Directory is a real security exposure.

Stacksync syncs Payments, Journal Transactions, Projects, Opportunities and Cases in Acumatica with Service principals, Directory roles, Devices, Users 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 Two-way sync of customers, orders, and invoices between Acumatica and a CRM so sales sees ERP truth without ERP logins.
  • 02 Create sales orders in Acumatica from e-commerce platforms and sync shipment and tracking status back to the storefront.
  • 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

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 Acumatica and Azure Active Directory

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.

Acumatica objects Azure Active Directory objects How this pairing syncs
Stock Items Inventory master data with quantities shared with external sales channels. Devices /devices registered or joined to the tenant; typically read-only into asset and security databases. Stock Items is specific to Acumatica and Devices to Azure Active Directory — each maps to any object or custom field on the other side.
Shipments Fulfillment documents read to update tracking in storefronts and CRMs. 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. Shipments is specific to Acumatica and Users to Azure Active Directory — each maps to any object or custom field on the other side.
Payments Customer payment records reconciled against invoices from payment platforms. Groups /groups covering security and Microsoft 365 groups; created, updated, and deleted through Graph, and read into warehouses for entitlement reporting. Payments is specific to Acumatica and Groups to Azure Active Directory — each maps to any object or custom field on the other side.
Journal Transactions GL entries replicated into reporting databases. 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. Journal Transactions is specific to Acumatica and Group memberships to Azure Active Directory — each maps to any object or custom field on the other side.
Projects Project cost and billing structures synced with delivery tools. Applications App registrations under /applications; usually read into a database or CMDB for app ownership and credential-expiry tracking. Projects is specific to Acumatica and Applications to Azure Active Directory — each maps to any object or custom field on the other side.
Opportunities and Cases Built-in CRM records synced with external sales and support tools. Service principals /servicePrincipals (enterprise apps) plus appRoleAssignments; read for app inventory and access-posture reporting. Opportunities and Cases is specific to Acumatica and Service principals to Azure Active Directory — each maps to any object or custom field on the other side.

How changes propagate between Acumatica and Azure Active Directory

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.

Acumatica Azure Active Directory Sub-second propagation

DetectionAcumatica notifies Stacksync of record changes through webhook events. Push notifications configurable on data changes, plus polling on LastModifiedDateTime fields.

DeliveryEach detected change is written to Azure Active Directory through its API, with automatic retries and rate-limit backoff.

Azure Active Directory Acumatica 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 Acumatica 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.
What ships with Acumatica ⇄ Azure Active Directory

Connect Acumatica and Azure Active Directory for flexible, real-time data sync.

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your Acumatica ⇄ Azure Active Directory sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Acumatica and Azure Active Directory.

How the Acumatica and Azure Active Directory connectors work

Acumatica

Integration surface
Contract-based REST API (JSON over versioned endpoints), plus SOAP web services and OData access to Generic Inquiries
Authentication
OAuth 2.0 or cookie-based session login with Acumatica credentials
Change detection
Push notifications configurable on data changes, plus polling on LastModifiedDateTime fields
Capabilities
read · write · webhooks

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
How it works

How to connect Acumatica to Azure Active Directory — 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 Acumatica and Azure Active Directory 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
    Acumatica connected
    Azure Active Directory connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Acumatica and Azure Active Directory 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 · Acumatica ⇄ Azure Active Directory
    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
    Acumatica Azure Active Directory
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Acumatica and Azure Active Directory 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.

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 514 integrations available for Acumatica and Azure Active Directory.

Popular · 8 of 514
Coworkers laughing in front of a laptop in a casual office setting

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