Skip to content
Security and identity ⇄ Accounting and finance

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

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

Keep the people who can act on financial records in Recurly matched to their identities in Azure 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. 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 Transactions, Line Items, Coupons and Redemptions, Billing Info in Recurly aligned with Users, Groups, Group memberships, Applications 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 Post usage records to Measured Units on metered Subscriptions from a metering database before each bill run.
  • 02 Sync Accounts and Subscriptions bi-directionally with Postgres so product and provisioning systems read live entitlement state and write plan or seat changes back to Recurly.
  • 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

Group and role membership drives finance permissions

A person's group or role in Azure 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 Azure Active Directory in real time, access certifications and SOX-style reviews start from current membership rather than a stale spreadsheet.

People attributes for allocation and approvals

Department, manager, and employee identifiers carried in Azure Active Directory flow to Recurly, so expense routing, cost-center allocation, and approval chains use the same org data as the directory.

What you can sync between Azure 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.

Azure Active Directory objects Recurly objects How this pairing syncs
Directory roles /directoryRoles and roleManagement assignments; read for privileged-access reviews, with role-assignment writes where the granted scopes permit. Invoices Charge and credit billing documents; read-heavy for revenue reporting, and creatable through Purchases for one-off charges. Directory roles is specific to Azure Active Directory and Invoices to Recurly — 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. Transactions Individual payment attempts — captures, refunds, and voids; typically read into a warehouse for reconciliation and dunning analysis. Devices is specific to Azure Active Directory and Transactions to Recurly — 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. Line Items One-time charges and credits on an account outside a subscription; synced for accurate revenue and adjustment reporting. Users is specific to Azure Active Directory and Line Items to Recurly — 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. Coupons and Redemptions Discount definitions and their application to accounts and subscriptions; read for discount and promotion analysis. Groups is specific to Azure Active Directory and Coupons and Redemptions to Recurly — 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. Billing Info Tokenized payment method (card/ACH) on an account; written when onboarding customers and read for payment-health signals (never stores raw card numbers). Group memberships is specific to Azure Active Directory and Billing Info to Recurly — each maps to any object or custom field on the other side.
Applications App registrations under /applications; usually read into a database or CMDB for app ownership and credential-expiry tracking. Measured Units and Usage Metered-billing units; usage records are posted to a subscription before each bill run for consumption-based pricing. Applications is specific to Azure Active Directory and Measured Units and Usage to Recurly — each maps to any object or custom field on the other side.

How changes propagate between Azure 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.

Azure Active Directory Recurly 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 Recurly through its API, with automatic retries and rate-limit backoff.

Recurly Azure 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 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.
  • 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 Azure Active Directory ⇄ Recurly

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your Azure 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 Azure Active Directory and Recurly.

How the Azure Active Directory and Recurly 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

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 Azure 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.

  1. 01

    Connect your apps

    Authenticate Azure 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.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Azure Active Directory connected
    Recurly connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Azure 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Azure Active Directory ⇄ Recurly
    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
    Azure Active Directory Recurly
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

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

Learn more about security
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:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 499 integrations available for Azure Active Directory and Recurly.

Popular · 8 of 499
All Azure Active Directory integrations All Recurly integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

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

Book a demo Tour the platform on your own