Skip to content
Developer tools ⇄ Database

Microsoft Graph to SAP Hana integration — real-time, two-way sync

Keep Microsoft Graph and SAP Hana 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 Graph and SAP Hana

Keep SAP Hana and Microsoft Graph in step: the rows in your database and the Teams messages and chats, Planner tasks, Users, Groups and memberships your engineering tools track stay consistent in real time, in both directions.

SAP Hana is where your application's durable data lives; Microsoft Graph is where engineering and operations teams track the issues, events, messages, or identities that run alongside it. The two overlap constantly, a row should open a ticket, an alert should land as a record, a user in one should exist in the other, but bridging them today means per-tool integration code: auth, webhooks, pagination, rate limits, and retries, built and maintained separately for every tool.

Stacksync syncs SQL views, Schemas, Sequences, Triggers in SAP Hana with Teams messages and chats, Planner tasks, Users, Groups and memberships in Microsoft Graph field by field, in real time, and in both directions. You decide which system owns which fields; Stacksync keeps every copy consistent and resolves conflicts by rules you set, so the database and the tooling around it never drift apart.

Common use cases

  • 01 Detect inserts, updates, and deletes on high-write tables via AFTER triggers or a last-modified column and replicate the deltas downstream near-real-time.
  • 02 Read SYS.TABLES and TABLE_COLUMNS system views to auto-discover schema and generate field mappings when new tables are added to the sync.
  • 03 Two-way sync Users and Groups between Microsoft Entra ID and an HRIS or Postgres so joiners, movers, and leavers provision and deprovision accounts and group memberships automatically.
  • 04 Sync Outlook Calendar events and Contacts two-way with a CRM so reps' meetings and the people they meet stay aligned across both systems.

Common sync patterns

Turn rows into the records your tools track

A new or changed row in SAP Hana creates or updates the matching record in Microsoft Graph, whether that is an issue, an event, a message, or a user, so the tool reflects the database without a custom API job.

Land tool activity as queryable rows

Records and events from Microsoft Graph arrive in SAP Hana as rows, so tickets, alerts, messages, or identity changes become joinable data your services and reports read directly.

One integration pattern instead of per-tool API code

Read and write the synced tables in SAP Hana and Stacksync keeps Microsoft Graph current, replacing the auth, webhooks, rate limits, and retry logic you would otherwise maintain for each tool.

What you can sync between Microsoft Graph and SAP Hana

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 Graph objects SAP Hana objects How this pairing syncs
Drive items (OneDrive & SharePoint) Files and folders via /drives and /me/drive; read and write items, upload and download content, and read per-item metadata. Column store tables HANA's default table type, optimized for analytics; synced two-way as rows over the SQL interface with the primary key driving upserts and delete tracking. Drive items (OneDrive & SharePoint) is specific to Microsoft Graph and Column store tables to SAP Hana — each maps to any object or custom field on the other side.
Teams messages and chats Channel messages and chats via /teams/{id}/channels and /chats; read message history and post new messages for alerts and archiving. Row store tables OLTP-oriented tables held fully in memory; read and written the same way through the SAP HANA client for high-write operational tables. Teams messages and chats is specific to Microsoft Graph and Row store tables to SAP Hana — each maps to any object or custom field on the other side.
Planner tasks Plans, buckets, and tasks via /planner; read and write task status, assignments, and due dates to keep project state in sync. Calculation views Modeled analytic views over base tables; read-only sources for pushing aggregated or joined results into a warehouse or downstream app. Planner tasks is specific to Microsoft Graph and Calculation views to SAP Hana — each maps to any object or custom field on the other side.
Users Entra ID user accounts read and written via /users; create, update profile attributes, and enable or disable accounts with User.ReadWrite.All. SQL views Standard database views; read-only projections synced outbound when the source data should not be exposed as raw base tables. Users is specific to Microsoft Graph and SQL views to SAP Hana — each maps to any object or custom field on the other side.
Groups and memberships Microsoft 365 and security groups via /groups; read and write name, owners, and add/remove members, with membership deltas surfaced by delta query. Schemas Namespaces that group tables and views; the connector targets a schema and enumerates its objects from the catalog to build the sync. Groups and memberships is specific to Microsoft Graph and Schemas to SAP Hana — each maps to any object or custom field on the other side.
Mail messages (Outlook) Messages via /users/{id}/messages; read and create drafts, update, and send with the sendMail action, so this surface is fully read-write. Sequences Server-generated key values; relevant when writing rows into tables whose identity is assigned HANA-side rather than by the source system. Mail messages (Outlook) is specific to Microsoft Graph and Sequences to SAP Hana — each maps to any object or custom field on the other side.

