Real-time
Two-way sync
Changes in Active Directory or Recurly instantly reflect in both systems. No stale data, no manual imports.
Security and identity ⇄ Accounting and finance
Active Directory to Recurly integration — real-time, two-way sync
Keep Active Directory and Recurly 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 Active Directory and Recurly
Keep the people who can act on financial records in Recurly matched to their identities in Active Directory, so access is provisioned, updated, and revoked in real time.
Recurly runs the money — the ledgers, invoices, budgets, and payments — and every one of those actions is taken by a person with a login. 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 Line Items, Coupons and Redemptions, Billing Info, Measured Units and Usage in Recurly aligned with Group memberships, Devices, Directory roles, Service principals & applications in 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 Trigger revenue-recognition or ERP entries when new_subscription and canceled_subscription webhooks fire.
- 02 Post usage records to Measured Units on metered Subscriptions from a metering database before each bill run.
- 03 Read Users, Groups, and directoryRole assignments into a warehouse for periodic access reviews and SOC 2 audit evidence.
- 04 Keep security-group memberships aligned with application entitlement tables so access reflects the right teams as they change.
Common sync patterns
One user roster across both systems
People, their status, and their contact details stay matched between Recurly and 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 Active Directory maps to their permission set in Recurly, 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 Recurly matches the identity source in 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 Active Directory and Recurly
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.
| Active Directory objects | Recurly objects | How this pairing syncs | |
|---|---|---|---|
| Directory roles Admin role assignments (directoryRole); read for access reviews and least-privilege governance. | Subscriptions Recurring subscription records tied to an Account and a Plan, with state, term, and next-bill date. Core object, synced two-way to drive provisioning and reporting. | Directory roles is specific to Active Directory and Subscriptions to Recurly — each maps to any object or custom field on the other side. | |
| Service principals & applications App registrations and enterprise apps; read-mostly for entitlement and license inventory. | Plans The product and pricing catalog (plan codes, intervals, add-ons); usually mastered in Recurly and read out, or mirrored from a product database. | Service principals & applications is specific to Active Directory and Plans to Recurly — each maps to any object or custom field on the other side. | |
| Organizational units On-prem AD DS containers (LDAP organizationalUnit) used to scope which users and groups a sync includes. | Invoices Charge and credit billing documents; read-heavy for revenue reporting, and creatable through Purchases for one-off charges. | Organizational units is specific to Active Directory and Invoices to Recurly — each maps to any object or custom field on the other side. | |
| Organizational contacts Directory contact objects (orgContact); synced for shared address-book and CRM person records. | Transactions Individual payment attempts — captures, refunds, and voids; typically read into a warehouse for reconciliation and dunning analysis. | Organizational contacts is specific to Active Directory and Transactions to Recurly — each maps to any object or custom field on the other side. | |
| Users User accounts in Entra ID and on-prem AD DS; synced two-way to create, update attributes, and enable or disable accounts. | Line Items One-time charges and credits on an account outside a subscription; synced for accurate revenue and adjustment reporting. | Users is specific to Active Directory and Line Items to Recurly — each maps to any object or custom field on the other side. | |
| Groups Security and Microsoft 365 groups; synced two-way including name, type, and owner, with membership tracked separately. | Coupons and Redemptions Discount definitions and their application to accounts and subscriptions; read for discount and promotion analysis. | Groups is specific to Active Directory and Coupons and Redemptions to Recurly — each maps to any object or custom field on the other side. |
How changes propagate between Active Directory and Recurly
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.
Active Directory Recurly Sub-second propagation
DetectionActive Directory notifies Stacksync of record changes through webhook events. Microsoft Graph delta query (change tracking) for Users and Groups, plus change-notification subscriptions (webhooks) for near-real-time triggers.
DeliveryEach detected change is written to Recurly through its API, with automatic retries and rate-limit backoff.
Recurly Active Directory Sub-second propagation
DetectionRecurly notifies Stacksync of record changes through webhook events. Webhooks (JSON or XML, one format per endpoint) for account, subscription, payment, and invoice events, plus incremental polling of list endpoints.
DeliveryEach detected change is written to Active Directory through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Active Directory: Graph throttles by resource-unit cost per app per tenant in 10-second windows (about 3,500–8,000 units by tenant size); directory delta tokens expire after ~7 days.
- Recurly: Production sites default to 1,000 requests/min with only GET requests counting toward the limit; sandbox sites 400/min with all requests counting; the limit is a sliding 5-minute window, X-RateLimit headers report the quota, and breaches return HTTP 429.
What ships with Active Directory ⇄ Recurly
Connect Active Directory and Recurly for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Active Directory–Recurly connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Active Directory or Recurly 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 Active Directory or Recurly record.
Observability
Monitoring
Track your Active Directory ⇄ Recurly sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Active Directory and Recurly.
How the Active Directory and Recurly connectors work
Active Directory
- Integration surface
- Microsoft Graph REST API (Entra ID / cloud) and LDAP/LDAPS (on-premises AD DS)
- Authentication
- OAuth 2.0 via the Microsoft identity platform — an app registration with application or delegated permissions (e.g. User.ReadWrite.All, Group.ReadWrite.All) and admin consent; on-prem AD DS uses a bound service account over LDAPS.
- Change detection
- Microsoft Graph delta query (change tracking) for Users and Groups, plus change-notification subscriptions (webhooks) for near-real-time triggers; on-prem AD DS uses the DirSync control and uSNChanged polling.
- Capabilities
- read · write · webhooks
- Rate limits
- Graph throttles by resource-unit cost per app per tenant in 10-second windows (about 3,500–8,000 units by tenant size); directory delta tokens expire after ~7 days.
Recurly
- Integration surface
- REST API (V3, date-versioned; legacy V2 XML API also exists)
- Authentication
- API key via HTTP Basic auth (key as username, blank password); keys are per-site, with separate sandbox and production keys
- Change detection
- Webhooks (JSON or XML, one format per endpoint) for account, subscription, payment, and invoice events, plus incremental polling of list endpoints sorted by updated_at with begin_time/end_time filters
- Capabilities
- read · write · webhooks
- Rate limits
- Production sites default to 1,000 requests/min with only GET requests counting toward the limit; sandbox sites 400/min with all requests counting; the limit is a sliding 5-minute window, X-RateLimit headers report the quota, and breaches return HTTP 429.
How it works
How to connect Active Directory to Recurly — 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 Active Directory and Recurly with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Active Directory
connected
Recurly
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Active Directory and Recurly 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 · Active Directory ⇄ RecurlyCustomers 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.
Active Directory RecurlyCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Active Directory and Recurly integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Active Directory and Recurly: authenticate both systems, choose the objects to sync (such as Active Directory's Directory roles and Service principals & applications), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Yes — Stacksync ships production-grade connectors for both Active Directory and Recurly. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Active Directory: Microsoft Graph delta query (change tracking) for Users and Groups, plus change-notification subscriptions (webhooks) for near-real-time triggers; on-prem AD DS uses the DirSync control and uSNChanged polling. On Recurly: Webhooks (JSON or XML, one format per endpoint) for account, subscription, payment, and invoice events, plus incremental polling of list endpoints sorted by updated_at with begin_time/end_time filters. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Recurly side: Line Items, Coupons and Redemptions, Billing Info, Measured Units and Usage, plus custom fields where Recurly exposes them. On the Active Directory side: Group memberships, Devices, Directory roles, Service principals & applications. 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 Active Directory and Recurly: 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 Recurly and Active Directory, so the finance system's login list reflects who actually works here instead of drifting out of date.
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 Active Directory and Recurly.
Popular · 8 of 499
-
Active Directory ⇄ QuickBooks -
Active Directory ⇄ Stripe -
Active Directory ⇄ Coupa -
Active Directory ⇄ Zuora - Recurly ⇄ Azure Active Directory
-
Recurly ⇄ Okta -
Recurly ⇄ Onelogin -
Recurly ⇄ Auth0
No integrations match .
