A UK firm on Microsoft 365 has two AI-adjacent tools in its existing estate. Power Automate builds workflows between Microsoft and third-party systems on triggers and rules, with standard connectors in many Microsoft 365 licences and premium connectors and unattended automation on a per-user or per-flow licence. Copilot Studio builds agents and custom copilots over the firm’s SharePoint, Teams and Dynamics data, priced on pooled message credits at tenant level rather than per seat, with some capacity included in Microsoft 365 Copilot licences. A small firm can sensibly build itself the approval flows, notifications and simple document routing in Power Automate, and a staff-facing Q&A agent over a SharePoint library in Copilot Studio. Where it stops is customer-facing agents with real integrations, anything needing an accuracy threshold and audit trail, and volumes where message credits become the bill; there a fixed-price build on the same Microsoft estate, owned by the firm, is usually cheaper and more controllable.
- Power Automate
- Workflows; per-user or per-flow licences
- Copilot Studio
- Agents; pooled message credits
- Build yourself
- Approvals, notifications, a staff Q&A agent
What each tool is
Power Automate is Microsoft’s workflow tool: when a form is submitted, a file arrives or a record changes, do these steps across Microsoft 365, Dynamics and hundreds of third-party connectors. Standard connectors come with many Microsoft 365 licences; premium connectors, unattended desktop automation and higher limits need Power Automate Premium per user or a per-flow licence, listed in pounds on Microsoft’s UK pricing page. Copilot Studio is the tool for building agents: a custom copilot that answers from a SharePoint library, or an agent that takes actions through connectors, published to Teams or a website. It moved from per-message to pooled credits in 2025, bought in packs at tenant level, with premium actions consuming more credits, and Microsoft 365 Copilot licences include some capacity for internal agents.
What a small firm can build itself
Power Automate: approval flows for holiday, expenses and purchase requests; notifications when a form is submitted or a file lands; routing documents into the right SharePoint folder with metadata; simple syncs between Microsoft lists and a CRM. Copilot Studio: a staff-facing agent that answers questions from the policies and procedures in a SharePoint library, published in Teams, with sources shown. These are the equivalents of the workflow tools in our n8n, Make and Zapier guide, inside the Microsoft estate, and for a firm with someone willing to maintain them they are a sound first step.
Relatedn8n, Make, Zapier or custom automation A knowledge assistant on your own documents
Where it stops
Four places. Customer-facing agents with real integrations into bookings, orders or accounts, where the connectors run out or the credits per conversation become the bill. Anything that needs an agreed accuracy threshold measured on your own inputs, an exceptions path a person works every day, and an audit trail a client can inspect. Volume: pooled credits at tenant level are simple until a successful agent is used a great deal, at which point the effective cost per conversation needs the same worked example as any credit-priced platform. And ownership: what is built inside a platform stays inside it, so the runbook and the portability questions apply.
RelatedRPA, workflow automation or an AI agent? AI vendor due diligence checklist What an AI customer service chatbot costs
When a build on the same estate is better
A fixed-price build can run on the firm’s own Azure subscription, using the same Microsoft identity and data, with the model of the firm’s choosing, Claude, GPT or another, behind it. It costs £4,000 to £15,000 for a first implementation and £8,000 to £25,000 for a custom system, with the running cost stated per unit rather than in credits, the accuracy threshold measured before go-live, least privilege and logging designed in, and the code and accounts in the firm’s name. That is the right answer once the process is customer-facing, integrated or high-volume, and the Power Automate and Copilot Studio work done first is not wasted, because the process it mapped is what gets built properly.
RelatedHow much AI automation costs in the UK Your data when a supplier builds your software Custom AI solutions
The data position
Both tools operate inside the Microsoft 365 boundary under the firm’s existing Microsoft terms and data processing addendum, and respect the firm’s permissions, which is their strongest argument for a regulated or cautious firm. The policy still applies: which agents may reach which libraries, what goes to a person, and who reviews the agent’s answers. And the same Cyber Essentials expectation applies to these as to any cloud service the firm administers.
Common questions
What is the difference between Power Automate and Copilot Studio?
Power Automate builds rule-based workflows between systems on triggers. Copilot Studio builds agents and custom copilots that answer questions or take actions using a model. Most processes need the first; a few need the second.
How is Copilot Studio priced?
On pooled message credits at tenant level, bought in packs, with premium actions consuming more, and some capacity included in Microsoft 365 Copilot licences. Work the example at your expected volume.
Is Power Automate included in Microsoft 365?
Standard connectors are included in many licences. Premium connectors, unattended automation and higher limits need Power Automate Premium per user or a per-flow licence.
Can a small firm build its own AI agent in Copilot Studio?
A staff-facing Q&A agent over a SharePoint library, yes. Customer-facing agents with real integrations, thresholds and audit trails are where a build is usually better.
Is Copilot Studio secure for client data?
It runs inside the Microsoft 365 boundary under your existing terms and permissions, which is a strong position. Govern which agents reach which libraries and who reviews their answers.
Do we need a Power Automate consultant?
Not for a simple flow between two Microsoft apps, which a confident member of staff can build. A Power Automate consultant earns the fee when flows need premium connectors, unattended runs, error handling and someone accountable for them, or when the job is better built outside the platform altogether.
When should a Microsoft firm commission a build instead?
When the process is customer-facing, needs integrations beyond the connectors, needs a measured accuracy threshold and audit trail, or when credits at volume exceed a fixed-price build you would own.