Skip to content
CRM ⇄ Business productivity

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

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

Sync what happens in Microsoft 365 with the customer records in Close, in real time and in both directions.

The CRM is supposed to be the record of every customer relationship, but customer-relevant information also accumulates in the other tools a team runs. Whatever Microsoft 365 holds or produces that touches a customer, whether conversations, payments, replies, enriched data, or notes, the CRM only benefits if it arrives without someone copying it over.

Stacksync connects Mail Messages, Calendar Events, Contacts, OneDrive Files (driveItems) in Microsoft 365 to Smart Views, Leads, Contacts, Opportunities in Close with bi-directional, real-time sync. Activity and record changes in Microsoft 365 update the matching contact or account in Close, and CRM data flows the other way wherever Microsoft 365 can store and use it.

Common use cases

  • 01 Archive mail and file metadata into a warehouse for compliance and activity analytics.
  • 02 Keep CRM contacts and Microsoft 365 contacts aligned in both directions.
  • 03 Write product usage or firmographic data from an internal database onto Close lead custom fields to prioritize follow-up.
  • 04 Sync Close leads and opportunities into Postgres or a warehouse for pipeline reporting outside Close's built-in reports.

Common sync patterns

Where Microsoft 365 can store CRM context: fields kept current

Owner, lifecycle stage, or account details from Close sync into Microsoft 365, so people working there have the context without switching tools.

Where Microsoft 365 supplies contact or company data

Enriched fields land directly on records in Close, and refreshes keep them from going stale.

Where Microsoft 365 processes payments

Charges, refunds, and subscription changes appear on the account in Close, so revenue context lives with the relationship.

What you can sync between Close and Microsoft 365

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.

Close objects Microsoft 365 objects How this pairing syncs
Contacts People nested under a lead, with emails and phone numbers used for outreach syncs. Contacts Personal and org contacts kept consistent with CRM contact records. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
Users Sales reps referenced as owners on leads, opportunities, and activities. Users Entra ID user accounts synced with HR and identity systems. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
Custom Fields Org-specific fields on leads, contacts, and opportunities; addressed by stable field ids in syncs. Calendar Events Events synced with scheduling tools and CRMs for meeting visibility. Custom Fields is specific to Close and Calendar Events to Microsoft 365 — each maps to any object or custom field on the other side.
Smart Views Saved lead searches that can scope which records a segment-based sync pulls. OneDrive Files (driveItems) File and folder metadata synced for document workflows and audits. Smart Views is specific to Close and OneDrive Files (driveItems) to Microsoft 365 — each maps to any object or custom field on the other side.
Leads The top-level record in Close; represents a company and holds its contacts, opportunities, and activity history. SharePoint Sites & Lists List items read and written like lightweight database tables. Leads is specific to Close and SharePoint Sites & Lists to Microsoft 365 — each maps to any object or custom field on the other side.
Opportunities Deal records with value, confidence, and status; commonly synced to reporting and billing systems. Teams Team and membership data provisioned from upstream systems. Opportunities is specific to Close and Teams to Microsoft 365 — each maps to any object or custom field on the other side.

How changes propagate between Close and Microsoft 365

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.

Close Microsoft 365 Sub-second propagation

DetectionClose notifies Stacksync of record changes through webhook events. Webhook subscriptions for record events, with polling on date_updated fields for backfills.

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

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

Rate-limit considerations

  • Close: Subject to per-endpoint rate limits communicated in response headers.
What ships with Close ⇄ Microsoft 365

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Close and Microsoft 365 connectors work

Close

Integration surface
REST API
Authentication
API key (sent via HTTP Basic auth)
Change detection
Webhook subscriptions for record events, with polling on date_updated fields for backfills
Capabilities
read · write · webhooks
Rate limits
Subject to per-endpoint rate limits communicated in response headers

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
How it works

How to connect Close to Microsoft 365 — 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 Close and Microsoft 365 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
    Close connected
    Microsoft 365 connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

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

Close and Microsoft 365 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
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:

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 478 integrations available for Close and Microsoft 365.

Popular · 8 of 478
All Close integrations All Microsoft 365 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