Contact Book a call

Automation platforms

Power Automate consultant: Microsoft flows and Copilot Studio agents.

If your company runs on Microsoft 365, you already have some Power Automate rights, and the questions are what they cover and what the rest costs. SBD works out the licensing, builds flows and Copilot Studio agents in your tenant and sets up ownership so they keep running when someone leaves, for teams of 5 to 1,000 people.

Tool
powerautomate.microsoft.com
Usually paired with
Microsoft 365, Power Apps, Salesforce, Slack
Timeline
Most builds live in 3 to 5 business days from scope
Owned by
You, with accounts, credentials and code in your name.

What we build on Power Automate

  • Work out which flows your Microsoft 365 licences already cover
  • Build approvals across SharePoint, Outlook and Teams
  • Build Copilot Studio agents with a credit estimate first
  • Put flows in solutions with a shared owner

What we sync

  • Cloud flows
  • Desktop flows
  • Connectors
  • Solutions
  • Agents

Workflows we are asked for

  • SharePoint approval to Teams with Power Automate
  • Outlook attachment to a SharePoint record
  • Copilot Studio agent answering from staff policies
  • Power Automate flow to a non-Microsoft system by connector

Often paired with

Tools Power Automate usually needs to talk to.

What we do

What SBD would build on the Microsoft stack

We work with Power Automate, Copilot Studio, Power Apps and the wider Microsoft 365 services around them. Typical uses are approvals across SharePoint and Teams, documents arriving in Outlook and landing on the right record, and a staff-facing agent that answers from your own policies and hands anything uncertain to a person.

SBD has no published case study on Power Automate or Copilot Studio. The comparable published work is on other platforms: six fixed-scope property automations on n8n, and an enquiry platform that reads emailed RFQs with AI and works with SAP. We can show you how those were scoped, and we will say plainly where a Microsoft requirement is new to us.

Licensing

What Microsoft 365 includes and what Power Automate Premium adds

Microsoft's licensing documentation, read in November 2026, says a Microsoft 365 licence lets a user create and run cloud flows with standard connectors, up to 6,000 actions a day. Premium and custom connectors are not included. A flow that calls a premium connector therefore needs another licence, which is easy to miss when scoping a project.

Microsoft's pricing page, also read in November 2026, lists Premium at $15 per user per month and Process at $150 per bot per month, both paid yearly, and Hosted Process at $215. Microsoft notes these prices are for marketing and may differ from your list price. Premium gives a user 40,000 actions a day and one attended bot. A Process licence attaches to a flow or a machine, with 250,000 actions a day, and the flow has to be in a solution before it can be assigned.

We size this in the audit with your real volumes, as actions per run multiplied by runs per day, because the cheapest answer depends on how many people own flows and how many only trigger them.

Ownership and governance

What breaks when a flow owner leaves

Automated and scheduled flows run in the flow owner's licence context, according to Microsoft's licensing FAQ, read in November 2026. If an owner loses their Premium licence on a premium flow, the flow is downgraded, the owners are notified, and it is turned off after 14 days if nobody acts. The FAQ's route for a departing owner is to change the owner on a solution-aware flow or assign a Process licence.

So we would build flows inside solutions, with a shared owner that belongs to the team, and a runbook naming who gets the notification.

Data policies need the same attention. Microsoft's documentation on connector classification, read in November 2026, sorts connectors into Business, Non-Business and Blocked groups, and a flow cannot use connectors from two different groups. HTTP connector settings can also affect child flows, so we check your policy before designing around them.

Copilot Studio

What a Copilot Studio agent costs to run

Microsoft's Copilot Studio pricing, read in November 2026, lists packs of 25,000 Copilot Credits at $200 a month, or pay-as-you-go through an Azure subscription. Microsoft 365 Copilot at $30 per user per month, paid yearly, lets licensed users build and use internal agents at no additional cost.

Microsoft's billing rates page, dated 30 October 2026, charges 1 credit for a classic answer, 2 for a generative answer, 5 for an agent action, 10 for tenant graph grounding and 13 for every 100 agent flow actions. Reasoning models add 10 credits per 1,000 tokens, and Microsoft's own worked example reaches 141 credits for one message. A tenant on prepaid capacity has its agents blocked at 125% of that capacity, unless overage is billed to pay-as-you-go. We estimate this before building and set limits with your admin.

Power Automate cloud flows use their own licensing and do not consume Copilot Credits, so moving a fixed process out of an agent and into a flow can lower the bill.

Choosing a platform

When Power Automate is the right choice, and when it is not

Choose it when the work lives in SharePoint, Outlook, Teams and Excel, standard connectors cover it, and IT wants flows inside the tenant under its existing policies. Its desktop flows also help where an old application has no API.

Other tools are a better fit in these cases:

  • Most of your systems sit outside Microsoft and would need premium connectors. Make or n8n may cost less per run.
  • Your workflows are long, branching and need real code. n8n is easier to test and version.
  • Your agent answers a fixed list of questions. A flow with a form or a plain lookup needs no credits.
  • Nobody in the company can act as Power Platform admin. A tenant full of unowned flows is hard to keep running.

