Real-time
Two-way sync
Changes in Adyen or Azure Active Directory instantly reflect in both systems. No stale data, no manual imports.
Accounting and finance ⇄ Security and identity
Adyen to Azure Active Directory integration — real-time, two-way sync
Keep Adyen 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 Adyen and Azure Active Directory
Keep the people who can act on financial records in Adyen matched to their identities in Azure Active Directory, so access is provisioned, updated, and revoked in real time.
Adyen runs the money — the ledgers, invoices, budgets, and payments — and every one of those actions is taken by a person with a login. Azure Active Directory is where those people and their access actually live: who is employed, what team they belong to, and what they are allowed to do. The two systems rarely share customers or transactions, but they share the one thing that governs both — the user. When that overlap is maintained by hand, a departed employee keeps finance access for weeks and a new hire waits on a ticket to get any.
Stacksync keeps Users and API Credentials, Webhook Configurations, Settlement Detail Reports, Payments in Adyen aligned with Applications, Service principals, Directory roles, Devices in Azure Active Directory, field by field and in real time. A person added, moved, or deactivated on the identity side updates their matching user in the finance system within seconds, with the role or permission set mapped from the group they belong to. Direction is yours to set: lead provisioning from the directory, or let an HR-owned finance record drive the downstream accounts.
For a finance team, that alignment is an audit control rather than a convenience. When the user list in the books matches the identity source of truth, segregation-of-duties and access reviews start from data that is already correct instead of an export that was current last quarter.
Common use cases
- 01 Ingest AUTHORISATION, CAPTURE, REFUND, and CHARGEBACK webhooks into Postgres or a warehouse so finance reconciles Adyen settlements against orders in an ERP without manual report exports.
- 02 Trigger a capture, refund, or cancel on an Adyen payment when an order's state changes in a CRM, OMS, or ERP, and write the returned pspReference and status back onto the record.
- 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
One user roster across both systems
People, their status, and their contact details stay matched between Adyen and Azure Active Directory, so the finance system's login list reflects who actually works here instead of drifting out of date.
Group and role membership drives finance permissions
A person's group or role in Azure Active Directory maps to their permission set in Adyen, so who can approve, post, or view is governed from one place instead of maintained twice.
Access reviews backed by live data
Because the user list in Adyen matches the identity source in Azure Active Directory in real time, access certifications and SOX-style reviews start from current membership rather than a stale spreadsheet.
What you can sync between Adyen 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.
| Adyen objects | Azure Active Directory objects | How this pairing syncs | |
|---|---|---|---|
| Users and API Credentials Customer Area users and API-credential objects managed via the Management API; created, updated, and deprovisioned to keep Adyen access aligned with an IdP or HR source. | Service principals /servicePrincipals (enterprise apps) plus appRoleAssignments; read for app inventory and access-posture reporting. | Users and API Credentials is specific to Adyen and Service principals to Azure Active Directory — each maps to any object or custom field on the other side. | |
| Webhook Configurations Per-company or per-merchant webhook subscriptions (Management API); created, listed, and updated to control which events Adyen sends and to which endpoint and HMAC key. | Directory roles /directoryRoles and roleManagement assignments; read for privileged-access reviews, with role-assignment writes where the granted scopes permit. | Webhook Configurations is specific to Adyen and Directory roles to Azure Active Directory — each maps to any object or custom field on the other side. | |
| Settlement Detail Reports Downloadable reports of settled transactions, fees, and payouts per merchant account; read-only, delivered when a report webhook fires, and loaded for finance reconciliation. | Devices /devices registered or joined to the tenant; typically read-only into asset and security databases. | Settlement Detail Reports is specific to Adyen and Devices to Azure Active Directory — each maps to any object or custom field on the other side. | |
| Payments Checkout API payment requests and results (/payments); created to authorize a card, wallet, or local payment, and retrieved by pspReference. Final state arrives asynchronously via the AUTHORISATION webhook. | 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. | Payments is specific to Adyen and Users to Azure Active Directory — each maps to any object or custom field on the other side. | |
| Modifications (Captures, Refunds, Cancels) Actions on an authorized payment via /payments/{pspReference}/captures, /refunds, and /cancels; written to settle, return, or void funds, with results confirmed by CAPTURE and REFUND webhooks. | Groups /groups covering security and Microsoft 365 groups; created, updated, and deleted through Graph, and read into warehouses for entitlement reporting. | Modifications (Captures, Refunds, Cancels) is specific to Adyen and Groups to Azure Active Directory — each maps to any object or custom field on the other side. | |
| Payment Links Hosted payment link objects created through /paymentLinks; created, retrieved, and expired, with paid or expired status reported back through webhooks for accounts-receivable sync. | 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. | Payment Links is specific to Adyen and Group memberships to Azure Active Directory — each maps to any object or custom field on the other side. |
How changes propagate between Adyen 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.
Adyen Azure Active Directory Sub-second propagation
DetectionAdyen notifies Stacksync of record changes through webhook events. Standard webhooks for payment events (AUTHORISATION, CAPTURE, REFUND, CHARGEBACK, and more) plus Management, Balance Platform, and report webhooks.
DeliveryEach detected change is written to Azure Active Directory through its API, with automatic retries and rate-limit backoff.
Azure Active Directory Adyen 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 Adyen through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Adyen: Adyen does not publish fixed numeric rate limits; excessive requests return HTTP 429, and the Management API reports 'too many requests' in the error detail. Adyen recommends exponential backoff, and no rate-limit response headers are documented.
- 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 Adyen ⇄ Azure Active Directory
Connect Adyen and Azure Active Directory for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Adyen–Azure Active Directory connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Adyen 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 Adyen or Azure Active Directory record.
Observability
Monitoring
Track your Adyen ⇄ 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 Adyen and Azure Active Directory.
How the Adyen and Azure Active Directory connectors work
Adyen
- Integration surface
- REST APIs on adyen.com - Checkout (/checkout/v71), Management (/v3), Balance Platform / Configuration, Transfers, Payouts, and Reports, with standard webhooks for events
- Authentication
- API key in the X-API-Key header per web service or Balance Platform user (primary for Checkout, Management, and Balance Platform); Basic auth for classic web-service users; OAuth 2.0 for partner integrations; client keys are client-side only
- Change detection
- Standard webhooks for payment events (AUTHORISATION, CAPTURE, REFUND, CHARGEBACK, and more) plus Management, Balance Platform, and report webhooks; all HMAC-signed and acknowledged with a 2xx within about 10 seconds. No database-style CDC; historical transactions come from Settlement Detail Reports
- Capabilities
- read · write · webhooks
- Rate limits
- Adyen does not publish fixed numeric rate limits; excessive requests return HTTP 429, and the Management API reports 'too many requests' in the error detail. Adyen recommends exponential backoff, and no rate-limit response headers are documented.
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 Adyen 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.
- 01
Connect your apps
Authenticate Adyen 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.
Adyen
connected
Azure Active Directory
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Adyen 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.
objects · Adyen ⇄ Azure Active DirectoryCustomers 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.
Adyen Azure Active DirectoryCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Adyen and Azure Active Directory integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Adyen and Azure Active Directory: authenticate both systems, choose the objects to sync (such as Adyen's Users and API Credentials and Webhook Configurations), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Change detection on Adyen: Standard webhooks for payment events (AUTHORISATION, CAPTURE, REFUND, CHARGEBACK, and more) plus Management, Balance Platform, and report webhooks; all HMAC-signed and acknowledged with a 2xx within about 10 seconds. No database-style CDC; historical transactions come from Settlement Detail Reports. 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. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Adyen side: Users and API Credentials, Webhook Configurations, Settlement Detail Reports, Payments, plus custom fields where Adyen exposes them. On the Azure Active Directory side: Applications, Service principals, Directory roles, Devices. 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 Adyen and Azure Active Directory: One user roster across both systems; Group and role membership drives finance permissions; Access reviews backed by live data. People, their status, and their contact details stay matched between Adyen and Azure Active Directory, so the finance system's login list reflects who actually works here instead of drifting out of date.
-
Adyen: REST APIs on adyen.com - Checkout (/checkout/v71), Management (/v3), Balance Platform / Configuration, Transfers, Payouts, and Reports, with standard webhooks for events. Authentication: API key in the X-API-Key header per web service or Balance Platform user (primary for Checkout, Management, and Balance Platform); Basic auth for classic web-service users; OAuth 2.0 for partner integrations; client keys are client-side only. 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. Stacksync manages authentication, retries, and rate limits on both sides.
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 499 integrations available for Adyen and Azure Active Directory.
Popular · 8 of 499
-
Adyen ⇄ Okta -
Adyen ⇄ Onelogin -
Adyen ⇄ Auth0 -
Adyen ⇄ Jumpcloud -
Azure Active Directory ⇄ Navan -
Azure Active Directory ⇄ Ramp -
Azure Active Directory ⇄ Recurly -
Azure Active Directory ⇄ Rillet
No integrations match .
