Skip to content
Business productivity ⇄ Accounting and finance

Microsoft 365 to Recurly integration — real-time, two-way sync

Keep Microsoft 365 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 Microsoft 365 and Recurly

Connect the financial records in Recurly with the work happening in Microsoft 365, so both stay current without exports or copy-paste.

Recurly holds the financial truth: who the customers are, what they were billed, what they paid. Microsoft 365 is where part of the day-to-day work happens, and that work often involves the same customers and transactions. Without a live connection, the two drift apart, and people end up answering questions from stale copies.

Stacksync keeps Transactions, Line Items, Coupons and Redemptions, Billing Info in Recurly and SharePoint Sites & Lists, Teams, Planner & To Do Tasks, Users in Microsoft 365 in sync, bi-directionally and in real time. Whatever records Microsoft 365 keeps and whatever events it produces, the overlap with Recurly is mapped field by field, and a change on either side shows up on the other within seconds.

There is no middleware to build, no API rate limits to babysit, and no nightly job that leaves the morning running on yesterday's data.

Common use cases

  • 01 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.
  • 02 Trigger revenue-recognition or ERP entries when new_subscription and canceled_subscription webhooks fire.
  • 03 Keep CRM contacts and Microsoft 365 contacts aligned in both directions.
  • 04 Sync employee records from an HR system into Entra ID users and group memberships.

Common sync patterns

Where Microsoft 365 collects payments or triggers charges: events land in Recurly

Payment and charge activity flows into Recurly as it happens, so the books reflect reality without manual reconciliation.

Where Microsoft 365 tracks people or companies: one identity

A customer's details updated in either system update the other, so finance and the rest of the business stop maintaining two versions of the same customer.

Where Microsoft 365 handles customer conversations: billing context in view

Front-line teams see invoice and payment status from Recurly next to the customer they are helping, without logging into the finance system.

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

Microsoft 365 objects Recurly objects How this pairing syncs
Calendar Events Events synced with scheduling tools and CRMs for meeting visibility. 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. Calendar Events is specific to Microsoft 365 and Subscriptions to Recurly — each maps to any object or custom field on the other side.
Contacts Personal and org contacts kept consistent with CRM contact records. Plans The product and pricing catalog (plan codes, intervals, add-ons); usually mastered in Recurly and read out, or mirrored from a product database. Contacts is specific to Microsoft 365 and Plans to Recurly — each maps to any object or custom field on the other side.
OneDrive Files (driveItems) File and folder metadata synced for document workflows and audits. Invoices Charge and credit billing documents; read-heavy for revenue reporting, and creatable through Purchases for one-off charges. OneDrive Files (driveItems) is specific to Microsoft 365 and Invoices to Recurly — each maps to any object or custom field on the other side.
SharePoint Sites & Lists List items read and written like lightweight database tables. Transactions Individual payment attempts — captures, refunds, and voids; typically read into a warehouse for reconciliation and dunning analysis. SharePoint Sites & Lists is specific to Microsoft 365 and Transactions to Recurly — each maps to any object or custom field on the other side.
Teams Team and membership data provisioned from upstream systems. Line Items One-time charges and credits on an account outside a subscription; synced for accurate revenue and adjustment reporting. Teams is specific to Microsoft 365 and Line Items to Recurly — each maps to any object or custom field on the other side.
Planner & To Do Tasks Task items synced with project and work-management tools. Coupons and Redemptions Discount definitions and their application to accounts and subscriptions; read for discount and promotion analysis. Planner & To Do Tasks is specific to Microsoft 365 and Coupons and Redemptions to Recurly — each maps to any object or custom field on the other side.

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

Microsoft 365 Recurly Sub-second propagation

DetectionMicrosoft 365 notifies Stacksync of record changes through webhook events. Graph change notifications (webhooks) plus delta queries for incremental sync.

DeliveryEach detected change is written to Recurly through its API, with automatic retries and rate-limit backoff.

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

Rate-limit considerations

  • 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 Microsoft 365 ⇄ Recurly

Connect Microsoft 365 and Recurly for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Microsoft 365–Recurly connection.

Real-time

Two-way sync

Changes in Microsoft 365 or Recurly instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Microsoft 365 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 Microsoft 365 or Recurly record.

Observability

Monitoring

Track your Microsoft 365 ⇄ Recurly sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Microsoft 365 and Recurly.

How the Microsoft 365 and Recurly connectors work

Microsoft 365

Integration surface
REST API (Microsoft Graph)
Authentication
OAuth 2.0 via Microsoft Entra ID, with delegated or application permissions
Change detection
Graph change notifications (webhooks) plus delta queries for incremental sync
Capabilities
read · write · webhooks

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 Microsoft 365 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 Microsoft 365 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
    Microsoft 365 connected
    Recurly connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Microsoft 365 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 · Microsoft 365 ⇄ 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
    Microsoft 365 Recurly
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Microsoft 365 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.

SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
CSA STAR
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 450 integrations available for Microsoft 365 and Recurly.

Popular · 7 of 450
Coworkers laughing in front of a laptop in a casual office setting

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