microsoft 365

Automate Microsoft 365 with what you already have

AA
Aurum Avis Labs Author
8 min read

Automate Microsoft 365 with what you already have

You can automate Microsoft 365 with Forms, Lists, Outlook rules, Teams approvals, Bookings and Power Automate while standard connectors are enough.

If your firm pays for a Microsoft 365 business plan, you can automate a fair share of office work without buying anything else. Forms collects requests in a fixed shape, Lists keeps the register, Outlook rules sort mail, the Approvals app in Teams records a yes or no, Bookings takes appointments, and Power Automate connects them with standard connectors. Premium connectors, desktop automation and flows tied to one person’s account are the usual limits.

This is for owners, office and finance leads in Swiss SMEs that already work in Outlook, Teams and SharePoint and want to know what they can set up themselves before they commission anything. If your question is really whether Copilot will do it, that is a different purchase. Copilot helps a person draft inside the apps. A flow moves data when nobody is typing. That fork is in a Copilot licence or a built workflow.

Power Automate on your plan: what is included

Microsoft’s plan comparison lists Forms, SharePoint, Bookings (in the versions that include Teams) and Power Automate cloud flows in Business Basic, Business Standard and Business Premium. Microsoft Lists is not named there, but a list can be created on a SharePoint site, and SharePoint is part of all three plans. The Power Automate rights are limited, though. According to Microsoft’s overview of seeded licences, Microsoft 365 users may create and run cloud flows with standard connectors, with a daily limit of 6,000 actions per user. The connectors for Forms, SharePoint (which reaches lists on a SharePoint site) and Bookings are all standard.

ToolOn its ownWith a flow
Microsoft FormsCollects a request in the same fields every time: a holiday request, an order, a damage reportEach new response starts the next step
Microsoft ListsA shared register with columns and views: open requests, orders, defectsA new or changed entry triggers a notification or an approval
Outlook rulesMoves, flags or answers mail automatically when a condition matches, for example words in the subjectRarely needed for plain sorting
Approvals in TeamsSomeone asks, someone decides, the answer is recordedA flow starts the approval and waits for the decision
Microsoft BookingsCustomers pick a free time and get a confirmationA flow reacts when an appointment is created, changed or cancelled

Two details belong in the plan. Microsoft notes that certain Outlook rules only run when Outlook is open, so anything that has to run over the weekend is safer in a flow. And the Approvals app stores approvals in the default Dataverse environment of your organisation. Users need a Power Automate, Microsoft 365 or Dynamics 365 licence, and whoever sets up approval templates also needs Forms.

A worked example: holiday requests without mail ping-pong

An example, not a client: a planning office with around 20 people. Holiday requests arrive by email, the team lead answers when she finds the mail, and the office keeps a spreadsheet that is never quite current. Everything needed to fix this is in the plan the office already pays for.

  1. A form instead of a mail

    A Microsoft Forms form asks for name, dates, half or full days and a note. The same fields every time.

  2. An entry in a list

    A Power Automate flow starts on each new response and writes it into a list with the status “requested”.

  3. An approval in Teams

    The same flow sends an approval to the team lead in Teams. She approves or rejects with a comment, on her phone if need be.

  4. Status and answer

    The flow sets the list entry to approved or rejected and sends the requester an Outlook mail with the decision.

  5. One view for the office

    The office filters the list by month. The spreadsheet goes.

All five steps run on standard connectors, so no extra licence is needed. What stays manual: the decision itself, the odd exception such as a request in the middle of a deadline, and entering the absence in payroll or HR software if that sits outside Microsoft 365. If someone in the office is comfortable with Power Automate, this can be set up internally. Then you do not need a provider for it.

Where the included licence stops

The included rights stop at the edge of Microsoft’s standard connectors. Microsoft’s licensing FAQ states that users on a Microsoft 365 plan can only access standard connectors. Four limits come up most often in small offices.

