Published: 17 November 2026 | By AOLC
If your business runs on Microsoft 365, there is a good chance you already have a tool that can stop the copy-and-paste, the chasing of approvals and the forgotten follow-ups. It is called Power Automate, and most South African businesses we speak to have never opened it.
This guide explains what it does in plain English, what your current licence probably covers, which first flows are worth building, and the mistakes that turn a quick win into a security or POPIA headache.
Power Automate connects the apps you already use and runs a set of steps for you whenever something happens. You build it once, and it runs every time without anyone remembering to do it.
What Power Automate Actually Does.
Every automation in Power Automate is called a flow, and every flow has the same shape: a trigger (something happens) followed by one or more actions (what to do about it). A new email arrives with an attachment, so save it to SharePoint and notify the finance team in Teams. A form is submitted, so create a record and ask a manager to approve it.
There are three flow types you will meet first:
- Automated flows — start by themselves when an event happens, such as a file being added or a form being submitted.
- Instant flows — start when someone presses a button, in Teams or on a phone, for jobs like logging a site visit or raising a request.
- Scheduled flows — run at a set time, such as a Monday-morning summary or a month-end reminder.
These are all cloud flows. There are also desktop flows, which let software click through older Windows applications that have no connection of their own. They are powerful, but they need extra licensing and more care, so leave them until the simple flows are working.
What Your Microsoft 365 Plan Includes.
Power Automate comes with many Microsoft 365 business plans for automating Microsoft 365 itself, using what Microsoft calls standard connectors. That covers Outlook, Teams, SharePoint, OneDrive, Forms, Excel Online and the built-in Approvals feature. For a first project that is usually plenty.
Premium connectors are different. Connecting to a database, calling an external system through an API or HTTP request, or running desktop flows needs an additional Power Automate licence. The rules also change when flows are shared widely or used outside the Microsoft 365 apps they were built for, so confirm the licensing before you roll one out to a whole department.
Tip
Microsoft changes what each plan includes and what the add-ons cost from time to time, so check the current terms for your own plan before you design anything around a premium connector. Our Microsoft 365 licensing guide explains the main plans, and we can quote and supply licences through our Microsoft CSP service.
Five First Flows Worth Building.
Start with something small, frequent and low-risk. These five suit most South African offices and use standard connectors only.
- Save email attachments automatically. When a message with an attachment lands in a shared mailbox such as accounts@ or orders@, save the file into the right SharePoint folder and post a note in the team channel.
- One-click approvals. A leave request, purchase request or quote sign-off goes to a manager as an approval in Teams or Outlook. The answer is recorded with a date and time, and the requester is told the outcome.
- Form to list. A Microsoft Form (a job card, a new-supplier request, a helpdesk-style request) writes straight into a SharePoint list, so nothing lives in someone’s inbox.
- Reminders that chase for you. A scheduled flow checks a list every morning and emails the owner of anything overdue, then copies their manager if it is still open a week later.
- New-starter checklist. When HR adds a new employee to a list, the flow creates the tasks for IT, the line manager and facilities, and sends the welcome email.
1 task
Pick one repetitive job that someone dislikes doing weekly. Measure how long it takes today, build the flow, and compare. A measured win makes the next project easy to approve.
For more ideas on what to automate and in what order, read our companion article, 5 Business Processes You Should Automate Today.
Your First Flow, Step by Step.
You do not need to be a developer for the simple cases. The basic routine is the same every time:
- Write the process on one page first. What starts it, what should happen, who decides, and what the exceptions are. If you cannot describe it simply, the process needs tidying before it can be automated.
- Open Power Automate with your work account and choose a template close to your idea, or start from blank. Templates are a quick way to see how a trigger and its actions fit together.
- Build it with test data. Use a test mailbox or a test list, not live customer records.
- Run it and read the run history. Every run shows which step succeeded or failed and why. Run history is kept for a limited time (28 days at the time of writing), so record anything you need to keep elsewhere.
- Run it alongside the manual way for a week or two, then switch over once the results match.
- Give it an owner and a name that says what it does, so that somebody knows who to call when it stops.
Mistakes That Cause Trouble.
- Flows owned by one person. A flow normally runs with the connections of the person who built it. When that person leaves and their account is disabled, the flow stops. Use a dedicated service account with multi-factor authentication where your setup allows it, or have an administrator own flows that the business depends on. See our MFA guide for why that matters.
- No data policies. Left open, a flow can move company data from SharePoint into a personal cloud app. Administrators can use data loss prevention policies in the Power Platform admin centre to decide which connectors may be mixed.
- Silent failures. A flow that fails overnight and tells nobody is worse than no flow. Add a failure notification to anything important.
- Automating a broken process. If the manual process is messy, the flow will be messy too, only faster.
- Shadow IT. Staff build flows without telling anyone, and nobody knows what is connected to what. Agree who may build, where flows are listed, and who reviews them.
POPIA and Power Automate.
Flows move personal information: names, ID numbers, bank details, leave records, customer emails. POPIA applies to all of it, exactly as it does when the same data sits in a spreadsheet. Four things to check before you go live:
- Security safeguards. Limit who can see the lists and folders a flow writes to, and who can edit the flow itself. POPIA expects reasonable technical and organisational safeguards for personal information.
- Where the data lives. Microsoft acts as an operator for the data in your tenant. Check where your tenant and Power Platform environment are hosted and that your operator arrangements cover it, particularly if information is transferred outside South Africa (POPIA sections 20, 21 and 72). Our POPIA and cloud storage guide walks through the questions to ask.
- Keep only what you need. Do not copy full ID numbers or bank details into a notification email when a reference number will do.
- Keep a human in the loop for significant decisions. POPIA section 71 restricts decisions with legal or similarly significant consequences for a person that are based solely on automated processing. Use a flow to prepare and route the decision, and let a person make it. Our employee data rights guide covers the employer’s duties in more detail.
When to Call for Help.
You can build the simple flows yourself. Bring in a specialist when a flow touches money or personal data, connects to accounting or CRM software, needs premium connectors, or has become something the business cannot run without. A good partner will map the process, build and test the flow, document it and make sure the accounts and licences behind it are managed. If your IT is already stretched, our managed IT service can look after the accounts, licences and security that your automations depend on, and our business automation service builds the flows themselves. For a short summary to share with your team, see our free guide 5 Business Processes to Automate This Quarter.
Book a Free Workflow Review.
Tell us which repetitive job costs your team the most time. We will check what your Microsoft 365 plan already includes, show you what can be automated and give you a clear scope and quote.
Contact Us
← Back to Blog