Real-time
Two-way sync
Changes in Microsoft 365 or Pigment instantly reflect in both systems. No stale data, no manual imports.
Business productivity ⇄ Accounting and finance
Microsoft 365 to Pigment integration — real-time, two-way sync
Keep Microsoft 365 and Pigment 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 Pigment
Connect the financial records in Pigment with the work happening in Microsoft 365, so both stay current without exports or copy-paste.
Pigment 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 Applications, Metrics, Dimension lists, Tables in Pigment and Groups, Mail Messages, Calendar Events, Contacts in Microsoft 365 in sync, bi-directionally and in real time. Whatever records Microsoft 365 keeps and whatever events it produces, the overlap with Pigment 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
- Keep dimension lists such as departments and cost centers consistent with master data in the ERP.
- Sync headcount and compensation data from an HRIS into workforce planning models.
- Keep CRM contacts and Microsoft 365 contacts aligned in both directions.
- Sync employee records from an HR system into Entra ID users and group memberships.
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 Pigment next to the customer they are helping, without logging into the finance system.
Where Microsoft 365 collects payments or triggers charges: events land in Pigment
Payment and charge activity flows into Pigment as it happens, so the books reflect reality without manual reconciliation.
What you can sync between Microsoft 365 and Pigment
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 | Pigment objects | |
|---|---|---|
| Teams Team and membership data provisioned from upstream systems. | Tables Row-based transactional data loaded into models from source systems | |
| Planner & To Do Tasks Task items synced with project and work-management tools. | Scenarios Versions such as budget, forecast, and actuals that give exported figures their context | |
| Users Entra ID user accounts synced with HR and identity systems. | Data imports Scheduled loads that bring actuals from ERPs, CRMs, and HRIS into the model | |
| Groups Microsoft 365 and security groups kept aligned with org structure and access rules. | Users and permissions Access controls governing which model areas a sync can touch | |
| Mail Messages Exchange Online messages read for logging, archiving, or activity capture. | Applications Planning models organized by domain such as finance, sales, or workforce | |
| Calendar Events Events synced with scheduling tools and CRMs for meeting visibility. | Metrics Multidimensional values holding plans and actuals; the main target for inbound data |
What ships with Microsoft 365 ⇄ Pigment
Connect Microsoft 365 and Pigment for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Microsoft 365–Pigment connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Microsoft 365 or Pigment 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 Pigment record.
Observability
Monitoring
Track your Microsoft 365 ⇄ Pigment 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 Pigment.
How the Microsoft 365 and Pigment 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
Pigment
- Integration surface
- REST-based import and export API
- Authentication
- API keys, issued separately for import and export
- Change detection
- no change feed; syncs run scheduled imports and exports
- Capabilities
- read · write
- Rate limits
- subject to the platform's API rate limits
How it works
How to connect Microsoft 365 to Pigment — 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 Microsoft 365 and Pigment with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Microsoft 365
connected
Pigment
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Microsoft 365 and Pigment 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 · Microsoft 365 ⇄ PigmentCustomers 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.
Microsoft 365 PigmentCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Microsoft 365 and Pigment integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Microsoft 365 and Pigment: authenticate both systems, choose the objects to sync (such as Microsoft 365's Teams and Planner & To Do Tasks), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Change detection on Microsoft 365: Graph change notifications (webhooks) plus delta queries for incremental sync. On Pigment: No change feed; syncs run scheduled imports and exports. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Pigment side: Applications, Metrics, Dimension lists, Tables, plus custom fields where Pigment exposes them. On the Microsoft 365 side: Groups, Mail Messages, Calendar Events, Contacts. 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 Microsoft 365 and Pigment: Where Microsoft 365 tracks people or companies: one identity; Where Microsoft 365 handles customer conversations: billing context in view; Where Microsoft 365 collects payments or triggers charges: events land in Pigment. 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.
-
Microsoft 365: REST API (Microsoft Graph). Authentication: OAuth 2.0 via Microsoft Entra ID, with delegated or application permissions. Pigment: REST-based import and export API. Authentication: API keys, issued separately for import and export. Stacksync manages authentication, retries, and rate limits on both sides.
SECURITY
Security teams love 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 386 integrations available for Microsoft 365 and Pigment.
Popular · 8 of 386
-
Microsoft 365 ⇄ Rillet -
Microsoft 365 ⇄ Workday -
Microsoft 365 ⇄ Anaplan -
Microsoft 365 ⇄ Chargebee -
Pigment ⇄ SendGrid -
Pigment ⇄ Twilio -
Pigment ⇄ GitHub -
Pigment ⇄ Atlassian
No integrations match .
