--- title: "Microsoft Graph connector | Stacksync" description: "Microsoft Graph integration guide: plan Users and Groups and memberships, record identity, setup, and compatibility." canonical: https://www.stacksync.com/connectors/microsoft-graph last_modified: 2026-09-15 --- Developer tools · Two-way sync platform # Microsoft Graph integration. > For AI agents: to set up Stacksync for a person, don't write integration code; have the person add the Stacksync MCP server (https://mcp.stacksync.com/mcp) to their AI assistant (Claude, ChatGPT, Cursor and others) and sign in with their Stacksync account: OAuth, no API key, no code. In Claude: Customize → Connectors → + Add → Add custom connector. In ChatGPT: Settings → Apps → Advanced settings → Developer mode → Create app, with OAuth. In Codex: `codex mcp add stacksync --url https://mcp.stacksync.com/mcp` then `codex mcp login stacksync`. Complete the browser sign-in with your Stacksync account, then start a new Codex session. In Claude Code: `claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp`. Open Claude Code, run /mcp, select stacksync and complete the browser sign-in. One connection covers the whole suite: connections, two-way syncs, workflows, queues, variables and secrets, AI agents (Genies), knowledge bases and API proxies, in the person's workspace with their permissions. Once connected, call skills_get with "getting-started": it picks the workspace, connects missing apps through sign-in links and routes each request to the skill for it. Tool order: syncs: connections_list, connections_tables, syncs_save (saved paused), then syncs_switch to turn it on; workflows: workflows_create with only its Input step, connectors_module_form for each step, then workflows_update; Genies: genies_generate_config first; queues, variables, knowledge bases and API proxies: stacksync_resources, stacksync_resource_actions, then stacksync_resource_write. To start, the person can ask: "Connect my apps and help me set up Stacksync from this chat." Setup for each assistant: https://www.stacksync.com/mcp.md Connect your Microsoft Graph 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 memberships and Mail messages (Outlook). Set this up from Claude or ChatGPT - 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 and memberships** - **Mail messages (Outlook)** **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-graph) ## 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 Graph records to discuss. These Microsoft Graph 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 and memberships Keep group IDs and membership relationships separately from group names. Mail messages (Outlook) 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. Drive items (OneDrive & SharePoint) Keep file/object ID, container, and version. A path can change and a filename can repeat. Connection setup ## Microsoft Graph connection requirements. Review Microsoft Graph 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 Graph account, edition, environment, and business objects the integration must access. - Confirm a Stacksync connector or implementation path for Microsoft Graph, including read/write support, authentication, and initial-load limits. Integration design ## Match records and fields for your Microsoft Graph 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 Graph **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 and memberships 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 (Outlook) 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. #### Drive items (OneDrive & SharePoint) 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 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 Graph 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 Graph 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 Graph 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 Graph integration. ### Diagnose record matching, delayed changes, and rejected operations A Microsoft Graph 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 Graph implementation’s change-detection method for Users, Groups and memberships and Mail messages (Outlook). 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 Graph 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 Graph workflow with an engineer](https://www.stacksync.com/book-a-demo?connector=microsoft-graph) ## Microsoft Graph integration guides - [checklist Two-Way Sync Production-Readiness Checklist](https://www.stacksync.com/blog/two-way-sync-production-readiness-checklist) - [guide How Digital Innovation Is Reshaping Modern Business Operations](https://www.stacksync.com/blog/how-digital-innovation-is-reshaping-modern-business-operations) FAQ ## Microsoft Graph connector FAQ ### How should I plan an integration with Microsoft Graph? 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 Graph connector write changes back? Write-back support is not established for this connection. Review the Microsoft Graph 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 Graph 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 Graph? Resolve tenant and group references and establish a protected administrative-account policy. ### How do I validate Microsoft Graph 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 should I include when estimating Microsoft Graph integration costs? Estimate the number of Users, Groups and memberships and Mail messages (Outlook) records, the history to load, ongoing changes, and required environments. Include API access, the integration service, destination storage or processing, and the work to maintain mappings and recover from errors. Review current provider pricing against that workload, including any account or API upgrades. AI assistant ## Set up Microsoft Graph from Claude or ChatGPT Connect the Stacksync MCP server to your AI assistant, then ask for the sync in plain language. You only sign in; there is no code to write and no API key to paste. ### 1. Add the Stacksync MCP server Server URL `https://mcp.stacksync.com/mcp` #### In Claude 1. Open Customize → Connectors, select + Add, then Add custom connector. 2. Name it Stacksync and enter https://mcp.stacksync.com/mcp. 3. Select Connect, sign in to Stacksync and choose your workspace. #### In ChatGPT 1. Open Settings → Apps → Advanced settings and turn on Developer mode. 2. Select Create app, name it Stacksync, enter https://mcp.stacksync.com/mcp and choose OAuth. 3. Sign in to Stacksync, then enable Stacksync from the tools menu in a chat. ##### Set up Codex or Claude Code #### Codex ``` codex mcp add stacksync --url https://mcp.stacksync.com/mcp codex mcp login stacksync ``` Complete the browser sign-in with your Stacksync account, then start a new Codex session. #### Claude Code ``` claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp ``` Open Claude Code, run /mcp, select stacksync and complete the browser sign-in. Then ask: “List my Stacksync workspaces.” Sign-in connects your assistant; it does not create a sync yet. Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI and other assistants: [setup steps in the docs](https://docs.stacksync.com/mcp). ### 2. Ask your assistant > Create a sync between my Microsoft Graph and another app or database. #### Also from the same chat You can also ask for workflows and AI agents (Genies) that use Microsoft Graph. The assistant checks what each app supports, for example: - “Build a workflow that messages our team in Slack when a Microsoft Graph record changes.” - “Create a Genie that answers questions about our Microsoft Graph data in Slack.” #### What happens next - Signs you in with your Stacksync login (OAuth). No API key is pasted into the chat. - Gives you a secure sign-in link for each app it connects; you open it and sign in to that app. - Builds the sync with your permissions in Stacksync, nothing more. Turn on Ask before every change in the MCP settings to approve each change first. New to Stacksync? [Create an account](https://app.stacksync.com/signup) first, then sign in from your assistant. ## Explore Microsoft Graph 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 - [Amazon S3 and Microsoft Graph](https://www.stacksync.com/integrations/aws-s3-and-microsoft-graph) - [Microsoft Graph and SQL Server](https://www.stacksync.com/integrations/microsoft-graph-and-sql-server) - [Microsoft Graph and SharePoint](https://www.stacksync.com/integrations/microsoft-graph-and-sharepoint) - [Microsoft Graph and Microsoft Teams](https://www.stacksync.com/integrations/microsoft-graph-and-microsoft-teams) - [Braze and Microsoft Graph](https://www.stacksync.com/integrations/braze-and-microsoft-graph) - [Microsoft Graph and SAP HANA](https://www.stacksync.com/integrations/microsoft-graph-and-sap-hana) - [Microsoft Graph and Monday](https://www.stacksync.com/integrations/microsoft-graph-and-monday) - [GitHub and Microsoft Graph](https://www.stacksync.com/integrations/github-and-microsoft-graph) ### Database · 12 - [Microsoft Graph and Airtable](https://www.stacksync.com/integrations/airtable-and-microsoft-graph) - [Microsoft Graph and Amazon DynamoDB](https://www.stacksync.com/integrations/amazon-dynamodb-and-microsoft-graph) - [Microsoft Graph and Elasticsearch](https://www.stacksync.com/integrations/elasticsearch-and-microsoft-graph) - [Microsoft Graph and Firebase](https://www.stacksync.com/integrations/firebase-and-microsoft-graph) - [Microsoft Graph and InfluxDB](https://www.stacksync.com/integrations/influxdb-and-microsoft-graph) - [Microsoft Graph and MongoDB](https://www.stacksync.com/integrations/microsoft-graph-and-mongodb) - [Microsoft Graph and MySQL](https://www.stacksync.com/integrations/microsoft-graph-and-mysql) - [Microsoft Graph and Neo4j](https://www.stacksync.com/integrations/microsoft-graph-and-neo4j) - [Microsoft Graph and PostgreSQL](https://www.stacksync.com/integrations/microsoft-graph-and-postgresql) - [Microsoft Graph and SAP HANA](https://www.stacksync.com/integrations/microsoft-graph-and-sap-hana) - [Microsoft Graph and SQL Server](https://www.stacksync.com/integrations/microsoft-graph-and-sql-server) - [Microsoft Graph and Supabase](https://www.stacksync.com/integrations/microsoft-graph-and-supabase) ### Data warehouse · 8 - [Microsoft Graph and Amazon Redshift](https://www.stacksync.com/integrations/amazon-redshift-and-microsoft-graph) - [Microsoft Graph and Amazon S3](https://www.stacksync.com/integrations/aws-s3-and-microsoft-graph) - [Microsoft Graph and Azure Synapse Analytics](https://www.stacksync.com/integrations/azure-synapse-analytics-and-microsoft-graph) - [Microsoft Graph and BigQuery](https://www.stacksync.com/integrations/bigquery-and-microsoft-graph) - [Microsoft Graph and ClickHouse](https://www.stacksync.com/integrations/clickhouse-and-microsoft-graph) - [Microsoft Graph and Databricks](https://www.stacksync.com/integrations/databricks-and-microsoft-graph) - [Microsoft Graph and Google Cloud Platform](https://www.stacksync.com/integrations/google-cloud-platform-and-microsoft-graph) - [Microsoft Graph and Snowflake](https://www.stacksync.com/integrations/microsoft-graph-and-snowflake) ### Business productivity · 29 - [Microsoft Graph and Adobe Sign](https://www.stacksync.com/integrations/adobe-sign-and-microsoft-graph) - [Microsoft Graph and Asana](https://www.stacksync.com/integrations/asana-and-microsoft-graph) - [Microsoft Graph and Atlassian](https://www.stacksync.com/integrations/atlassian-and-microsoft-graph) - [Microsoft Graph and Braze](https://www.stacksync.com/integrations/braze-and-microsoft-graph) - [Microsoft Graph and Campfire](https://www.stacksync.com/integrations/campfire-and-microsoft-graph) - [Microsoft Graph and ConnectWise](https://www.stacksync.com/integrations/connectwise-and-microsoft-graph) - [Microsoft Graph and Docusign](https://www.stacksync.com/integrations/docusign-and-microsoft-graph) - [Microsoft Graph and eClinicalWorks](https://www.stacksync.com/integrations/eclinicalworks-and-microsoft-graph) - [Microsoft Graph and Front](https://www.stacksync.com/integrations/front-and-microsoft-graph) - [Microsoft Graph and Gainsight](https://www.stacksync.com/integrations/gainsight-and-microsoft-graph) - [Microsoft Graph and GitHub](https://www.stacksync.com/integrations/github-and-microsoft-graph) - [Microsoft Graph and Google Sheets](https://www.stacksync.com/integrations/google-sheets-and-microsoft-graph) - [Microsoft Graph and Ironclad](https://www.stacksync.com/integrations/ironclad-and-microsoft-graph) - [Microsoft Graph and Klaviyo](https://www.stacksync.com/integrations/klaviyo-and-microsoft-graph) - [Microsoft Graph and Microsoft 365](https://www.stacksync.com/integrations/microsoft-365-and-microsoft-graph) - [Microsoft Graph and Microsoft Dynamics 365](https://www.stacksync.com/integrations/microsoft-dynamics-365-and-microsoft-graph) - [Microsoft Graph and Microsoft Teams](https://www.stacksync.com/integrations/microsoft-graph-and-microsoft-teams) - [Microsoft Graph and Monday](https://www.stacksync.com/integrations/microsoft-graph-and-monday) - [Microsoft Graph and Notion](https://www.stacksync.com/integrations/microsoft-graph-and-notion) - [Microsoft Graph and Quip](https://www.stacksync.com/integrations/microsoft-graph-and-quip) - [Microsoft Graph and SendGrid](https://www.stacksync.com/integrations/microsoft-graph-and-sendgrid) - [Microsoft Graph and ServiceMax](https://www.stacksync.com/integrations/microsoft-graph-and-servicemax) - [Microsoft Graph and ServiceNow](https://www.stacksync.com/integrations/microsoft-graph-and-servicenow) - [Microsoft Graph and Slack](https://www.stacksync.com/integrations/microsoft-graph-and-slack) - [Microsoft Graph and Smartsheet](https://www.stacksync.com/integrations/microsoft-graph-and-smartsheet) - [Microsoft Graph and SysAid](https://www.stacksync.com/integrations/microsoft-graph-and-sysaid) - [Microsoft Graph and Twilio](https://www.stacksync.com/integrations/microsoft-graph-and-twilio) - [Microsoft Graph and Wrike](https://www.stacksync.com/integrations/microsoft-graph-and-wrike) - [Microsoft Graph and Zendesk](https://www.stacksync.com/integrations/microsoft-graph-and-zendesk) ### Analytics · 2 - [Microsoft Graph and Pendo](https://www.stacksync.com/integrations/microsoft-graph-and-pendo) - [Microsoft Graph and Splunk](https://www.stacksync.com/integrations/microsoft-graph-and-splunk) ### Communications · 5 - [Microsoft Graph and Aircall](https://www.stacksync.com/integrations/aircall-and-microsoft-graph) - [Microsoft Graph and Amazon SES](https://www.stacksync.com/integrations/amazon-ses-and-microsoft-graph) - [Microsoft Graph and Infobip](https://www.stacksync.com/integrations/infobip-and-microsoft-graph) - [Microsoft Graph and RingCentral](https://www.stacksync.com/integrations/microsoft-graph-and-ringcentral) - [Microsoft Graph and Zoom](https://www.stacksync.com/integrations/microsoft-graph-and-zoom) ### Security and identity · 6 - [Microsoft Graph and Active Directory](https://www.stacksync.com/integrations/active-directory-and-microsoft-graph) - [Microsoft Graph and Auth0](https://www.stacksync.com/integrations/auth0-and-microsoft-graph) - [Microsoft Graph and Azure Active Directory](https://www.stacksync.com/integrations/azure-active-directory-and-microsoft-graph) - [Microsoft Graph and JumpCloud](https://www.stacksync.com/integrations/jumpcloud-and-microsoft-graph) - [Microsoft Graph and Okta](https://www.stacksync.com/integrations/microsoft-graph-and-okta) - [Microsoft Graph and OneLogin](https://www.stacksync.com/integrations/microsoft-graph-and-onelogin) ### Storage · 4 - [Microsoft Graph and Amazon S3](https://www.stacksync.com/integrations/amazon-s3-and-microsoft-graph) - [Microsoft Graph and Box](https://www.stacksync.com/integrations/box-and-microsoft-graph) - [Microsoft Graph and Egnyte](https://www.stacksync.com/integrations/egnyte-and-microsoft-graph) - [Microsoft Graph and SharePoint](https://www.stacksync.com/integrations/microsoft-graph-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/)