How to integrate Microsoft Teams with SAP Business ByDesign
Short answer
Build a Teams bot or Power Automate flow that reads and writes ByDesign through communication-arrangement web services or custom OData services. Adaptive cards carry approvals and alerts, Entra ID identifies the user, and a mapping table ties each Teams user to a ByDesign employee.
Many ByDesign companies are Microsoft shops for everything else: Microsoft 365, Teams for chat, SharePoint for files. ByDesign sits off to the side in a browser tab, and the notifications it sends arrive by email where they compete with everything else. Managers approve late, planners miss stock alerts, and finance learns about a blocked invoice a day after it happens.
Teams is a natural front door because people are already in it all day. A channel post for exceptions, a card for approvals, and a bot for quick lookups remove most of the reasons to log into ByDesign for small tasks. The system of record stays the same.
The integration choices are shaped by ByDesign being SaaS: you work only through supported web services, communication arrangements and the SDK, and you should plan the Teams side to be the thin layer.
What teams use it for
Approval cards for purchase requests
An adaptive card shows requester, cost center, items and total, with Approve and Decline. The decision completes the ByDesign workflow task.
Stock-out and reorder alerts in a planner channel
A scheduled query on available quantity per material and warehouse posts to the planning channel when stock falls below the safety level.
Order desk lookups
Customer service types order status for a customer and the bot replies with open sales orders, promised dates and delivery status.
Blocked supplier invoice notifications
AP gets a card when an invoice fails a match, with PO and goods receipt references and a link into ByDesign.
Production order exceptions
Supervisors see late or incomplete production orders each morning in a Teams channel, with owner tagging.
Month-end close checklist nudges
Finance receives reminders about unposted documents and open accruals, pulled from report feeds.
SAP Business ByDesign integration surface
- SOAP web services exposed through Communication Scenarios, with a communication system, user and arrangement for the bot or flow.
- Report-based OData feeds from Business Analytics for read-only data such as open orders, stock overviews and aging, with the custom reports defined by key users.
- Custom OData and web services created in the Cloud Application Studio for narrowly scoped operations.
- Workflow rules and SDK business object events that can call out to a webhook when a document hits a certain status.
- Employee and business user records in ByDesign, which need to be linked to Entra ID identities by email or employee number.
- SAP Integration Suite as an optional broker for monitoring and retries.
How it works
- 1
Pick the Teams pattern
Incoming webhooks or Workflows for simple alerts, a bot built with the Teams SDK or Bot Framework for interactive cards, or Power Automate for low-code flows with an HTTP action to ByDesign.
- 2
Set up ByDesign access
Create the communication system, a dedicated communication user and an arrangement for the scenarios needed. Prefer certificate authentication where supported by your configuration.
- 3
Register the app in Entra ID
Create an app registration for the bot, configure single sign-on, and decide whether actions run as the integration user or are checked against the person's own ByDesign authorisations.
- 4
Build a user mapping
Maintain a table of Entra user to ByDesign employee or business user so that approvals are recorded against the right person and a user cannot approve outside their authority.
- 5
Design the cards
Keep cards short: three to six fields, one primary action. Always include a deep link back to the ByDesign document for detail.
- 6
Handle write-backs and refresh
After an action, update the card in place to show the outcome and the time, so nobody clicks twice on a stale card.
- 7
Monitor
Alert on failed web service calls and expired credentials; review the ByDesign web service message monitor for rejected inbound calls.
Example flows
Approve a purchase request from Teams
Trigger: A purchase request enters approval in ByDesign.
- A workflow step posts to the bot with request ID and approver email.
- The bot resolves the Entra user and sends an adaptive card to that person.
- The approver taps Approve, optionally adding a comment.
- The bot checks the mapping, calls the ByDesign service to complete the task, and updates the card to Approved.
Result: Approval turnaround drops from days to hours and the comment is kept with the workflow history.
Morning supply exceptions
Trigger: A scheduled job runs at 7:00 local time.
- The job reads a report feed of purchase order items past their delivery date.
- It groups by buyer and posts one message per buyer in a procurement channel.
- Each message includes a button that sends a reminder template to the supplier contact.
Result: Buyers start the day with a prioritised list instead of hunting in work center views.
Keeping data on-prem
ByDesign is cloud only, so the question is where the Teams bot and any AI sit. The bot service can run in your own Azure tenant, a private cloud or on-prem behind a gateway that exposes only the Bot Framework endpoint. If you want natural-language lookups, use a self-hosted open-weight model on your own GPUs to turn questions into calls against a fixed set of read-only ByDesign queries, so customer and pricing data does not go to a third-party model API.
Security checklist
- Use a least-privilege communication user and separate arrangements for read-only and write operations.
- Check each action against the mapped ByDesign user, not only against the bot's credentials, so authority limits are respected.
- Restrict channel membership where cards expose margins, prices or payroll-adjacent data.
- Verify the Bot Framework token on every inbound request, and keep secrets in a vault, not in flow definitions.
- Retain an audit record outside Teams in case messages are deleted by retention policies.
Ways to get it done
Power Automate with HTTP actions
Effort: Days per flow; complexity grows with mapping and error handling.
Quick wins for alerts and simple approvals if you already license Power Platform.
Custom Teams bot with a ByDesign service layer
Effort: 3 to 6 weeks for a first set of cards and lookups.
Needed for rich lookups, user mapping, and enforcing per-user authority.
Partner-built with AI lookups
Effort: 4 to 8 weeks.
When you also want free-text questions and summaries, ideally on a private model.
Pitfalls
- !Adaptive card features differ across Teams clients; test in desktop, web and mobile.
- !Sending approvals as the integration user hides who actually decided; always pass the real approver into the audit trail.
- !Report feeds are only as fast as the underlying report; avoid per-message full-table pulls.
- !Entra email and ByDesign email often differ for contractors and shared accounts, which breaks mapping silently.
- !Posting too many alerts trains people to mute the channel; start with only exceptions that need action.
Frequently asked questions
Is there an official SAP Business ByDesign app for Teams?
I would not assume one. SAP has published collaboration integrations for some products, but for ByDesign the dependable approach is a bot or Power Automate flow over web services. Check with your SAP partner for the current state on your release.
Can I approve ByDesign workflow tasks from Teams?
Yes, if you expose the workflow task or the underlying document action through a web service the integration can call. The details depend on the task type, so confirm in a test tenant which approvals can be completed by service.
Do users need separate logins for the bot?
They sign in to Teams with Entra ID. The bot then maps that identity to a ByDesign user. The integration usually calls ByDesign with a technical user, so you must enforce authority checks in your own layer.
Can Power BI and Teams work together here?
Yes. A Power BI report can be pinned in a Teams channel while alerts and approvals come through the bot. Keep the roles separate: Power BI for analysis, the bot for actions.
What does this cost to run?
Mostly Microsoft licensing you already have plus hosting for a small service. Development effort is the real cost. Power Automate premium connectors can add per-user fees, so model that before choosing the low-code route.
Want Microsoft Teams working on your SAP Business ByDesign?
A free 30 minute assessment: we map the integration path for your version and setup, and where it should run.
Get a free assessment