--- title: "Microsoft 365 connector: setup and compatibility | Stacksync" description: "Microsoft 365 integration guide: plan Users and Groups, record identity, setup, and compatibility." canonical: https://www.stacksync.com/connectors/microsoft-365 last_modified: 2026-09-15 --- Business productivity · Two-way sync platform # Microsoft 365 integration. Connect your Microsoft 365 workflow to the systems your business runs on. Work with a Stacksync engineer to confirm the connection and required operations, starting with Users, Groups and Mail Messages. - Review your systems with an integration engineer - Get a scoped implementation and validation plan Technical workflow review ## Bring one workflow. Leave with a technical plan. An engineer will assess the required records, access method, and read/write operations before recommending an implementation. - **Users** - **Groups** - **Mail Messages** **What to bring** Bring a sample record, the other system, and the change your team needs to automate. [Talk through your workflow](https://www.stacksync.com/book-a-demo?connector=microsoft-365) ## Adopted by fast-scaling companies moving mission-critical data in real time - Gladia Case study - IDEXX - MedPro Migrated from MuleSoft - Eko Case study - Ubicloud - Vimeo - Codility Migrated from Celigo - ACERTUS Migrated from Heroku Connect - Syringa Migrated from Matillion - Truora - Streaam Case study - SEAL SQ - Rinsed Migrated from Fivetran - IA Capital Group Case study - Meter - Golden Pear Funding Migrated from Celigo Record types ## Microsoft 365 records to discuss. These Microsoft 365 record examples help scope a technical review. They are not a list of verified Stacksync operations. Users Use the immutable user ID within the tenant or directory. Do not equate an application user with a CRM customer contact. Groups Keep group IDs and membership relationships separately from group names. Mail Messages Retain message ID, conversation/thread ID, channel, and sender identity. ### See 3 more record examples Calendar Events Identify this record type and the operation you need to review with Stacksync. Contacts Use a stable person/contact ID and an explicit cross-system lookup. Email can change and can be shared, so treat it as a matching clue rather than a universal key. OneDrive Files (driveItems) Keep file/object ID, container, and version. A path can change and a filename can repeat. Connection setup ## Microsoft 365 connection requirements. Review Microsoft 365 access and the operations your workflow needs with Stacksync. The vendor API reference below can help your administrator prepare for that discussion. ### Prepare access and scope for the engineering review - Identify the Microsoft 365 account, edition, environment, and business objects the integration must access. - Confirm a Stacksync connector or implementation path for Microsoft 365, including read/write support, authentication, and initial-load limits. Integration design ## Match records and fields for your Microsoft 365 integration. Choose the object and business event that matter to the workflow. Separate record updates from side effects such as notifications, approvals, and file creation. Use these design questions to prepare a representative record and the business rules your integration must preserve. ### Explore record matching and field-mapping checks Microsoft 365 **Source record ID** Keep the account and record type Record matching **Source ID ↔ destination ID** Link the same record across systems Selected destination **Destination record ID** Preserve its local key and rules *Conceptual identity model. Keep source and destination IDs linked so an update reaches the right record. Confirm the supported sync direction separately.* Match the same record in both systems Use the immutable user ID within the tenant or directory. Do not equate an application user with a CRM customer contact. Load related records in the right order Resolve tenant and group references and establish a protected administrative-account policy. ### Mapping checks by record type #### Users Confirm object support with Stacksync Identity Use the immutable user ID within the tenant or directory. Do not equate an application user with a CRM customer contact. Fields to consider Source user ID · Tenant reference · Account status · Group references Related records to resolve first Resolve tenant and group references and establish a protected administrative-account policy. Test before going live Test a renamed login, disabled account, missing group, and a user existing in two tenants. #### Groups Confirm object support with Stacksync Identity Keep group IDs and membership relationships separately from group names. Fields to consider Source group ID · Member references · Tenant reference · Group type Related records to resolve first Resolve user and tenant identities before membership changes. Test before going live Test removed membership, nested groups, and equal group names in different tenants. #### Mail Messages Confirm object support with Stacksync Identity Retain message ID, conversation/thread ID, channel, and sender identity. Fields to consider Source message ID · Thread reference · Delivery state · Timestamp · Related record ID Related records to resolve first Resolve conversation, participant, and customer context before associating messages. Test before going live Test a delivery-state change, repeated message, private conversation, and reply linked to the correct thread. #### Contacts Confirm object support with Stacksync Identity Use a stable person/contact ID and an explicit cross-system lookup. Email can change and can be shared, so treat it as a matching clue rather than a universal key. Fields to consider Source person ID · Display name · Email address · Organization reference · Consent state Related records to resolve first Resolve the organization relationship and any owner or consent references required by the destination. Test before going live Test an email change, two records sharing an email, and a person associated with multiple organizations. #### OneDrive Files (driveItems) Confirm object support with Stacksync Identity Keep file/object ID, container, and version. A path can change and a filename can repeat. Fields to consider Source file ID · Container reference · Version · Metadata · Access classification Related records to resolve first Resolve folder/container and parent-record references before attaching metadata. Test before going live Test a renamed file, a new version, a moved folder, and an access-restricted document. #### Planner & To Do Tasks Confirm object support with Stacksync Identity Use a stable task/work-item ID and preserve its project or parent-ticket reference. Fields to consider Source task ID · Parent reference · Assignee · Status · Due date Related records to resolve first Resolve project, user, and parent-item references before the task. Test before going live Test a reassignment, an unsupported status transition, a deleted parent, and a due date across time zones. [Download the field-mapping workbook (CSV)](https://www.stacksync.com/downloads/sync-planning/field-mapping-workbook.csv) to capture the actual API fields, matching keys, owners, and test results. Use it as you build with your team or a Stacksync engineer. Setup and validation ## Validate the Microsoft 365 integration in four steps. An update reaches the intended record, preserves its relationships, and performs each approved side effect once. ### View the four setup tests and expected results 1. ### Confirm the intended Microsoft 365 account and grant After confirming an implementation path, validate the selected access method with the intended account and environment. Check that the authorizing user can grant access to the selected objects; test reauthorization without changing the mapped record identity. **Expected result:** The connection reaches the intended account, and the integration owner can renew or revoke the grant through the agreed procedure. 2. ### Test record matching for Users Using the implementation established in the compatibility review, preserve the selected source ID and resolve the required references. Test a renamed login, disabled account, missing group, and a user existing in two tenants. **Expected result:** An update reaches the intended record, preserves its relationships, and performs each approved side effect once. 3. ### Test the operation your workflow needs Review one Microsoft 365 record with a Stacksync engineer. Confirm how it should reach the other system, how often it must update, and whether your workflow needs reads, creates, or updates. Test those operations before expanding the integration. **Expected result:** The selected operation is confirmed, addresses the intended record, and exposes rejected values for repair. 4. ### Test recovery and name the support owner For the confirmed implementation, interrupt a non-production transfer and restore access. Establish whether recovery uses the current source state or a stored historical event, and verify that repeated delivery preserves record identity. **Expected result:** The records have the expected current values, repeated delivery creates no duplicate business record, and your team knows who handles unresolved errors. [Use the production-readiness checklist](https://www.stacksync.com/blog/two-way-sync-production-readiness-checklist) to record test results, assign support owners, and agree on when to go live. Troubleshooting ## Troubleshoot your Microsoft 365 integration. ### Diagnose record matching, delayed changes, and rejected operations A Microsoft 365 record appears under the wrong destination record Use the immutable user ID within the tenant or directory. Do not equate an application user with a CRM customer contact. Resolve tenant and group references and establish a protected administrative-account policy. Repair the ID relationship before repeating the operation. The first load looks correct but later results differ Confirm the selected Microsoft 365 implementation’s change-detection method for Users, Groups and Mail Messages. Compare later changes with the original source rather than using a successful initial copy as evidence of ongoing capture. One operation succeeds while another is rejected Check the specific Microsoft 365 object, field permissions, required references, and allowed operation. A successful read does not establish that a create, update, deletion, or business action is available. [Review retry, replay, and recovery behavior](https://www.stacksync.com/blog/two-way-sync-error-handling-retries-replay) before repeating an operation that may already have succeeded. [Review your Microsoft 365 workflow with an engineer](https://www.stacksync.com/book-a-demo?connector=microsoft-365) ## Microsoft 365 integration guides - [checklist Two-Way Sync Production-Readiness Checklist](https://www.stacksync.com/blog/two-way-sync-production-readiness-checklist) - [guide Two-Way Sync Field Mapping Workbook](https://www.stacksync.com/blog/two-way-sync-field-mapping-workbook) FAQ ## Microsoft 365 connector FAQ ### How should I plan an integration with Microsoft 365? Choose the object and business event that matter to the workflow. Separate record updates from side effects such as notifications, approvals, and file creation. Confirm the connection and read/write operations with Stacksync. Start with one workflow, agree on which fields each system owns, then test initial data, later changes, and recovery before expanding. ### Can the Microsoft 365 connector write changes back? Write-back support is not established for this connection. Review the Microsoft 365 records and fields you need with a Stacksync engineer, then test the required operation with a representative record. ### Which identifiers should I preserve for Microsoft 365 data? Use the immutable user ID within the tenant or directory. Do not equate an application user with a CRM customer contact. ### Which related records should I load first for Microsoft 365? Resolve tenant and group references and establish a protected administrative-account policy. ### How do I validate Microsoft 365 changes after the initial load? Test a renamed login, disabled account, missing group, and a user existing in two tenants. An update reaches the intended record, preserves its relationships, and performs each approved side effect once. ### What will we cover in a Microsoft 365 integration demo? Start with one workflow and a sample record from Users, Groups and Mail Messages. We can review how to identify the record, connect related data, set the update direction, and test recovery. Include the person who owns the source system and anyone who will maintain the integration; you do not need a finished requirements document. ## Explore Microsoft 365 connections Choose the other system in your workflow. Each guide explains the connection options, available operations, field mapping, and setup checks for that pair. ### Start with these integration guides - [BambooHR and Microsoft 365](https://www.stacksync.com/integrations/bamboohr-and-microsoft-365) - [eClinicalWorks and Microsoft 365](https://www.stacksync.com/integrations/eclinicalworks-and-microsoft-365) - [Microsoft 365 and Salesforce](https://www.stacksync.com/integrations/microsoft-365-and-salesforce) - [Microsoft 365 and Slack](https://www.stacksync.com/integrations/microsoft-365-and-slack) - [Microsoft 365 and QuickBooks](https://www.stacksync.com/integrations/microsoft-365-and-quickbooks) - [Microsoft 365 and Odoo](https://www.stacksync.com/integrations/microsoft-365-and-odoo) - [Hibob and Microsoft 365](https://www.stacksync.com/integrations/hibob-and-microsoft-365) - [Microsoft 365 and Pigment](https://www.stacksync.com/integrations/microsoft-365-and-pigment) ### CRM · 41 - [Microsoft 365 and Affinity](https://www.stacksync.com/integrations/affinity-and-microsoft-365) - [Microsoft 365 and Apollo.io](https://www.stacksync.com/integrations/apollo-io-and-microsoft-365) - [Microsoft 365 and Attio](https://www.stacksync.com/integrations/attio-and-microsoft-365) - [Microsoft 365 and Chorusai](https://www.stacksync.com/integrations/chorusai-and-microsoft-365) - [Microsoft 365 and Clari](https://www.stacksync.com/integrations/clari-and-microsoft-365) - [Microsoft 365 and Close](https://www.stacksync.com/integrations/close-and-microsoft-365) - [Microsoft 365 and Copper CRM](https://www.stacksync.com/integrations/copper-crm-and-microsoft-365) - [Microsoft 365 and Creatio CRM](https://www.stacksync.com/integrations/creatio-crm-and-microsoft-365) - [Microsoft 365 and DealCloud](https://www.stacksync.com/integrations/dealcloud-and-microsoft-365) - [Microsoft 365 and Dun & Bradstreet](https://www.stacksync.com/integrations/dun-bradstreet-and-microsoft-365) - [Microsoft 365 and Folk CRM](https://www.stacksync.com/integrations/folk-crm-and-microsoft-365) - [Microsoft 365 and Freshsales](https://www.stacksync.com/integrations/freshsales-and-microsoft-365) - [Microsoft 365 and Freshworks CRM](https://www.stacksync.com/integrations/freshworks-crm-and-microsoft-365) - [Microsoft 365 and Gladly](https://www.stacksync.com/integrations/gladly-and-microsoft-365) - [Microsoft 365 and Gong](https://www.stacksync.com/integrations/gong-and-microsoft-365) - [Microsoft 365 and HubSpot](https://www.stacksync.com/integrations/hubspot-and-microsoft-365) - [Microsoft 365 and Infor CRM](https://www.stacksync.com/integrations/infor-crm-and-microsoft-365) - [Microsoft 365 and Insightly](https://www.stacksync.com/integrations/insightly-and-microsoft-365) - [Microsoft 365 and Intercom](https://www.stacksync.com/integrations/intercom-and-microsoft-365) - [Microsoft 365 and Kommo](https://www.stacksync.com/integrations/kommo-and-microsoft-365) - [Microsoft 365 and Kustomer](https://www.stacksync.com/integrations/kustomer-and-microsoft-365) - [Microsoft 365 and Microsoft Dynamics 365 Sales](https://www.stacksync.com/integrations/microsoft-365-and-microsoft-dynamics-365-sales) - [Microsoft 365 and Nimble](https://www.stacksync.com/integrations/microsoft-365-and-nimble) - [Microsoft 365 and Nutshell](https://www.stacksync.com/integrations/microsoft-365-and-nutshell) - [Microsoft 365 and Oracle CX Sales](https://www.stacksync.com/integrations/microsoft-365-and-oracle-cx-sales) - [Microsoft 365 and Outreach](https://www.stacksync.com/integrations/microsoft-365-and-outreach) - [Microsoft 365 and Pipedrive](https://www.stacksync.com/integrations/microsoft-365-and-pipedrive) - [Microsoft 365 and Salesforce](https://www.stacksync.com/integrations/microsoft-365-and-salesforce) - [Microsoft 365 and Salesloft](https://www.stacksync.com/integrations/microsoft-365-and-salesloft) - [Microsoft 365 and SAP Sales Cloud](https://www.stacksync.com/integrations/microsoft-365-and-sap-sales-cloud) - [Microsoft 365 and Seismic](https://www.stacksync.com/integrations/microsoft-365-and-seismic) - [Microsoft 365 and Streak CRM](https://www.stacksync.com/integrations/microsoft-365-and-streak-crm) - [Microsoft 365 and SugarCRM](https://www.stacksync.com/integrations/microsoft-365-and-sugarcrm) - [Microsoft 365 and Twenty CRM](https://www.stacksync.com/integrations/microsoft-365-and-twenty-crm) - [Microsoft 365 and Veeva CRM](https://www.stacksync.com/integrations/microsoft-365-and-veeva-crm) - [Microsoft 365 and Vitally](https://www.stacksync.com/integrations/microsoft-365-and-vitally) - [Microsoft 365 and Vtiger CRM](https://www.stacksync.com/integrations/microsoft-365-and-vtiger-crm) - [Microsoft 365 and Xactly](https://www.stacksync.com/integrations/microsoft-365-and-xactly) - [Microsoft 365 and Zoho CRM](https://www.stacksync.com/integrations/microsoft-365-and-zoho-crm) - [Microsoft 365 and Zoho SalesIQ](https://www.stacksync.com/integrations/microsoft-365-and-zoho-salesiq) - [Microsoft 365 and ZoomInfo](https://www.stacksync.com/integrations/microsoft-365-and-zoominfo) ### ERP · 20 - [Microsoft 365 and Acumatica](https://www.stacksync.com/integrations/acumatica-and-microsoft-365) - [Microsoft 365 and Deposco](https://www.stacksync.com/integrations/deposco-and-microsoft-365) - [Microsoft 365 and Dynamics 365 Business Central](https://www.stacksync.com/integrations/microsoft-365-and-microsoft-dynamics-365-business-central) - [Microsoft 365 and Epicor ERP](https://www.stacksync.com/integrations/epicor-erp-and-microsoft-365) - [Microsoft 365 and Infor LN](https://www.stacksync.com/integrations/infor-ln-and-microsoft-365) - [Microsoft 365 and Infor M3](https://www.stacksync.com/integrations/infor-m3-and-microsoft-365) - [Microsoft 365 and Infor WMS](https://www.stacksync.com/integrations/infor-wms-and-microsoft-365) - [Microsoft 365 and NetSuite](https://www.stacksync.com/integrations/microsoft-365-and-netsuite) - [Microsoft 365 and Odoo](https://www.stacksync.com/integrations/microsoft-365-and-odoo) - [Microsoft 365 and Oracle Fusion ERP](https://www.stacksync.com/integrations/microsoft-365-and-oracle-fusion-erp) - [Microsoft 365 and Sage 100](https://www.stacksync.com/integrations/microsoft-365-and-sage-100) - [Microsoft 365 and Sage 300](https://www.stacksync.com/integrations/microsoft-365-and-sage-300) - [Microsoft 365 and Sage Intacct](https://www.stacksync.com/integrations/microsoft-365-and-sage-intacct) - [Microsoft 365 and Sage X3](https://www.stacksync.com/integrations/microsoft-365-and-sage-x3) - [Microsoft 365 and SAP](https://www.stacksync.com/integrations/microsoft-365-and-sap) - [Microsoft 365 and SAP Business ByDesign](https://www.stacksync.com/integrations/microsoft-365-and-sap-business-bydesign) - [Microsoft 365 and SAP Business One](https://www.stacksync.com/integrations/microsoft-365-and-sap-business-one) - [Microsoft 365 and SAP S/4HANA](https://www.stacksync.com/integrations/microsoft-365-and-sap-s4hana) - [Microsoft 365 and Snapfulfil](https://www.stacksync.com/integrations/microsoft-365-and-snapfulfil) - [Microsoft 365 and Syspro](https://www.stacksync.com/integrations/microsoft-365-and-syspro) ### Database · 25 - [Microsoft 365 and Airtable](https://www.stacksync.com/integrations/airtable-and-microsoft-365) - [Microsoft 365 and Amazon DynamoDB](https://www.stacksync.com/integrations/dynamo-db-and-microsoft-365) - [Microsoft 365 and Amazon DynamoDB](https://www.stacksync.com/integrations/amazon-dynamodb-and-microsoft-365) - [Microsoft 365 and Amazon Lightsail](https://www.stacksync.com/integrations/amazon-lightsail-and-microsoft-365) - [Microsoft 365 and Amazon RDS](https://www.stacksync.com/integrations/amazon-rds-and-microsoft-365) - [Microsoft 365 and AWS Aurora PostgreSQL](https://www.stacksync.com/integrations/aws-aurora-postgresql-and-microsoft-365) - [Microsoft 365 and Azure Cosmos DB](https://www.stacksync.com/integrations/azure-cosmos-db-and-microsoft-365) - [Microsoft 365 and Azure SQL Database](https://www.stacksync.com/integrations/azure-sql-database-and-microsoft-365) - [Microsoft 365 and Citus](https://www.stacksync.com/integrations/citus-and-microsoft-365) - [Microsoft 365 and CockroachDB](https://www.stacksync.com/integrations/cockroachdb-and-microsoft-365) - [Microsoft 365 and Firebase](https://www.stacksync.com/integrations/firebase-and-microsoft-365) - [Microsoft 365 and IBM Db2](https://www.stacksync.com/integrations/ibm-db2-and-microsoft-365) - [Microsoft 365 and InterSystems IRIS](https://www.stacksync.com/integrations/intersystems-iris-and-microsoft-365) - [Microsoft 365 and JDBC](https://www.stacksync.com/integrations/jdbc-and-microsoft-365) - [Microsoft 365 and MariaDB](https://www.stacksync.com/integrations/mariadb-and-microsoft-365) - [Microsoft 365 and MongoDB](https://www.stacksync.com/integrations/microsoft-365-and-mongodb) - [Microsoft 365 and MySQL](https://www.stacksync.com/integrations/microsoft-365-and-mysql) - [Microsoft 365 and Oracle DB](https://www.stacksync.com/integrations/microsoft-365-and-oracle-db) - [Microsoft 365 and Postgres Heroku](https://www.stacksync.com/integrations/microsoft-365-and-postgres-heroku) - [Microsoft 365 and PostgreSQL](https://www.stacksync.com/integrations/microsoft-365-and-postgresql) - [Microsoft 365 and Reltio](https://www.stacksync.com/integrations/microsoft-365-and-reltio) - [Microsoft 365 and SAP HANA](https://www.stacksync.com/integrations/microsoft-365-and-sap-hana) - [Microsoft 365 and SingleStore](https://www.stacksync.com/integrations/microsoft-365-and-singlestore) - [Microsoft 365 and SQL Server](https://www.stacksync.com/integrations/microsoft-365-and-sql-server) - [Microsoft 365 and Supabase](https://www.stacksync.com/integrations/microsoft-365-and-supabase) ### Data warehouse · 29 - [Microsoft 365 and Amazon Redshift](https://www.stacksync.com/integrations/amazon-redshift-and-microsoft-365) - [Microsoft 365 and Amazon S3](https://www.stacksync.com/integrations/aws-s3-and-microsoft-365) - [Microsoft 365 and Apache Doris](https://www.stacksync.com/integrations/apache-doris-and-microsoft-365) - [Microsoft 365 and Apache Druid](https://www.stacksync.com/integrations/apache-druid-and-microsoft-365) - [Microsoft 365 and Apache Hive](https://www.stacksync.com/integrations/apache-hive-and-microsoft-365) - [Microsoft 365 and Apache Impala](https://www.stacksync.com/integrations/apache-impala-and-microsoft-365) - [Microsoft 365 and Apache Kylin](https://www.stacksync.com/integrations/apache-kylin-and-microsoft-365) - [Microsoft 365 and Apache Pinot](https://www.stacksync.com/integrations/apache-pinot-and-microsoft-365) - [Microsoft 365 and Azure Synapse Analytics](https://www.stacksync.com/integrations/azure-synapse-analytics-and-microsoft-365) - [Microsoft 365 and BigQuery](https://www.stacksync.com/integrations/bigquery-and-microsoft-365) - [Microsoft 365 and ClickHouse](https://www.stacksync.com/integrations/clickhouse-and-microsoft-365) - [Microsoft 365 and Cloudera Data Platform](https://www.stacksync.com/integrations/cloudera-data-platform-and-microsoft-365) - [Microsoft 365 and Databricks](https://www.stacksync.com/integrations/databricks-and-microsoft-365) - [Microsoft 365 and Dremio](https://www.stacksync.com/integrations/dremio-and-microsoft-365) - [Microsoft 365 and Exasol](https://www.stacksync.com/integrations/exasol-and-microsoft-365) - [Microsoft 365 and Firebolt](https://www.stacksync.com/integrations/firebolt-and-microsoft-365) - [Microsoft 365 and Google Cloud Platform](https://www.stacksync.com/integrations/google-cloud-platform-and-microsoft-365) - [Microsoft 365 and Greenplum](https://www.stacksync.com/integrations/greenplum-and-microsoft-365) - [Microsoft 365 and IBM Netezza](https://www.stacksync.com/integrations/ibm-netezza-and-microsoft-365) - [Microsoft 365 and Materialize](https://www.stacksync.com/integrations/materialize-and-microsoft-365) - [Microsoft 365 and MotherDuck](https://www.stacksync.com/integrations/microsoft-365-and-motherduck) - [Microsoft 365 and Rockset](https://www.stacksync.com/integrations/microsoft-365-and-rockset) - [Microsoft 365 and Snowflake](https://www.stacksync.com/integrations/microsoft-365-and-snowflake) - [Microsoft 365 and Starburst Enterprise](https://www.stacksync.com/integrations/microsoft-365-and-starburst-enterprise) - [Microsoft 365 and StarRocks](https://www.stacksync.com/integrations/microsoft-365-and-starrocks) - [Microsoft 365 and Teradata Vantage](https://www.stacksync.com/integrations/microsoft-365-and-teradata-vantage) - [Microsoft 365 and Tinybird](https://www.stacksync.com/integrations/microsoft-365-and-tinybird) - [Microsoft 365 and Vertica](https://www.stacksync.com/integrations/microsoft-365-and-vertica) - [Microsoft 365 and Yellowbrick](https://www.stacksync.com/integrations/microsoft-365-and-yellowbrick) ### Business productivity · 32 - [Microsoft 365 and Adobe Sign](https://www.stacksync.com/integrations/adobe-sign-and-microsoft-365) - [Microsoft 365 and Agiloft](https://www.stacksync.com/integrations/agiloft-and-microsoft-365) - [Microsoft 365 and Amazon Seller Central](https://www.stacksync.com/integrations/amazon-seller-central-and-microsoft-365) - [Microsoft 365 and Asana](https://www.stacksync.com/integrations/asana-and-microsoft-365) - [Microsoft 365 and Atlassian](https://www.stacksync.com/integrations/atlassian-and-microsoft-365) - [Microsoft 365 and Braze](https://www.stacksync.com/integrations/braze-and-microsoft-365) - [Microsoft 365 and Docusign](https://www.stacksync.com/integrations/docusign-and-microsoft-365) - [Microsoft 365 and eClinicalWorks](https://www.stacksync.com/integrations/eclinicalworks-and-microsoft-365) - [Microsoft 365 and Front](https://www.stacksync.com/integrations/front-and-microsoft-365) - [Microsoft 365 and FullEnrich](https://www.stacksync.com/integrations/full-enrich-and-microsoft-365) - [Microsoft 365 and Gainsight](https://www.stacksync.com/integrations/gainsight-and-microsoft-365) - [Microsoft 365 and Gatekeeper](https://www.stacksync.com/integrations/gatekeeper-and-microsoft-365) - [Microsoft 365 and GitHub](https://www.stacksync.com/integrations/github-and-microsoft-365) - [Microsoft 365 and Google Sheets](https://www.stacksync.com/integrations/google-sheets-and-microsoft-365) - [Microsoft 365 and Ironclad](https://www.stacksync.com/integrations/ironclad-and-microsoft-365) - [Microsoft 365 and Klaviyo](https://www.stacksync.com/integrations/klaviyo-and-microsoft-365) - [Microsoft 365 and Lemlist](https://www.stacksync.com/integrations/lemlist-and-microsoft-365) - [Microsoft 365 and Microsoft Dynamics 365](https://www.stacksync.com/integrations/microsoft-365-and-microsoft-dynamics-365) - [Microsoft 365 and Microsoft Teams](https://www.stacksync.com/integrations/microsoft-365-and-microsoft-teams) - [Microsoft 365 and Monday](https://www.stacksync.com/integrations/microsoft-365-and-monday) - [Microsoft 365 and Notion](https://www.stacksync.com/integrations/microsoft-365-and-notion) - [Microsoft 365 and Quip](https://www.stacksync.com/integrations/microsoft-365-and-quip) - [Microsoft 365 and Resend](https://www.stacksync.com/integrations/microsoft-365-and-resend) - [Microsoft 365 and SendGrid](https://www.stacksync.com/integrations/microsoft-365-and-sendgrid) - [Microsoft 365 and ServiceMax](https://www.stacksync.com/integrations/microsoft-365-and-servicemax) - [Microsoft 365 and ServiceNow](https://www.stacksync.com/integrations/microsoft-365-and-servicenow) - [Microsoft 365 and Slack](https://www.stacksync.com/integrations/microsoft-365-and-slack) - [Microsoft 365 and Smartsheet](https://www.stacksync.com/integrations/microsoft-365-and-smartsheet) - [Microsoft 365 and SysAid](https://www.stacksync.com/integrations/microsoft-365-and-sysaid) - [Microsoft 365 and Twilio](https://www.stacksync.com/integrations/microsoft-365-and-twilio) - [Microsoft 365 and Wrike](https://www.stacksync.com/integrations/microsoft-365-and-wrike) - [Microsoft 365 and Zendesk](https://www.stacksync.com/integrations/microsoft-365-and-zendesk) ### Accounting and finance · 15 - [Microsoft 365 and Adyen](https://www.stacksync.com/integrations/adyen-and-microsoft-365) - [Microsoft 365 and Anaplan](https://www.stacksync.com/integrations/anaplan-and-microsoft-365) - [Microsoft 365 and BILL](https://www.stacksync.com/integrations/bill-and-microsoft-365) - [Microsoft 365 and Braintree](https://www.stacksync.com/integrations/braintree-and-microsoft-365) - [Microsoft 365 and Chargebee](https://www.stacksync.com/integrations/chargebee-and-microsoft-365) - [Microsoft 365 and Coupa](https://www.stacksync.com/integrations/coupa-and-microsoft-365) - [Microsoft 365 and LogiSense](https://www.stacksync.com/integrations/logisense-and-microsoft-365) - [Microsoft 365 and Navan](https://www.stacksync.com/integrations/microsoft-365-and-navan) - [Microsoft 365 and Pigment](https://www.stacksync.com/integrations/microsoft-365-and-pigment) - [Microsoft 365 and QuickBooks](https://www.stacksync.com/integrations/microsoft-365-and-quickbooks) - [Microsoft 365 and Ramp](https://www.stacksync.com/integrations/microsoft-365-and-ramp) - [Microsoft 365 and Recurly](https://www.stacksync.com/integrations/microsoft-365-and-recurly) - [Microsoft 365 and Stripe](https://www.stacksync.com/integrations/microsoft-365-and-stripe) - [Microsoft 365 and Workday](https://www.stacksync.com/integrations/microsoft-365-and-workday) - [Microsoft 365 and Zuora](https://www.stacksync.com/integrations/microsoft-365-and-zuora) ### AI · 5 - [Microsoft 365 and Anthropic](https://www.stacksync.com/integrations/anthropic-and-microsoft-365) - [Microsoft 365 and Autopilot](https://www.stacksync.com/integrations/autopilot-and-microsoft-365) - [Microsoft 365 and Azure OpenAI](https://www.stacksync.com/integrations/azure-openai-and-microsoft-365) - [Microsoft 365 and OpenAI](https://www.stacksync.com/integrations/microsoft-365-and-openai) - [Microsoft 365 and Pinecone](https://www.stacksync.com/integrations/microsoft-365-and-pinecone) ### Communications · 1 - [Microsoft 365 and Gmail](https://www.stacksync.com/integrations/gmail-and-microsoft-365) ### Developer tools · 11 - [Microsoft 365 and Azure Service Bus](https://www.stacksync.com/integrations/azure-service-bus-and-microsoft-365) - [Microsoft 365 and Datadog](https://www.stacksync.com/integrations/datadog-and-microsoft-365) - [Microsoft 365 and Google Cloud Pub/Sub](https://www.stacksync.com/integrations/google-pubsub-and-microsoft-365) - [Microsoft 365 and Jira](https://www.stacksync.com/integrations/jira-and-microsoft-365) - [Microsoft 365 and JMS](https://www.stacksync.com/integrations/jms-and-microsoft-365) - [Microsoft 365 and LDAP](https://www.stacksync.com/integrations/ldap-and-microsoft-365) - [Microsoft 365 and Microsoft Graph](https://www.stacksync.com/integrations/microsoft-365-and-microsoft-graph) - [Microsoft 365 and New Relic](https://www.stacksync.com/integrations/microsoft-365-and-newrelic) - [Microsoft 365 and Opsgenie](https://www.stacksync.com/integrations/microsoft-365-and-opsgenie) - [Microsoft 365 and PagerDuty](https://www.stacksync.com/integrations/microsoft-365-and-pagerduty) - [Microsoft 365 and RabbitMQ](https://www.stacksync.com/integrations/microsoft-365-and-rabbitmq) ### Human resources · 14 - [Microsoft 365 and BambooHR](https://www.stacksync.com/integrations/bamboohr-and-microsoft-365) - [Microsoft 365 and Ceridian Dayforce](https://www.stacksync.com/integrations/ceridian-dayforce-and-microsoft-365) - [Microsoft 365 and D2L Brightspace](https://www.stacksync.com/integrations/d2l-brightspace-and-microsoft-365) - [Microsoft 365 and Greenhouse](https://www.stacksync.com/integrations/greenhouse-and-microsoft-365) - [Microsoft 365 and Hibob](https://www.stacksync.com/integrations/hibob-and-microsoft-365) - [Microsoft 365 and Jobvite](https://www.stacksync.com/integrations/jobvite-and-microsoft-365) - [Microsoft 365 and Lever](https://www.stacksync.com/integrations/lever-and-microsoft-365) - [Microsoft 365 and Namely](https://www.stacksync.com/integrations/microsoft-365-and-namely) - [Microsoft 365 and Oracle Fusion Cloud HCM](https://www.stacksync.com/integrations/microsoft-365-and-oracle-fusion-cloud-hcm) - [Microsoft 365 and Paylocity](https://www.stacksync.com/integrations/microsoft-365-and-paylocity) - [Microsoft 365 and SmartRecruiters](https://www.stacksync.com/integrations/microsoft-365-and-smartrecruiters) - [Microsoft 365 and Success Factors](https://www.stacksync.com/integrations/microsoft-365-and-success-factors) - [Microsoft 365 and UKG Pro](https://www.stacksync.com/integrations/microsoft-365-and-ukg-pro) - [Microsoft 365 and UKG Ready](https://www.stacksync.com/integrations/microsoft-365-and-ukg-ready) ### Security and identity · 6 - [Microsoft 365 and Active Directory](https://www.stacksync.com/integrations/active-directory-and-microsoft-365) - [Microsoft 365 and Auth0](https://www.stacksync.com/integrations/auth0-and-microsoft-365) - [Microsoft 365 and Azure Active Directory](https://www.stacksync.com/integrations/azure-active-directory-and-microsoft-365) - [Microsoft 365 and JumpCloud](https://www.stacksync.com/integrations/jumpcloud-and-microsoft-365) - [Microsoft 365 and Okta](https://www.stacksync.com/integrations/microsoft-365-and-okta) - [Microsoft 365 and OneLogin](https://www.stacksync.com/integrations/microsoft-365-and-onelogin) ### Storage · 4 - [Microsoft 365 and Amazon S3](https://www.stacksync.com/integrations/amazon-s3-and-microsoft-365) - [Microsoft 365 and Box](https://www.stacksync.com/integrations/box-and-microsoft-365) - [Microsoft 365 and Egnyte](https://www.stacksync.com/integrations/egnyte-and-microsoft-365) - [Microsoft 365 and SharePoint](https://www.stacksync.com/integrations/microsoft-365-and-sharepoint) 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](https://www.stacksync.com/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](https://www.stacksync.com/security) [SSH Tunnelling](https://docs.stacksync.com/two-way-sync/connectors/setup-options/ssh-tunneling) [SSL certificates](https://docs.stacksync.com/two-way-sync/connectors/postgres/authorize-postgres/amazon-rds/ensuring-secure-rds-connections-with-ssl-certificate) [IP Whitelisting](https://docs.stacksync.com/two-way-sync/connectors/setup-options/ip-whitelisting) [VPN gateway](https://docs.stacksync.com/two-way-sync/legal/service-consumption-tables#:~:text=%E2%9C%93-,VPN%20gateway,-%2D) [VPC peering](https://www.stacksync.com/security) and more ## Connect the systems your business runs on. Build your next workflow with Stacksync. [Book a demo](https://www.stacksync.com/book-a-demo) [Get started](https://app.stacksync.com/)