Microsoft workflows are automated sequences of tasks that run across Microsoft 365 apps without anyone starting them by hand. Most are built in Power Automate, but the Workflows app in Microsoft Teams, Microsoft Lists, Forms, Approvals and Copilot Studio all create them too. Which tool you should use depends on who is building the workflow and how complex it is.
Key Takeaways
- “Microsoft workflows” is not one product. It covers the Workflows app in Teams, Power Automate, Lists, Forms, Approvals and Copilot Studio. Choosing between them is the first decision.
- Teams Workflows is where most people start. It is built in, template driven, and handles the common cases without opening Power Automate at all.
- Power Automate is the engine underneath. Nearly everything else is a simpler front end on the same platform.
- The limits are real and worth knowing before you build. Licensing, premium connectors, run quotas and approval depth all bite at predictable points.
- Classic SharePoint workflows are being retired. If your business still runs them, Power Automate is the migration path.
What Are Microsoft Workflows?
Microsoft workflows are automated steps that run across your Microsoft 365 apps. An event starts them, not a person.
Some are simple. Send a notification when a file lands in SharePoint. Others are not. Route a purchase order through three approvers, then update the accounting system.
The underlying idea is always the same: a trigger starts the workflow, then one or more actions run in order, with conditions deciding what happens next.
Microsoft 365, Office 365, M365: the naming
You will see the same thing called Microsoft 365 workflows, Office 365 workflows, M365 workflows and MS365 workflows. They are the same capability. Microsoft renamed Office 365 to Microsoft 365 in 2020 for most business subscriptions. The old name stuck. It still turns up in Australian businesses, mostly in documents written before the change.
What does differ between subscriptions is what you are entitled to build. That is covered in the limitations section below.
Is Microsoft Workflow the Same as Power Automate?
Not quite, and the distinction matters when you are choosing a tool.
Power Automate is Microsoft’s workflow platform. It is where flows are built, run and monitored, and it holds the connector library that lets a workflow reach other systems.
“Microsoft workflows” is the broader term. It covers Power Automate and the simpler builders sitting on top of it.
Three of those: the Workflows app in Teams, the automation rules in Microsoft Lists, and anything Copilot Studio generates. All three produce Power Automate flows underneath, and the person building them may never open Power Automate.
So every Power Automate flow is a Microsoft workflow. Not every Microsoft workflow is built in Power Automate directly.
Older documentation adds to the confusion. Microsoft Flow was renamed Power Automate in 2019, and classic SharePoint workflows were a separate, much older system that is now being retired.
Which Microsoft Workflow Tool Should You Use?
Most Australian businesses already hold every tool below, so the question is rarely which Microsoft workflow software to buy. It is which of these fits the job in front of you, and whether you need a separate workflow management system at all.
| Tool | Best for | Who builds it |
| Workflows in Microsoft Teams | Notifications, reminders, simple approvals inside Teams | Anyone, from templates |
| Microsoft Lists rules | Alerts and status changes tied to a list | Anyone |
| Microsoft Forms plus Power Automate | Collecting a request, then acting on it | Anyone, with a little setup |
| Approvals in Teams | Sign-offs that need an audit trail | Anyone |
| Power Automate cloud flows | Multi-step processes across several systems | Someone comfortable with logic and connectors |
| Power Automate desktop flows | Automating legacy software with no API | IT or a trained power user |
| Copilot Studio | Workflows described in natural language, agent driven | Anyone, with governance in place |
| Azure Logic Apps | High volume or developer-managed integration | Developers |
A practical rule: start at the top of that table and move down only when the tool in front of you cannot do the job. Most workflows that get built in Power Automate could have been built in Teams or Lists in a fraction of the time.
Where Microsoft Workflow Tools Fall Short
Microsoft documentation explains what its workflow management tools do. It is less forthcoming about where they stop. These are the limitations worth knowing before you commit to a design.
- Premium connectors cost extra. Standard connectors cover Microsoft 365. Reaching most third-party or on-premises systems requires a premium licence per user or per flow.
- Run limits apply. Flows are subject to daily action quotas that vary by licence. High-frequency automation can hit them.
- Approvals get awkward past a point. Sequential and parallel approvals are supported, but complex conditional routing becomes hard to maintain and harder to hand over.
- Error handling is manual. A failed flow does not announce itself unless you have built the notification. Unmonitored flows fail quietly.
- Desktop flows need a machine running. Robotic process automation on the desktop needs an available, signed-in machine, which is an infrastructure commitment rather than a cloud service.
- Flows inherit the builder’s access, permanently. Every connection in a flow signs in as the person who created it. So a flow built by a staff member runs with that person’s permissions, unattended, for as long as it exists. This matters if you have done Essential Eight work on restricting administrative privileges. That control limits what a person can do at their keyboard. It does not limit what a flow they built keeps doing every night after everyone has logged off.
None of these is a reason to avoid the platform. They are reasons to decide the design before building, which is the part most businesses skip.
Workflows in Microsoft Teams
For most Australian businesses, Teams is where workflows now begin. The Workflows app sits inside Teams, offers a template gallery, and covers the common cases without anyone opening Power Automate.
Typical uses are simple. Post a message to a channel on a schedule. Notify a team when a form is submitted. Request approval on a file. Create a task when a message is flagged.
Two things make it worth starting here. The templates cover a large share of what small teams need, and because the flow is created inside Teams, the people who use it can see and understand it. Workflows built in Power Automate by one person tend to become invisible to everyone else.
When a Teams workflow runs out of room, it can be opened in Power Automate and extended. Nothing is lost by starting simple.
Building Workflows with Power Automate
Power Automate is where workflow automation in Microsoft 365 gets serious. A flow has three parts.
Triggers
The event that starts the flow. It might be a new email in Outlook, a file created in SharePoint, or a response submitted in Forms. It can also be a row added in Dataverse, a set time, or someone pressing a button.
Actions and conditions
What the flow does once it starts, and the branching logic that decides between paths. Actions can span Microsoft 365, Dynamics 365 and external systems through connectors.
Testing and monitoring
Every flow has a run history showing what happened and where it failed. Checking that history is the difference between automation you can trust and automation nobody notices has broken.
Three habits make Power Automate workflows last. Name flows so someone else can tell what they do. Build the failure notification at the same time as the flow, not after the first failure. And own flows through a service account or a solution rather than an individual’s login.
Where Your Workflow Data Is Stored
This is worth settling before you automate anything that touches personal information.
Power Platform stores your data in what Microsoft calls the home geo. That is set when the tenant is created, based on the billing country.
For an Australian tenant, the home geo is Australia. The datacentres are Australia East in New South Wales and Australia Southeast in Victoria, and each replicates to the other. Source: Microsoft Learn, data storage and governance in Power Platform, and the Microsoft Cloud Australia datacentre documentation.
Three qualifications matter, and none of them is obvious.
Microsoft Forms is the trap
Forms is one of the most common workflow triggers. Where it stores data depends on when your tenant was set up.
Microsoft’s data location documentation is specific. Australian tenants that set Forms up on or before 2022-10-12 have their Forms data stored in the United States. Tenants that set it up after that date have it stored in Australia.
So if you have been on Microsoft 365 for a few years, and a Form feeds one of your workflows, those responses may be sitting in the United States. Check rather than assume. The Data Location Card in the Microsoft 365 admin centre shows where each service stores your data.
Connectors move data outside the boundary
The home geo covers data at rest inside Power Platform. It does not cover what leaves.
Microsoft’s documentation is explicit: when Power Automate connects to external services, customer data may be transferred outside the region. A flow that stays inside Microsoft 365 keeps data in the Australian boundary. A flow that calls a third-party system sends it wherever that system lives.
Microsoft also does not publish where a flow physically executes, only where its data is stored. If your obligations are strict, that distinction is worth raising with your provider rather than assuming.
What this means under the Privacy Act
None of this makes Power Automate unsuitable. It means one question is worth answering before you build, not after an audit asks it: does this flow disclose personal information overseas? That is Australian Privacy Principle 8, and it applies.
If your requirements are strict, Advanced Data Residency is the next step. Microsoft offers it to Australian tenants, and it pins data at rest to a named region.
Why Workflows Break
Most businesses discover workflow governance the same way: a process that has run quietly for a year stops, and nobody can say why. These are the causes, in roughly the order we see them.
The person who built it left
This is the big one. Power Automate assigns every cloud flow to exactly one owner, the person who created it, unless a co-owner is added. The connections inside the flow authenticate as that person too.
Disable or delete that account and the flow becomes what Microsoft calls an orphaned flow. It shows with no owner in the Power Platform admin centre.
If a co-owner exists, the flow keeps running. But any action using the leaver’s connections starts failing. If there is no co-owner, nobody can even open it.
There is no automatic reassignment. Microsoft’s documented fix is to add a co-owner through the admin centre, or to reassign in bulk with the Set-AdminFlowOwnerRole PowerShell cmdlet.
The prevention is one minute of work: add a co-owner when you build the flow, and add flow ownership to your offboarding checklist alongside mailbox and licence steps.
The licence moved
Flows using premium connectors run on their owner’s licence. Reassign that licence, or change the owner to someone without an equivalent one, and premium actions stop. Per-flow licensing avoids this by attaching entitlement to the flow rather than the person, which is worth considering for anything business critical.
Nobody was told it failed
A failed flow does not announce itself. Power Automate records the failure in run history and sends a notification to the owner, which is of limited use when the owner has left or ignores it. Build the failure alert to a shared mailbox or Teams channel at the same time as the flow, not after the first outage.
A tool you relied on got deprecated
Microsoft retires features regularly, and workflow integrations are not exempt.
The most recent example is the Visio to Power Automate export, which let teams design a process as a BPMN diagram and turn it into a flow. It was deprecated effective 2026-07-14, and the Export and Show Flow Markup buttons have gone from the Visio ribbon. Existing flows still run, but the design path is closed.
Worth checking Microsoft’s “important changes coming” page for Power Platform before you build a workflow that depends on an integration.
Nobody can tell what it does
Flows named “Flow 1” and “Copy of Flow 2” are common and unmaintainable. Naming a flow for the process it serves is the cheapest governance you will ever do.
Using AI and Copilot in Power Automate
Copilot in Power Automate lets you describe a flow in plain language. It builds a first version, and you refine it by conversation instead of dragging actions around. Copilot Studio goes further. It creates agents that decide what to do rather than following a fixed path.
For most businesses the realistic use today is drafting. Copilot gets a flow roughly right quickly, and someone who understands the process corrects it. That is a genuine saving on build time, but it does not remove the need to understand what the flow does.
The governance question arrives with it. An agent that acts on your data reaches whatever the person who built it can reach, which makes permissions and data governance a prerequisite rather than a follow-up. We cover that side of it in our AI strategy consulting service.
Microsoft Workflow Examples for Australian Businesses
These are the automations Australian small and medium businesses build first, in rough order of how often we see them.
1. Employee onboarding
Create the account. Assign permissions. Send the welcome email with the documents attached. Book the orientation session. Track what has been signed.
This is the most common first workflow. The steps are fixed, and a missed step shows up straight away.
2. Purchase order approval
Route each request to the right approver, based on the amount or the department. Chase the ones that sit unanswered. Escalate the ones that stall. Write the result back to your accounting system.
3. Document review and approval
Pick reviewers by document type. Set a deadline and send reminders. Keep versions and comments together. Collect the sign-off at the end.
4. Leave requests
Give staff a simple form. Check the balance and look for clashes. Send it to the right manager. Update the HR system and the team calendar once it is approved.
This one rarely needs Power Automate. Teams Workflows will usually do it.
5. Expense and budget management
Collect claims through one form. Check them against policy. Route for approval by amount or department. Pass the approved ones to accounts.
6. IT service requests
Give staff one place to raise a request. Sort and rank it automatically. Assign it to the right person. Report on how long fixes take.
Four more come up almost as often: customer service triage, contract management, marketing content approval, and project milestone tracking. All four make better second or third projects than first ones, for the reasons below.
Which to build first, and which to leave
They are not all equally good starting points.
| Start here | Why |
| Leave requests | Frequent, simple rules, an error is visible and cheap to fix |
| IT service requests | Frequent, and the current process is usually email |
| Employee onboarding | Fixed steps, and a missed step is obvious immediately |
| Leave until later | Why |
| Contract management | The renewal rules are usually undocumented, and a missed expiry is expensive. Document the process before automating it |
| Customer service triage | Misrouting is invisible until a customer complains, which makes errors expensive and slow to detect |
| Project milestone tracking | Depends on project structures that tend to change faster than the flow can be maintained |
The test for any first automation is the same: frequent, currently slow, and tolerant of review. A process that is rare, or where a silent error would be costly and hard to spot, is a poor place to learn the platform.
What Is Replacing SharePoint Workflows?
Power Automate is the replacement. Classic SharePoint workflows, built on the older SharePoint Designer platform, are being retired, and Microsoft’s migration path points at Power Automate.
If you still run classic SharePoint workflows, plan the migration. Do not rebuild them step for step.
Old workflows usually contain rules nobody wrote down. So the first job is working out what the existing one actually does. Once you know that, rebuilding in Power Automate is a chance to simplify the process rather than copy it.
Businesses weighing up how much of this to keep in SharePoint at all may find our comparison of SharePoint and a dedicated intranet useful.
Getting Started with Microsoft Workflow Automation
Microsoft 365 workflow automation works best when it starts small and narrow. Do not try to automate workflows across the whole business at once. Pick one process, build it in the simplest tool that will do the job, run it for a month, then decide whether to extend it.
The businesses that get the least from automation are usually the ones that tried to map everything first. The businesses that get the most tend to have automated one annoying thing, seen it work, and gone looking for the next one.
Kloudify works with Australian businesses on Microsoft 365 and Azure. On workflow engagements that usually means three things.
We review what your existing licences already cover. We build the first two or three automations alongside your team rather than for them. And we set the ownership and failure alerting, so they outlast the people who built them. If you would like help working out which processes are worth automating and which tool fits, talk to us about business productivity services
Frequently Asked Questions
Microsoft workflows are automated sequences of actions that run across Microsoft 365 applications, started by an event rather than by a person. They can be built in the Workflows app in Microsoft Teams, in Power Automate, in Microsoft Lists, or through Copilot Studio. A workflow has a trigger, one or more actions, and usually some conditional logic.
Not exactly. Power Automate is the platform where workflows are built and run. “Microsoft workflows” is the broader term, covering Power Automate along with the simpler builders that sit on top of it, such as Workflows in Teams and rules in Microsoft Lists. Those simpler tools create Power Automate flows underneath.
Power Automate. Classic SharePoint workflows built on SharePoint Designer are being retired, and Power Automate is Microsoft’s stated migration path. Because older workflows often contain business rules that were never documented, the first step is usually to establish what the existing workflow actually does before rebuilding it.
Microsoft Visio is the diagramming tool, but its direct export into Power Automate has gone. Microsoft deprecated that integration effective 2026-07-14, removing the Export and Show Flow Markup controls from the ribbon. Flows already exported keep running and BPMN templates remain, but new automation must be built in the Power Automate designer.
In the tenant’s home geo, which for an Australian tenant means the Australia East and Australia Southeast datacentres. Two qualifications apply. Microsoft records Forms data as stored in the United States for Australian tenants that set Forms up on or before 2022-10-12. Any flow calling an external service can also send data offshore. Check the Data Location Card in your own admin centre.
It becomes an orphaned flow. Power Automate gives each flow a single owner by default, and its connections authenticate as that person. With a co-owner the flow keeps running, though actions using the leaver’s connections fail. Without one, nobody can access it. There is no automatic reassignment, so add a co-owner at build time.




