Two-way sync
Changes in Azure Active Directory or Infor CloudSuite instantly reflect in both systems. No stale data, no manual imports.
Keep Azure Active Directory and Infor CloudSuite in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
An ERP and an identity system describe the same workforce from two angles. Infor CloudSuite 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 Infor CloudSuite and their account still being active in Azure Active Directory is a real security exposure.
Stacksync syncs Items, Customers, Suppliers / vendors, Sales orders in Infor CloudSuite 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.
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.
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.
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.
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 | Infor CloudSuite objects | How this pairing syncs | |
|---|---|---|---|
| Service principals /servicePrincipals (enterprise apps) plus appRoleAssignments; read for app inventory and access-posture reporting. | Sales orders Demand-side documents synced in from commerce channels and out for fulfillment visibility. | Service principals is specific to Azure Active Directory and Sales orders to Infor CloudSuite — 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. | Purchase orders Supply-side documents shared with procurement and supplier portals. | Directory roles is specific to Azure Active Directory and Purchase orders to Infor CloudSuite — 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. | Invoices Billing documents synced to finance and reporting systems. | Devices is specific to Azure Active Directory and Invoices to Infor CloudSuite — 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. | Inventory balances On-hand quantities exposed so external channels quote against real stock. | Users is specific to Azure Active Directory and Inventory balances to Infor CloudSuite — 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. | GL journal entries Financial postings replicated for consolidated reporting. | Groups is specific to Azure Active Directory and GL journal entries to Infor CloudSuite — 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. | Items Product and material masters synced to commerce, CRM, and planning tools. | Group memberships is specific to Azure Active Directory and Items to Infor CloudSuite — each maps to any object or custom field on the other side. |
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.
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 Infor CloudSuite through its API, with automatic retries and rate-limit backoff.
DetectionStacksync polls Infor CloudSuite for changes on an incremental schedule, reading only records changed since the previous pass. Event-style BOD publications through Infor ION where configured.
DeliveryEach detected change is written to Azure Active Directory through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Azure Active Directory–Infor CloudSuite connection.
Changes in Azure Active Directory or Infor CloudSuite instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Azure Active Directory or Infor CloudSuite data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Azure Active Directory or Infor CloudSuite record.
Track your Azure Active Directory ⇄ Infor CloudSuite sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Azure Active Directory and Infor CloudSuite.
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.
Authenticate Azure Active Directory and Infor CloudSuite with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pick the Azure Active Directory and Infor CloudSuite 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Azure Active Directory and Infor CloudSuite: 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.
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 Infor CloudSuite: Event-style BOD publications through Infor ION where configured; otherwise polling. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the Infor CloudSuite side: Items, Customers, Suppliers / vendors, Sales orders, plus custom fields where Infor CloudSuite exposes them. On the Azure Active Directory side: Service principals, Directory roles, Devices, Users. 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 Infor CloudSuite: One roster on a shared key; Create accounts from new records; Disable access at offboarding. 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.
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. Infor CloudSuite: REST APIs exposed through the Infor ION API gateway; integration payloads are standardized as Business Object Documents (BODs). Authentication: OAuth 2.0 via Infor OS / ION API credentials. Stacksync manages authentication, retries, and rate limits on both sides.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 403 integrations available for Azure Active Directory and Infor CloudSuite.