Build finance and operations agents on your own Microsoft stack
Copilot Studio lets you build AI agents that run inside your Microsoft 365 tenant, governed by the agreements you already have. We help finance and operations teams design, build and govern those agents, and we get the EU data residency settings right, including the 2026 changes most teams have not noticed.
The short version
Agents that live in your tenant, not a vendor’s
Copilot Studio is Microsoft’s low-code tool for building custom AI agents on the Power Platform and Dataverse. The agents you build run inside your own Microsoft 365 tenant and inherit the data processing terms you already signed with Microsoft. For a finance team, that is a meaningfully different starting point from pasting numbers into a consumer chatbot.
In 2026 the platform matured fast. Computer-using agents, agent-to-agent workflows and apps inside agents are generally available, and Microsoft Agent 365 gives administrators a single place to govern every agent in the estate. That makes Copilot Studio a credible way to automate real finance and operations work, provided it is set up with governance and residency in mind from the start.
What we build
Copilot Studio agents for finance and operations
We focus on workflows anchored in data you already hold in Microsoft 365 and Dynamics 365, where a native agent removes manual effort without adding a vendor.
Reconciliation prep agents
Agents that pull, match and flag exceptions across bank, ledger and sub-ledger data held in Dataverse and Excel, ready for a human to approve.
Variance and reporting commentary
Agents that draft first-pass variance commentary and board narrative from your D365 and Power BI data, in your tenant.
AP and approval routing
Agents that triage invoices, check them against policy, and route approvals through Teams without a separate AP platform.
Operations workflow agents
Agent-to-agent workflows that move work across functions, from procurement intake to fulfilment status, using your existing connectors.
Already on Dynamics 365? See our D365 F&O consulting, or read our practical Microsoft Copilot for finance setup guide.
The autonomous end of the spectrum
Copilot Cowork, and the skill that actually matters now
Copilot Studio is for agents you design. Copilot Cowork, generally available since 16 June 2026, is the other shape: you hand it a whole multi-step job, it works across your apps, files and the web on its own, and it hands back the finished output rather than a draft you spend an hour fixing.
In our own use, the change is real: work that used to block out half a day finishes in roughly an hour while you get on with something else. The new skill is not prompting. It is judgment, knowing which work belongs to an agent and which does not. Quick questions, meeting summaries and light edits stay in ordinary Copilot. The heavy, multi-step jobs go to Cowork.
Good first jobs for a finance or operations team: an agent that researches a company, market or competitor and returns a one-page briefing; one that turns the week’s meeting transcripts into a clean list of what was promised, what is open and who owes what by when; or a first-draft proposal or report built from your own templates. The bigger prizes, checking contracts against policy or building the board narrative from your numbers, touch your most sensitive data, so we hold those until the residency question below is settled.
Generally available
Since 16 June 2026, worldwide
Metered, per task
Needs pay-as-you-go or prepaid on top of a Copilot licence
Off by default
Spend controls at tenant, group and user level
Frontier grace period
Preview tenants not billed until 1 July 2026
Cowork’s advanced agent work runs on Anthropic’s Claude models, which brings us straight to the question every finance leader should ask first.
The part most teams miss
Where does your finance data actually go?
This is the question a chartered accountant asks before anyone builds anything. With the Microsoft stack the answer is good, but it changed twice in 2026 and the defaults moved. Here is the current picture, in plain terms.
Native Copilot Studio agents can stay in the EU Data Boundary
If your tenant has an EU or EFTA billing address and all your environments are created in an EU region, Copilot Studio is in scope for the Microsoft EU Data Boundary. Native agents running on Azure OpenAI keep both data at rest and, by default, processing within that boundary. For most regulated finance workloads this is the right starting configuration.
Flex Routing changed the default on 17 April 2026
Microsoft 365 Copilot “Flex Routing” (message centre item MC1269223) was enabled by default and permits Copilot language model processing to move outside the EU Data Boundary during peak demand. Data at rest stays encrypted within the EU, and only limited pseudonymised data may be stored outside. But if you require strict EU residency, an administrator must actively disable Flex Routing and document that decision. Many teams have not checked.
Choosing Claude or ChatGPT changes your residency position
Microsoft now lets you select Anthropic Claude models in Office apps and Copilot Studio, and Claude is available in Microsoft Foundry. As of mid-2026, Anthropic models are out of scope for the EU Data Boundary, run on Anthropic-hosted infrastructure rather than Azure EU regions, and EU support is listed as coming during 2026. For EU and UK tenants these models are excluded from the default rollout and an admin must opt in explicitly. The capability is genuinely strong; the point is to choose it deliberately, with your DPO informed.
Microsoft’s platform and policies change frequently. We verify the current position with your tenant settings and Microsoft’s documentation as part of every engagement, rather than relying on what was true last quarter.
Choosing well
Native Microsoft AI vs opting into Claude or ChatGPT
There is no single right answer. We help you match the choice to the workload and your regulatory position.
| Native Copilot Studio (Azure OpenAI) | Opting into Claude / ChatGPT | |
|---|---|---|
| EU Data Boundary | In scope when tenant and environments are EU-configured | Anthropic models out of scope as of mid-2026; EU support coming |
| Where it runs | Your Microsoft tenant and Azure EU regions | Anthropic-hosted infrastructure (for Claude), opt-in required |
| Data agreement | Your existing Microsoft terms cover it | Review needed; treat as a deliberate addition |
| Best for | Data-bound finance work: reconciliation, reporting, approvals | Heavier free-form reasoning and drafting tasks |
| Setup effort | Lower; native to your stack | Higher; admin opt-in plus governance review |
For a fuller side-by-side of the tools themselves, read ChatGPT vs Copilot vs Claude for finance.
How we engage
Audit, build, govern
Audit
We review your finance and operations workflows, your Microsoft licensing and your tenant configuration, then pick two or three agents that pay back fast.
Build
We build the agents in Copilot Studio against your Dataverse and Microsoft 365 data, with residency and governance settings configured correctly from the start.
Govern and train
We set up administration through Microsoft Agent 365, document the data position for your DPO, and train your team to maintain and extend the agents.
Questions
Copilot Studio for finance FAQ
Build agents you can take to the auditors
Book a consultation and we will review your Microsoft stack, find the highest-value Copilot Studio agents for your finance and operations teams, and tell you exactly where your data goes.