Premium connectors. Many connectors to systems outside Microsoft are premium, the SQL Server connector for example. If an instant flow uses a premium connector, every user who runs it needs Power Automate Premium, or the flow gets its own Process licence, according to the same FAQ. Premium costs CHF 12.10 per user and month on annual billing, excluding VAT, on Microsoft’s Swiss price page at the time of writing.

Custom connectors and the on-premises gateway. If your ERP or industry software has an API but no ready-made connector, the usual route is a custom connector. According to the same overview of seeded licences, that is not part of the Microsoft 365 rights, and neither is the gateway to a server in your own office. Whether your program offers an interface at all is something we look at in the Process Check.

Desktop automation. Having a flow click through an older Windows program (robotic process automation) is not included in the Microsoft 365 rights either, according to the same overview.

Flows on Bookings. The Bookings connector lists its own limits: only Bookings admins can create flows with its appointment triggers, and each Bookings mailbox allows five flows.

When one person holds all the flows

The risk that bites small firms is rarely the licence. It is ownership. A flow is created in someone’s account, and its connections usually sign in as that person. Microsoft’s guidance on flows whose owner has left says such flows can fail if they use connections tied to that account.

Three habits cover most of it. Add a second owner to every flow the business relies on. Keep one page listing each flow: what it does, what starts it, whose account its connections use. And decide who is told when a run fails. A flow that stops quietly is worse than the manual job it replaced, because people keep trusting the result.

Complex logic is the other limit. A flow with a handful of steps can be read by the next person. A flow with nested conditions, loops over attachments and a dozen exceptions often cannot, not even by whoever built it six months ago. When the rules no longer fit on one page, write them down and decide whether this is still a job for an evening in Power Automate.

What we built on Microsoft 365 ourselves

Aurum Avis Labs runs on Microsoft 365, and the booking page for the Process Check is built on it. The page reads free slots from Microsoft Bookings through Microsoft Graph. The Process Check is free, so booking it does not go through Stripe. A flow that creates the appointment only after payment is in automating appointment booking with payment.

That is the fork this article is about. Bookings, Teams and Outlook do most of the work. The part Bookings cannot do, taking payment first, needed code that talks to Microsoft Graph directly. And that kind of code has its own upkeep: the secret an app uses to reach Graph lasts 24 months at most, according to Microsoft, and someone has to renew it in time.

When the included tools are enough

They are enough when every system involved sits inside Microsoft 365, the rules fit on one page, and someone internal owns the flow and has a deputy. Holiday requests, a register of incoming orders, a reminder when a list entry has waited too long, a Bookings confirmation that also posts to a Teams channel: all of that is do-it-yourself territory.

  • Do input and output stay entirely inside M365?
  • Does the logic fit on one page without nested exceptions?
  • Is there a second owner on every production flow?
  • Do you know who is told when a run fails?

Get help when the data has to reach a system with no standard connector, when the logic has more exceptions than rules, or when nobody internal can look after it. Sorting a shared inbox by customer or case is a typical example. Outlook rules follow fixed conditions, such as words in the subject line. They do not read a mail and judge where it belongs. That case is in sorting emails in a shared inbox.

When the Process Check fits

The Process Check fits when you have one recurring task that is still done by hand and want to know whether Microsoft 365 alone covers it or whether it needs an implementation. Thirty minutes on Microsoft Teams. The Process Check is free. You leave knowing where to start, whether it pays off, and with a price range for the implementation. The half hour may well end with “set this up yourself in Power Automate”. Then you have that in writing.

If you already know which task it is, start with the Process Check page.

microsoft 365 power automate process automation
AA

Written by

Aurum Avis Labs

Builds and ships at Aurum Avis Labs. Writes here about what we learn working with founders and SMEs in the DACH region.

Customize your cookie preferences. Essential cookies cannot be disabled as they are required for the website to function properly.

Essential Cookies

Required for basic website functionality, security, user authentication, and error tracking.

Always active

Analytics Cookies

Help us understand how visitors interact with our website to improve user experience. Includes Google Analytics and Microsoft Clarity session recordings.

Marketing Cookies

Used to track visitors across websites to display relevant and engaging advertisements.