Power Automate: 10 Example Flows for SMEs

Power Automate connects Microsoft 365 applications such as Outlook, SharePoint and Teams with external systems and automates recurring tasks without programming skills. For small and medium-sized businesses, flows that work with the Microsoft 365 licenses already in place are a good starting point, since these use only standard connectors and incur no additional costs. Which connectors belong to the standard tier and which to the premium tier is documented in the official connector overview from Microsoft. As soon as databases, Dataverse or AI-powered document processing come into play, a premium connector is needed, which requires a Power Automate premium license. Below are ten concrete example flows from practice, organized by sales, administration and data processing, each with the required connectors and license tier. As of: July 2026.

Examples for Sales and Customer Service

• Lead notification from the form: A new entry in a Microsoft Forms form automatically triggers a message to the sales team in Teams as well as a confirmation email to the prospect. This way, no lead goes unanswered for more than a few minutes (connectors: Microsoft Forms, Microsoft Teams, Office 365 Outlook; license: Standard).
• Approval of quotes and discounts: Before a quote with special terms is sent out, it goes through an approval step. The responsible manager receives the request directly in Outlook or Teams and can approve or reject it with a click (connectors: Approvals, Office 365 Outlook, SharePoint; license: Standard).
• Capture customer feedback centrally: Responses from a satisfaction survey are automatically stored in structured form in an Excel table, and in the case of low ratings the responsible employee immediately receives a Teams message. This way, dissatisfied customers are not noticed only weeks later (connectors: Microsoft Forms, Excel Online (Business), Microsoft Teams; license: Standard).
• Reminder before customer appointments: A flow checks the calendar daily and sends the responsible employee a reminder along with the relevant documents from SharePoint, so that appointments take place well prepared (connectors: Office 365 Outlook, SharePoint; license: Standard).

Examples for Administration, Accounting and HR

• Approve vacation requests digitally: Employees submit the request via a form, the manager receives an approval request, and after approval the entry is automatically documented in a SharePoint list (connectors: Microsoft Forms, Approvals, SharePoint, Office 365 Outlook; license: Standard).
• Archive incoming invoices: When an email with an invoice attachment arrives at a defined address, the flow automatically saves the attachment in a SharePoint or OneDrive folder with a consistent naming convention (connectors: Office 365 Outlook, SharePoint or OneDrive for Business; license: Standard).
• Automatically extract invoice data: Instead of manually transferring amount, invoice number and supplier, an AI model extracts the relevant fields from the PDF and writes them directly into a SharePoint list for further processing in accounting. This is worthwhile especially with larger invoice volumes, since setting up the AI model requires some effort (connectors: AI Builder for document processing, SharePoint; license: Premium).
• Onboarding checklist for new employees: As soon as a new employee is created in a SharePoint list, the flow automatically creates tasks in Planner for IT, facility management and the relevant department, and informs everyone involved in Teams (connectors: SharePoint, Planner, Microsoft Teams; license: Standard).

Examples for Data and Internal Systems

• Database analysis as a report: A scheduled flow reads key figures from a SQL database and uses them to automatically update an Excel table, which is sent as a weekly report to management (connectors: SQL Server, Excel Online (Business), Office 365 Outlook; license: Premium, since SQL Server is a premium connector).
• Sync project data between Dataverse and SharePoint: Companies that already work with Power Apps and Dataverse automatically keep project status and documents in sync between Dataverse tables and a SharePoint document library (connectors: Microsoft Dataverse, SharePoint; license: Premium).

Which of these flows are suitable for a specific business depends on the existing licenses and the current system landscape. NordFlux supports small and medium-sized businesses in selecting the right flows and implementing them at a fixed price, without unnecessarily purchasing premium licenses.

Frequently Asked Questions about Power Automate Examples

What does a flow with premium connectors cost?

Premium connectors such as SQL Server, Dataverse or AI Builder require a Power Automate premium license, either per user or per flow. The exact calculation depends on the number of users and flows and is described in detail on the Microsoft Learn page on Power Automate license types. Anyone who is unsure should check this before implementation, so that no oversized license is purchased. Details for your own inventory are provided by the Power Automate license consulting.

Are the standard connectors enough for getting started?

For many SME use cases in the Microsoft 365 environment, such as approvals, notifications or simple document filing, standard connectors are completely sufficient. Only when databases, CRM systems outside Microsoft 365 or AI-based document analysis are needed does a premium connector become necessary.

How long does it take to build such a flow?

A simple flow with two to three standard connectors can often be set up and tested within a few hours. Flows with approval logic, multiple branches or AI models require more time for testing and fine-tuning, especially when edge cases need to be handled cleanly.

What happens if the underlying form or list changes?

If the structure of a form or a SharePoint list changes, the flow usually has to be adjusted manually, since otherwise the field mapping becomes faulty or the flow stops completely. It is advisable to keep the form structure and flow logic as stable as possible and to document any changes made.