Engagement and cost

How a Microsoft engagement with SBD works

Every engagement starts with an Automation Audit at $500, credited in full to your build. We map the work, check your licences and policies, and tell you what Microsoft already covers. Workflows start at $1,500, internal tools at $3,000 and multi-module systems at $5,000, as a fixed price set after the audit. Everything is built in your tenant and stays there.

In every build

Standards we apply to every build.

Under the hood

  • Upserts keyed on the record

    Each write is matched on the source ID, so a retry or a re-fired event updates the existing record.

  • Retries with backoff

    Rate limits and timeouts are retried with increasing delays. If they still fail, they are parked for review.

  • Idempotent, loop-safe writes

    Two-way flows carry a marker so a change written by the sync does not re-trigger the sync.

  • Reconciliation

    A nightly job compares counts and totals on both sides and lists any record that differs.

  • Audit log

    Each run records the input, the mapping result, the action taken and what triggered it. You can search it by record.

For the team

  • Slack or email notifications

    Alerts go to a named person on your team, by Slack, email or WhatsApp.

  • A runbook

    One document per integration: what it does, what each alert means, and what to do in the first ten minutes.

  • Training

    A live session with the people who will use the review queue, recorded for whoever joins later.

  • Handover

    Admin access, billing and code sit in accounts in your name from the start, so the build keeps running if we stop working together.

  • Sixty days of hypercare

    The engineers who built it stay on call after go-live, fix what breaks and tune what the team asks for.

Keys and data

  • Keys are kept in a vault

    API keys and tokens are stored in the orchestration layer's encrypted credential store or the platform's secret manager. None are written into workflows, repos, spreadsheets or chat.

  • One credential per connection

    Each integration gets its own key, scoped to the objects and actions it needs. A lead sync cannot read invoices. Revoking one key stops one thing.

  • Service accounts for connections

    Connections use a dedicated service user in your account, so nothing breaks when a person leaves and nothing runs under someone's name.

  • Two-factor on every account

    Each platform account we set up has two-factor authentication on, and the recovery codes are handed to you.

  • Rotation on handover and on request

    Keys are rotated when the build is handed over, when anyone with access leaves, and at any time you ask.

The offer

Connect Power Automate to the rest of your stack.

We agree a fixed scope in a discovery call, and most builds go live in three to five business days. The accounts are in your name, and the engineers who built it stay on call for sixty days after.

  • ScopeOne call to agree the workflows, the fields and the owner, written up the same day.
  • BuildValidation, upserts, retries, reconciliation and an audit log, on n8n, Make or code.
  • Go-liveWe test in a sandbox first, then switch over. It takes longer only where a vendor has to approve something.
  • HandoverRunbook, training session, alerts to a named owner, admin access and code in your accounts.
  • AfterSixty days of hypercare, then a care plan or run it yourself.

Questions

What people ask about Power Automate.

Does Microsoft 365 include Power Automate?

Partly. Microsoft's documentation, read in November 2026, says a Microsoft 365 licence covers cloud flows with standard connectors. Premium and custom connectors need another licence.

What happens when a flow owner leaves?

Automated and scheduled flows run in the owner's licence context, so a departure can affect them. We would build flows in solutions with a shared owner, which lets the owner be changed.

Power Automate

Start with the one Power Automate workflow your team still runs by hand.

Bring it to a discovery call. You leave with a yes or no on fit, an outline of the build and what we would do first.

Book the call
A team of six gathered around one screen in an open-plan office
A discovery call with the people who own the process.

Cookie preferences

Choose what this site may use on your device. You can change this at any time from “Cookie settings” in the footer.

Strictly necessary

Keep the site working and remember the choices you make here. These cannot be switched off, and none of them track you.

Always on
What this includes (4)
NameProvider PurposeDuration
sbd-consentThis site Remembers your cookie choices12 months
Vercel Web AnalyticsVercel Inc. Counts page views in aggregate. Sets no cookie and stores nothing on your deviceNone
ticker-dismissed, sbd-note-offThis site Remembers that you closed a notice or language tipUntil the tab closes
sbd-voice-resume, sbd-voice-prefillThis site Carries a voice conversation across pages, only if you start oneUntil the tab closes

Analytics

Tell us which pages are read and where visitors leave, so we can improve them. IP addresses are anonymised and nothing is used for advertising.

What this includes (2)
NameProvider PurposeDuration
_gaGoogle Analytics (Google LLC) Distinguishes visitors with a random ID13 months
_ga_FPXDMQPRV1Google Analytics (Google LLC) Keeps the session state for this site13 months

Functional

Embedded services that set their own cookies. Without them the site still works; you get a link to open the service instead.

What this includes (1)
NameProvider PurposeDuration
Booking calendarCal.com Inc. Shows live availability and books the call on the booking pageSet by Cal.com

Advertising

Not used. This site has no advertising, retargeting or social media tracking, and we never sell data.

Not used

Questions about your data: hello@smallbaydigital.com