Real-time
Two-way sync
Changes in Gong or Microsoft 365 instantly reflect in both systems. No stale data, no manual imports.
CRM ⇄ Business productivity
Gong to Microsoft 365 integration — real-time, two-way sync
Keep Gong 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 Gong and Microsoft 365
Sync what happens in Microsoft 365 with the customer records in Gong, 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 Planner & To Do Tasks, Users, Groups, Mail Messages in Microsoft 365 to Interaction Stats (Activity), Trackers & Scorecards, CRM Objects, Library in Gong with bi-directional, real-time sync. Activity and record changes in Microsoft 365 update the matching contact or account in Gong, and CRM data flows the other way wherever Microsoft 365 can store and use it.
Common use cases
- 01 Keep CRM contacts and Microsoft 365 contacts aligned in both directions.
- 02 Sync employee records from an HR system into Entra ID users and group memberships.
- 03 Submit data-privacy erase-data-for-email requests to Gong to fulfill GDPR/CCPA deletion across recorded conversations.
- 04 Pull call Transcripts by callId into a warehouse or vector store to power search, RAG, and deal-review summaries over what was said on calls.
Common sync patterns
Where Microsoft 365 supplies contact or company data
Enriched fields land directly on records in Gong, and refreshes keep them from going stale.
Where Microsoft 365 processes payments
Charges, refunds, and subscription changes appear on the account in Gong, so revenue context lives with the relationship.
Where Microsoft 365 can store CRM context: fields kept current
Owner, lifecycle stage, or account details from Gong sync into Microsoft 365, so people working there have the context without switching tools.
What you can sync between Gong 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.
| Gong objects | Microsoft 365 objects | How this pairing syncs | |
|---|---|---|---|
| Users Gong users and team members with roles, titles, email, and settings, read via GET /v2/users to map call owners and participants to CRM and warehouse identities. Read-only. | 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. | |
| Calls Retrieved via POST /v2/calls/extensive with participants, topics, trackers, scorecards, and media URLs, filtered by fromDateTime/toDateTime; external recordings are also imported via POST /v2/calls with media uploaded via PUT /v2/calls/{id}/media. Read and write. | Mail Messages Exchange Online messages read for logging, archiving, or activity capture. | Calls is specific to Gong and Mail Messages to Microsoft 365 — each maps to any object or custom field on the other side. | |
| Transcripts Speaker-attributed, timestamped sentences retrieved via POST /v2/calls/transcript for one or more callIds; available only after asynchronous processing completes. Read-only. | Calendar Events Events synced with scheduling tools and CRMs for meeting visibility. | Transcripts is specific to Gong and Calendar Events to Microsoft 365 — each maps to any object or custom field on the other side. | |
| Interaction Stats (Activity) Aggregated talk/listen ratios, interaction stats, and day-by-day user activity retrieved via POST /v2/stats endpoints; read out for coaching and engagement reporting. Read-only. | Contacts Personal and org contacts kept consistent with CRM contact records. | Interaction Stats (Activity) is specific to Gong and Contacts to Microsoft 365 — each maps to any object or custom field on the other side. | |
| Trackers & Scorecards Keyword and topic tracker definitions plus coaching scorecards, including answered scorecards, read from Settings as coaching and deal-risk signals. Read-only. | OneDrive Files (driveItems) File and folder metadata synced for document workflows and audits. | Trackers & Scorecards is specific to Gong and OneDrive Files (driveItems) to Microsoft 365 — each maps to any object or custom field on the other side. | |
| CRM Objects Accounts, opportunities, stages, and users uploaded into Gong through the CRM integration API so CRM context appears alongside conversations. Write (upload) path. | SharePoint Sites & Lists List items read and written like lightweight database tables. | CRM Objects is specific to Gong and SharePoint Sites & Lists to Microsoft 365 — each maps to any object or custom field on the other side. |
How changes propagate between Gong 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.
Gong Microsoft 365 Interval-based propagation
DetectionStacksync polls Gong for changes on an incremental schedule, reading only records changed since the previous pass. Polling POST /v2/calls/extensive on fromDateTime/toDateTime.
DeliveryEach detected change is written to Microsoft 365 through its API, with automatic retries and rate-limit backoff.
Microsoft 365 Gong 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 Gong through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Gong: 3 API calls per second and 10,000 calls per day per company by default; exceeding returns HTTP 429 with a Retry-After header, and limits can be raised by contacting Gong.
What ships with Gong ⇄ Microsoft 365
Connect Gong and Microsoft 365 for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Gong–Microsoft 365 connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Gong 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 Gong or Microsoft 365 record.
Observability
Monitoring
Track your Gong ⇄ 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 Gong and Microsoft 365.
How the Gong and Microsoft 365 connectors work
Gong
- Integration surface
- REST API on api.gong.io/v2 - retrieval endpoints (calls, transcript, users, stats, settings, library, logs) plus write endpoints for importing calls, uploading CRM data, and data-privacy erasure
- Authentication
- Basic authorization header combining an Access Key and Access Key Secret (created by a Gong technical admin, base64-encoded as key:secret); OAuth 2.0 Bearer tokens are supported for marketplace apps
- Change detection
- Polling POST /v2/calls/extensive on fromDateTime/toDateTime; the public API exposes no outbound webhooks or CDC, though a Gong admin can configure a product-side automation Rule that POSTs matching calls to a URL. Transcripts and analysis appear only after asynchronous processing.
- Capabilities
- read · write
- Rate limits
- 3 API calls per second and 10,000 calls per day per company by default; exceeding returns HTTP 429 with a Retry-After header, and limits can be raised by contacting Gong.
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 Gong 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.
- 01
Connect your apps
Authenticate Gong 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.
Gong
connected
Microsoft 365
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Gong 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.
objects · Gong ⇄ Microsoft 365Customers 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.
Gong Microsoft 365Company company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Gong and Microsoft 365 integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Gong and Microsoft 365: authenticate both systems, choose the objects to sync (such as Gong's Users and Calls), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Common patterns for Gong and Microsoft 365: Where Microsoft 365 supplies contact or company data; Where Microsoft 365 processes payments; Where Microsoft 365 can store CRM context: fields kept current. Enriched fields land directly on records in Gong, and refreshes keep them from going stale.
-
Gong: REST API on api.gong.io/v2 - retrieval endpoints (calls, transcript, users, stats, settings, library, logs) plus write endpoints for importing calls, uploading CRM data, and data-privacy erasure. Authentication: Basic authorization header combining an Access Key and Access Key Secret (created by a Gong technical admin, base64-encoded as key:secret); OAuth 2.0 Bearer tokens are supported for marketplace apps. Microsoft 365: REST API (Microsoft Graph). Authentication: OAuth 2.0 via Microsoft Entra ID, with delegated or application permissions. Stacksync manages authentication, retries, and rate limits on both sides.
-
Microsoft 365: Nearly all Microsoft 365 workloads (Exchange, SharePoint, OneDrive, Teams, Entra ID) are exposed through the single Microsoft Graph endpoint rather than per-product APIs. Gong: Transcript retrieval is a POST to /v2/calls/transcript that accepts callIds and returns speaker-attributed, timestamped sentences only for calls that have finished processing. Stacksync's field mapping accounts for these differences between Gong and Microsoft 365 without custom code.
-
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Gong and Microsoft 365 records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Gong and Microsoft 365 connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Gong–Microsoft 365 integration in-house.
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 478 integrations available for Gong and Microsoft 365.
Popular · 7 of 478
-
Gong ⇄ Sysaid -
Gong ⇄ Wrike -
Gong ⇄ Zendesk -
Gong ⇄ Campfire -
Microsoft 365 ⇄ Oracle CX Sales -
Microsoft 365 ⇄ Outreach -
Microsoft 365 ⇄ Salesloft
No integrations match .
