How do I connect Microsoft Teams to SAP?

Connect Microsoft Teams to SAP using Koodisi's visual workflow builder and its no-code REST Client for both platforms — SAP is reached through its REST APIs, so no custom middleware is required. Build triggers on SAP events, design the Teams card, and deploy. Credentials for both systems are stored in Key Vault.

Does the Microsoft Teams SAP integration work in real time?

Yes. SAP events can trigger Koodisi workflows as they occur, so an approval card reaches the channel while the order still has time to move. Scheduled runs are also supported where a periodic digest of pending items is preferred over per-event alerts.

Do approvers need an SAP licence to approve from Teams?

Approvers act on the Teams card, and Koodisi performs the SAP write. Whether that requires a named SAP user for each approver depends on your SAP licensing terms and how your organisation configures the service account — confirm the arrangement with your SAP account team before rollout.

Is the approval decision auditable in SAP?

Yes. The decision, the approver, the comment, and the timestamp are written back onto the SAP record, and Koodisi keeps its own execution log of the run with the payload attached. Both sides can be reconciled during an audit rather than relying on chat history.

Microsoft Teams

SAP

Microsoft Teams + SAP Integration

Approve SAP orders and see master data changes in Teams, without handing everyone an SAP licence.

Get a Demo View Docs

Approvals resolved in the channel instead of waiting on an SAP login

Occasional approvers act without consuming an SAP licence

Every decision written back to SAP against the approver's own identity

Today

Approvals stalled behind an ERP login

Approvals and exceptions live in SAP, but the people who need to act on them work in Teams.
Every approval means logging into an unfamiliar interface, so requests sit for days and orders miss their window.
Occasional approvers do not have SAP licences at all, so decisions get relayed through chat and re-keyed by someone who does — which means the audit trail records the wrong person.
Master data changes go unnoticed until something downstream breaks.

With Koodisi

ERP events in the channel with Koodisi

Koodisi connects Microsoft Teams and SAP through its no-code REST Client, so ERP events reach the channel as actionable cards.
Sales Orders on credit hold, Purchase Orders over threshold, and Business Partner changes post to the relevant Teams channel with the detail needed to decide.
Approvers act on the card, and Koodisi writes the decision back into SAP against the approver's own identity — so the record shows who actually decided, not who re-keyed it.

The sync

What moves, in both directions

Microsoft Teams and SAP stay in step because the sync runs both ways.

SAPMicrosoft Teams

Post Sales Order, Purchase Order, and Business Partner events as cards with the values needed to approve or reject.

Microsoft TeamsSAP

Capture approval decisions and comments, and write them back into SAP against the approver's identity.

Approvals happen in hours instead of days, occasional approvers never need an SAP seat, and every decision carries a timestamped record of who made it.

Use cases

What teams automate with this integration

The work that moves between Microsoft Teams and SAP today, and what Koodisi takes over.

Sales Order on hold posts to the channel

When a Sales Order is blocked in SAP — credit hold, pricing exception, or missing master data — Koodisi posts a card to the responsible Teams channel.
The card carries customer, value, and the specific reason for the block.
The owner releases or rejects from the card, and Koodisi applies the decision in SAP.
Orders stop sitting in a queue nobody is watching.

Purchase Order approval above threshold

When a Purchase Order exceeds its approval threshold in SAP, Koodisi routes an approval card to the approver or channel defined by the rule.
Vendor, line items, and budget context travel with the card.
The approver's decision and comment are written back onto the SAP record against their own identity, so the audit trail names the person who actually decided rather than whoever re-keyed it.

Business Partner changes alert the owning team

When Business Partner master data changes in SAP — bank details, payment terms, or tax identifiers — Koodisi notifies the owning Teams channel with the before and after values.
Finance sees sensitive changes as they happen rather than during a later review.
Sensitive values can be masked in the notification and in logs while still showing that a change occurred.

Teams questions resolved with live SAP data

When someone asks about order or delivery status in a Teams channel, Koodisi can return the current SAP values without the asker opening the ERP.
The lookup is read-only and scoped by permission, so people see what their role allows and nothing more.
Routine status questions stop consuming the time of the few people with SAP access.

The workflow

What this looks like when it runs

Koodisi connects Microsoft Teams and SAP using its no-code REST Client for both platforms.
SAP events — order blocks, approval thresholds, master data changes — trigger workflows that read the record, select the fields an approver needs, and post an actionable card to the right Teams channel.
Decisions taken on the card return through the same workflow and are written back into SAP against the approver's identity, so the audit trail reflects who actually decided.
Approval thresholds and routing live in a decision table your team can review and change without editing the workflow.
Sensitive values can be masked in notifications and logs, permissions scope who may approve what, and every run is retried on transient failure and recorded for audit.

SAP Purchase Order → Teams approval

1Purchase Order exceeds its approval threshold in SAP
2Koodisi builds an approval card with vendor, line items, and budget context
3Card is routed to the approver or channel defined by the rule
4Decision and comment are written back into SAP against the approver's identity

SAP Sales Order hold → channel resolution

1Sales Order is blocked in SAP for credit or pricing
2Koodisi posts the order, customer, value, and block reason to the channel
3Owner releases or rejects the order from the card
4Koodisi applies the outcome in SAP and logs the run for audit

Governance

Automated, but still under control

Every run is authorised, recorded, and observable — the part that decides whether automation survives an audit.

Scoped permissions

Role-based access decides who can publish or run the Microsoft Teams and SAP workflows, and who can only watch them.

Every run recorded

Each execution writes an audit trail — what triggered it, what changed, and what the downstream system returned.

Credentials in Key Vault

Microsoft Teams and SAP credentials are stored and retrieved from Key Vault, never pasted into workflow steps.

Traced end to end

OpenTelemetry logs, metrics, and traces show where a run slowed down or failed, rather than reporting one aggregate status.

Routing rules stay readable

Which records sync, and which need approval first, live in a decision table your team can review and change without editing the workflow.

Sensitive fields masked

Personal and commercial values can be masked in logs so an operational record does not become a copy of your customer database.

FAQ

Frequently asked questions

Still have a question? Talk to our team.

Related Integrations

Salesforce to SAP Integration SAP to Salesforce Integration SAP to Slack Integration Salesforce to Microsoft Teams Integration

Ship integrations faster. Operate them without chaos.

Less time on auth, retries, and deployment scripts. More time on the integrations your customers are asking for.

Contact Sales