Four patterns that let mid-sized companies automate workflows directly in Microsoft Teams: approvals, notifications, forms and question bots.
Most approvals in mid-sized companies still run over email: the leave request to the boss, the invoice for release to accounting, the quote for review to the sales lead. Yet the actual work has long moved into Microsoft Teams. That is exactly where the automation belongs: automating Microsoft Teams for mid-sized companies means handling a workflow inside the tool that is already open, instead of sending it through the building by email. That way it gets done faster.
In practice, automating Microsoft Teams means four things for mid-sized companies: approvals directly in the chat, automated notifications from other systems into channels, forms that kick off a process, and simple bots that answer questions about company knowledge. All four patterns can be built with Microsoft's built-in tools, above all with Power Automate and the Approvals app. This article shows what you can manage yourself and where support makes sense.
In mid-sized companies, automation rarely fails because of the technology, but because staff will not open an additional tool. A new portal for leave requests needs training, passwords and reminders. An approval card in the Teams chat needs none of that: it appears right where the recipient is already typing, and it is answered with a single click.
On top of that: in most companies, Teams is already paid for. Anyone with Microsoft 365 in house already owns the building blocks with Power Automate, Forms and the Approvals app. How these building blocks work together is something we describe in detail on the Microsoft 365 automation page.
The Approvals app renders sign-offs as a card directly in the Teams chat: submit a request, approve or reject, and every step is documented with a timestamp. This is the pattern with the fastest payoff, because it replaces the email ping-pong exactly where it is most annoying.
Three typical cases from our projects: the leave request goes as a card to the manager and, once approved, enters itself in the team calendar. The incoming invoice above a defined amount moves to management for release, below that accounting can handle it. The quote above a threshold needs a four-eyes sign-off before it goes out. In every case an escalation can be added: if the approver does not respond for two days, the flow reminds them or forwards it to their deputy.
A notification flow pushes events from other systems as a message into a Teams channel, without anyone having to actively check. Instead of reviewing five systems one by one each morning, the team reads a single channel.
Technically, these notifications are usually small flows in Power Automate that connect a trigger in the source system with a channel message. For common systems there are ready-made connectors, for the rest there are webhooks.
Teams automation consists of four patterns: approvals in the chat, notifications from other systems, forms that start processes, and question bots on company knowledge. A skilled user builds the first three themselves with Power Automate; for the fourth and for chained processes, support pays off.
The third pattern connects a form to a process: an employee fills out a Microsoft Forms form, a flow files the data in a structured way in SharePoint and notifies the people responsible in Teams. Damage report, material order, IT request: anything that arrives today as an informal email and then gets sorted by hand is suitable for this. The gain lies less in the form itself than in the clean filing that comes out of it.
The fourth pattern is the question bot: an agent in Teams that answers questions like “How do I apply for parental leave?” or “Where is the current price list?” from your own documents. With Microsoft Copilot and Copilot Studio, such agents can be set up on SharePoint content. What an internal knowledge assistant can do and where its limits lie is something we described in a separate article.
The honest answer: a single approval flow or a channel notification is doable with the standard connectors included in Microsoft 365, and a skilled user builds something like that in an afternoon. You need neither an agency nor any additional software for it.
Consulting on automating Microsoft Teams pays off at three points. First, when premium connectors or external systems such as ERP and inventory management come into play, because then it is about licensing questions and interfaces. Second, when flows become multi-stage: escalations, deputy rules and error handling are the difference between a tinkered flow and a process the business relies on. Third, with the question bot, because its quality depends on how your documents are prepared and not on the tool.
The biggest danger in Teams automation is not the failed flow, but the sprawl of working ones. By default, flows hang on the account of the person who built them: if that colleague leaves the company, invoice release comes to a standstill and no one knows why. Three simple rules help against this: transfer business-critical flows to a service account, document every production flow with its purpose and owner in a list, and use a DLP policy to define which connectors may take company data out at all. Whoever plans for this from the start keeps control over their automation instead of chasing after it.
Approvals, channel notifications and form flows with standard connectors are already included in the common Microsoft 365 Business licenses. Additional costs only arise from premium connectors, for example for SAP or SQL databases, and from the effort for design and build. You will find the current license prices in Microsoft's price list; they change regularly.
For the four basic patterns, no. Power Automate, the Approvals app and Microsoft Forms are part of Microsoft 365. Third-party tools only become interesting when you want to connect many systems outside the Microsoft world; there a tool like n8n can be the better choice.
Yes, the Approvals app logs the requester, approver, decision and timestamp. For sign-offs with formal requirements, for example in accounting, you should agree on the retention of the logs with your tax advisor. That is a question of process design, not legal advice on our part.
A small group is enough: one or two named people per area plus a central point that keeps the overview. More important than the restriction is the rule that every production flow is documented and business-critical flows are transferred to a service account.
A single approval flow is up in days, not months. For a package of several flows including governance rules, in projects we reckon on around 30 days until the first production results, depending on how clearly your processes are defined beforehand.
NordFlux builds digital employees for organisations: automations and AI agents that take over repetitive work. You stay in control.
How to automate Microsoft Planner with Power Automate and where the connector reaches its limits after the Planner-To Do-Project merger.
Five SharePoint processes that mid-sized companies should automate first, and the tools you use to do it.
Email ping-pong, forgotten delegations, no traceability: Where approvals get stuck in mid-market companies and how to fix it.
In the free initial analysis we look at your approvals and notification paths and tell you concretely which of them is doable with your existing Microsoft 365 licenses.
