Real-time
Two-way sync
Changes in Azure Active Directory or Sage 100 instantly reflect in both systems. No stale data, no manual imports.
Security and identity ⇄ ERP
Azure Active Directory to Sage 100 integration — real-time, two-way sync
Keep Azure Active Directory and Sage 100 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 Sage 100
Keep the employee, group, and account records that Sage 100 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. Sage 100 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 Sage 100 and their account still being active in Azure Active Directory is a real security exposure.
Stacksync syncs Inventory Items, Sales Orders, AR Invoices, Purchase Orders in Sage 100 with Directory roles, Devices, Users, Groups 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 Push e-commerce and EDI orders into the Sales Order module instead of rekeying them.
- 02 Publish item, pricing, and on-hand inventory to online catalogs on a schedule.
- 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
Create accounts from new records
A person added in one system gets a matching account or record in the other automatically, so a new hire can be granted access without anyone re-keying their details.
Disable access at offboarding
When a person is marked terminated or inactive in one system, the matching account is disabled in the other within seconds, closing the gap that leaves ex-employees with live access.
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.
What you can sync between Azure Active Directory and Sage 100
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 | Sage 100 objects | How this pairing syncs | |
|---|---|---|---|
| Applications App registrations under /applications; usually read into a database or CMDB for app ownership and credential-expiry tracking. | Inventory Items Item master with pricing and quantities, synced to e-commerce catalogs. | Applications is specific to Azure Active Directory and Inventory Items to Sage 100 — 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. | Sales Orders Order headers and lines, the usual write target for web and EDI orders. | Service principals is specific to Azure Active Directory and Sales Orders to Sage 100 — 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. | AR Invoices Billing documents synced outward for payment status and revenue reporting. | Directory roles is specific to Azure Active Directory and AR Invoices to Sage 100 — 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. | Purchase Orders Procurement documents read for spend and receiving workflows. | Devices is specific to Azure Active Directory and Purchase Orders to Sage 100 — 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. | GL Accounts Chart of accounts read for mapping transactions in finance integrations. | Users is specific to Azure Active Directory and GL Accounts to Sage 100 — 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. | Journal Entries Posted GL activity replicated to warehouses for FP&A. | Groups is specific to Azure Active Directory and Journal Entries to Sage 100 — each maps to any object or custom field on the other side. |
How changes propagate between Azure Active Directory and Sage 100
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 Sage 100 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 applied to Sage 100 as a row-level write, with types converted between the two schemas.
Sage 100 Azure Active Directory Interval-based propagation
DetectionStacksync polls Sage 100 for changes on an incremental schedule, reading only records changed since the previous pass. Scheduled polling.
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.
What ships with Azure Active Directory ⇄ Sage 100
Connect Azure Active Directory and Sage 100 for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Azure Active Directory–Sage 100 connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Azure Active Directory or Sage 100 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 Sage 100 record.
Observability
Monitoring
Track your Azure Active Directory ⇄ Sage 100 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 Sage 100.
How the Azure Active Directory and Sage 100 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
Sage 100
- Integration surface
- ODBC (ProvideX driver) for reads; Business Object Interface (BOI) or Sage-provided web services for writes
- Authentication
- Sage 100 company and user credentials; ODBC DSN credentials for direct reads
- Change detection
- Scheduled polling; no webhooks or change log on the integration surface
- Capabilities
- read · write
How it works
How to connect Azure Active Directory to Sage 100 — 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 Sage 100 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
Sage 100
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Azure Active Directory and Sage 100 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 ⇄ Sage 100Customers 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 Sage 100Company company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Azure Active Directory and Sage 100 integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Azure Active Directory and Sage 100: authenticate both systems, choose the objects to sync (such as Azure Active Directory's Applications and Service principals), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Yes — Stacksync ships production-grade connectors for both Azure Active Directory and Sage 100. 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 Sage 100: Scheduled polling; no webhooks or change log on the integration surface. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Sage 100 side: Inventory Items, Sales Orders, AR Invoices, Purchase Orders, plus custom fields where Sage 100 exposes them. On the Azure Active Directory side: Directory roles, Devices, Users, Groups. 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 Sage 100: Create accounts from new records; Disable access at offboarding; Keep profile attributes current. A person added in one system gets a matching account or record in the other automatically, so a new hire can be granted access without anyone re-keying their details.
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 505 integrations available for Azure Active Directory and Sage 100.
Popular · 8 of 505
-
Azure Active Directory ⇄ Rootstock ERP - Azure Active Directory ⇄ Sage 300
- Azure Active Directory ⇄ Sage Intacct
- Azure Active Directory ⇄ Sage X3
- Sage 100 ⇄ Active Directory
-
Sage 100 ⇄ Okta -
Sage 100 ⇄ Onelogin -
Sage 100 ⇄ Auth0
No integrations match .