How changes propagate between Microsoft Graph and SAP Hana

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.

Microsoft Graph SAP Hana Sub-second propagation

DetectionMicrosoft Graph notifies Stacksync of record changes through webhook events. Delta query (change tracking) returns created, updated, and deleted items since the last deltaLink for users, groups, mail, events, contacts, and.

DeliveryEach detected change is applied to SAP Hana as a row-level write, with types converted between the two schemas.

SAP Hana Microsoft Graph Sub-second propagation

DetectionChanges in SAP Hana are captured at the source via change data capture — no polling loop against its API. Polling on a last-modified timestamp column, or AFTER INSERT/UPDATE/DELETE triggers writing to a shadow table.

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

Rate-limit considerations

  • Microsoft Graph: Throttled per app and per tenant, returning HTTP 429 with a Retry-After header; limits vary by service — the Outlook mail service allows about 10,000 requests per 10 minutes per app per mailbox with up to 4 concurrent requests, and delta and subscription tokens expire and must be renewed.
  • SAP Hana: No SaaS-style request quota; throughput is bounded by connection limits, statement memory caps, and workload-class admission control (concurrency/memory limits) that share capacity with production queries.
What ships with Microsoft Graph ⇄ SAP Hana

Connect Microsoft Graph and SAP Hana for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Microsoft Graph–SAP Hana connection.

Real-time

Two-way sync

Changes in Microsoft Graph or SAP Hana instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Microsoft Graph or SAP Hana 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 Graph or SAP Hana record.

Observability

Monitoring

Track your Microsoft Graph ⇄ SAP Hana sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Microsoft Graph and SAP Hana.

How the Microsoft Graph and SAP Hana connectors work

Microsoft Graph

Integration surface
Microsoft Graph unified REST API (v1.0 and beta) at graph.microsoft.com, spanning Microsoft 365 services — Entra ID, Outlook mail and calendar, OneDrive and SharePoint, Teams, and Planner; supports JSON $batch (up to 20 requests per call).
Authentication
OAuth 2.0 via the Microsoft identity platform (Microsoft Entra ID). An app registration holds delegated or application (app-only) scopes such as Mail.ReadWrite, Calendars.ReadWrite, Files.ReadWrite.All, User.ReadWrite.All, and Group.ReadWrite.All; application permissions require tenant admin consent.
Change detection
Delta query (change tracking) returns created, updated, and deleted items since the last deltaLink for users, groups, mail, events, contacts, and driveItems; change-notification subscriptions (webhooks) POST near-real-time notifications to a notification URL and must be renewed before they expire.
Capabilities
read · write · webhooks
Rate limits
Throttled per app and per tenant, returning HTTP 429 with a Retry-After header; limits vary by service — the Outlook mail service allows about 10,000 requests per 10 minutes per app per mailbox with up to 4 concurrent requests, and delta and subscription tokens expire and must be renewed.

SAP Hana

Integration surface
SQL over the SAP HANA client (JDBC/ODBC drivers); OData/REST via XS for app-layer access
Authentication
Dedicated database user credentials over an encrypted TLS connection (password sent hashed); Kerberos, SAML, JWT, and X.509 certificate authentication are also supported. SAP HANA Cloud enforces TLS and IP allowlisting.
Change detection
Polling on a last-modified timestamp column, or AFTER INSERT/UPDATE/DELETE triggers writing to a shadow table; system-versioned temporal tables and SLT/SDI provide trigger- and log-based CDC. No native webhooks.
Capabilities
read · write · CDC
Rate limits
No SaaS-style request quota; throughput is bounded by connection limits, statement memory caps, and workload-class admission control (concurrency/memory limits) that share capacity with production queries.
How it works

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

    Choose tables

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

Microsoft Graph and SAP Hana 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
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 352 integrations available for Microsoft Graph and SAP Hana.

Popular · 5 of 352
All Microsoft Graph integrations All SAP Hana 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