Microsoft 365 Copilot earns its licence fee in a UK bank in five places: relationship manager meeting preparation, credit paper drafting, regulatory change monitoring, complaints handling under the Consumer Duty, and committee and board reporting. Each one is a drafting and synthesis job sitting on data the bank already holds in Microsoft 365. None of them replaces a regulated decision. This guide sets out the five use cases, the controls that make each defensible to the FCA, what the rollout costs, and the 90-day plan that turns licences into adoption.
By Toni Dos Santos, Co-Founder, Spicy Advisory — previously at BPCE, France's second-largest banking group. Last updated 31 July 2026.
Key Takeaways
- Five use cases carry most of the value in UK banking: RM meeting prep, credit analysis and credit papers, regulatory change monitoring, complaints and customer contact, and committee or board reporting. All five are synthesis and drafting work, not decision-making.
- The pattern is consistent. Copilot drafts, a named human decides. Every workflow below keeps the regulated judgement — the credit rating, the complaint outcome, the policy sign-off — with an accountable person under the Senior Managers & Certification Regime.
- UK banks are past the pilot stage. Barclays is rolling Microsoft 365 Copilot out to 100,000 colleagues after an initial deployment to around 15,000, and the Bank of England and FCA found 75% of financial firms already using AI in their 2024 survey, up from 58% in 2022.
- Permissions are the real risk, not the model. Copilot inherits Microsoft Graph permissions, so it surfaces anything a user can already reach. In banks, the failure mode is an over-shared SharePoint site, not a rogue prompt.
- Licences are around £16 per user per month, adoption is the expensive part. Microsoft lists Microsoft 365 Copilot Business at £16.10 per user per month on an annual commitment, discounted to £13.80 until 30 September 2026. The cost that decides your return is role-based training and workflow design.
- The FCA has set the direction. The Mills Review, published 6 July 2026, confirms no new AI rulebook but a higher bar on governance and evidence. Copilot use cases that produce customer-facing or credit outcomes need an audit trail from day one.
Why Copilot Behaves Differently Inside a Bank
Microsoft 365 Copilot is not a chatbot bolted onto Office. It is a reasoning layer sitting on top of the Microsoft Graph — your Outlook mail, Teams meetings, SharePoint documents, OneDrive files and Excel models — with the tenant's existing permissions applied. That architecture is why it works well in banking and why it fails badly when the underlying estate is untidy.
Two consequences follow, and both matter more in a regulated firm than anywhere else.
First, Copilot's answers are only as good as the bank's document hygiene. A relationship manager asking for a client summary gets a genuinely useful briefing when credit files, call reports and meeting notes live in structured SharePoint libraries. The same prompt in a bank running on shared drives and email attachments returns a confident, thin summary that misses the covenant breach recorded in someone's inbox.
Second, Copilot surfaces what a user can already open. It does not grant new access. But most banks have SharePoint sites that were over-shared years ago and never audited, and Copilot makes that discoverable in seconds rather than in a subject access request eighteen months later. Every rollout we have run in financial services has started with a permissions review before a single licence was assigned. Our guide to AI and data residency for UK enterprises covers the tenant-level questions that sit alongside this.
“The banks that get value from Copilot in the first quarter are not the ones with the best prompts. They are the ones that cleaned up permissions, picked two workflows per function, and told people exactly what they are allowed to do with it.” — Toni Dos Santos, Co-Founder, Spicy Advisory
The Five Use Cases at a Glance
| # | Use case | Who owns it | Realistic time saved | The control that makes it defensible |
|---|---|---|---|---|
| 1 | RM meeting prep and account reviews | Commercial / relationship banking | 2–4 hours per RM per week | Briefing is a draft; the RM verifies exposures against the source system |
| 2 | Credit analysis and credit paper drafting | Credit risk | 30–40% of first-draft time | Copilot writes narrative only; ratings and numbers come from the credit system |
| 3 | Regulatory change monitoring and policy drafting | Compliance | 1–2 days per month per analyst | Source-linked outputs; a named compliance officer signs the gap analysis |
| 4 | Complaints handling and customer contact | Operations / Consumer Duty | 20–30% of handling time | No auto-send; handler owns the outcome and the final letter |
| 5 | Committee packs, MI and board reporting | Finance / business management | 1–2 days per reporting cycle | Figures sourced from the MI system; Copilot writes commentary around them |
1. Relationship Manager Meeting Prep and Account Reviews
This is the fastest payback in most UK banks, and it is the one RMs adopt without being chased.
A commercial or business banking RM covering 60 to 120 clients spends a significant part of the week reconstructing context: what did we discuss last quarter, what did the client ask for, what has changed in the file, what is the current utilisation. That reconstruction happens across Outlook, Teams recordings, SharePoint credit files and the CRM.
What Copilot does: in Word or Teams, it assembles a pre-meeting briefing from the last twelve months of correspondence, meeting notes and stored documents for a named client, structured against the bank's own review template — relationship history, current facilities, open actions, changes since last review, questions to ask.
A prompt pattern that works: “Using my emails, Teams meetings and files relating to [Client Name] from the last 12 months, draft a pre-meeting briefing using our annual review template. Cover: relationship summary, current facilities and any changes, open actions from the last meeting, matters raised by the client, and five questions I should ask. Cite the file or email each point comes from.”
The instruction to cite sources is the part most teams miss. It converts an unverifiable summary into something the RM can check in ninety seconds.
The control: exposures, limits and pricing are read from the core system, never from Copilot. The briefing is preparation, not a record. Investec, working with Microsoft, has reported bankers saving up to 200 hours a year using Copilot for Sales in this kind of workflow, which is roughly what we see when RM prep is the first use case deployed properly rather than the fifth deployed casually.
2. Credit Analysis and Credit Paper Drafting
Credit is where banks are most nervous about AI, and the nervousness is well placed. It is also where the drafting burden is heaviest.
A credit paper for an SME facility is largely structured narrative: business overview, sector context, financial performance commentary, covenant analysis, risks and mitigants. The analytical judgement is a small fraction of the page count. The rest is writing.
What Copilot does: in Excel it summarises movements in management accounts and flags variances worth explaining. In Word it drafts the narrative sections of the credit paper against the bank's template, pulling from the financial model, the RM's file notes and prior papers. It does not produce a rating, a probability of default, or a recommendation.
The line that must not move: creditworthiness assessment of a natural person is classified as high-risk under Annex III of the EU AI Act, which matters directly for UK banks with EU operations or EU customers. The UK has taken a different route — no horizontal AI law, but the Consumer Duty and SM&CR apply in full. Under both regimes, the same discipline holds: the model drafts prose, an accountable human makes and owns the credit decision, and the file shows which is which. Our explainer on the Digital Omnibus and the revised AI Act timeline sets out what changed for firms operating on both sides of the Channel.
Practical guardrail: require the analyst to mark AI-drafted sections in the working file before submission to committee. Not as a compliance ritual — as a way of knowing, six months later, which parts of a paper were reviewed with fresh eyes.
3. Regulatory Change Monitoring and Policy Drafting
The FCA publishes consultation papers, policy statements, Dear CEO letters, portfolio letters and handbook updates at a rate no compliance team reads in full. Most banks handle this with a horizon-scanning subscription and an analyst who triages.
What Copilot does: summarises a new publication against a standard structure — what changed, who it applies to, effective dates, obligations created — and then compares it to the bank's existing policy set held in SharePoint to draft a first-pass gap analysis. With Copilot agents in SharePoint, this becomes a repeatable process rather than a one-off prompt: an agent grounded in the policy library, available to the whole compliance team.
Why this one converts sceptics: compliance teams are the most resistant population in a bank and the fastest to change their minds, because the output is verifiable. A gap analysis is either right or wrong against a document they can open. There is no ambiguity to argue about.
The control: outputs must be source-linked to the specific paragraph, and a named compliance officer signs the analysis. Copilot narrows the reading; it does not conclude. The FCA's Mills Review, published on 6 July 2026, is explicit that firms stay accountable for AI-assisted outcomes and that senior managers must be able to show the reasonable steps they took. We covered its implications in detail in our analysis of the Mills Review for UK financial services.
4. Complaints Handling and Customer Contact Quality
Under the Consumer Duty, banks have to show they are delivering good outcomes, not just following process. Complaints are where that evidence is thinnest and the manual effort is highest.
What Copilot does, in three steps:
- Summarises the case. Call transcripts from Teams, prior correspondence and case notes condensed into a factual chronology with the customer's actual complaint isolated from the surrounding narrative.
- Drafts the response. A final response letter against the bank's approved template, in plain English, addressing each point raised rather than the handler's paraphrase of it.
- Flags what a human must look at. Indicators of vulnerability, potential systemic issues, and cases where the complaint touches a product outside the handler's scope.
The control that is not negotiable: nothing auto-sends. The handler reads, corrects and owns the letter. The Financial Ombudsman Service assesses the firm's conduct, not its tooling, and “the model drafted it” is not a defence anyone has successfully run.
The second-order benefit: once complaint summaries are structured and consistent, thematic analysis across a quarter becomes possible in an afternoon rather than a project. That is Consumer Duty outcome-testing evidence produced as a by-product of doing the work.
5. Committee Packs, MI and Board Reporting
Every bank has a monthly cycle where finance and business management assemble the same pack: performance against plan, portfolio movements, risk indicators, commentary. The numbers take hours. The commentary takes days.
What Copilot does: in Excel, it identifies and explains the movements worth commenting on. In PowerPoint, it converts the approved MI into a draft committee deck against the standing template. In Word, it drafts the pre-read summary that most committee members will actually read instead of the deck.
The control: Copilot never calculates the numbers that go to a committee. Figures come from the MI system or the finance model, verified as they are today. Copilot writes the narrative around verified figures and drafts the pages. Our walkthrough of Copilot workflows for Excel and PowerPoint covers the mechanics, and AI workflows for finance teams covers the wider reporting cycle.
Where it goes wrong: teams that ask Copilot to do arithmetic on pasted data and then present the result. The failure is rarely caught in the room. Keep the calculation layer where it already is and use Copilot for the layer above it.
What Separates Banks That Get Value From Banks That Just Buy Licences
The gap between banks running the same software is not technical. It is three decisions.
They pilot before they scale. Barclays deployed Microsoft 365 Copilot to around 15,000 colleagues before committing to a rollout across 100,000 employees globally, integrating it into the bank's own colleague productivity tool rather than deploying it as a standalone app. Computer Weekly's reporting on the rollout notes that the licence sits inside an existing workflow, which is precisely why usage holds after month three.
They do not build what they can buy. Société Générale spent more than a year running SoGPT, its own internal generative AI assistant, before decommissioning it in favour of Microsoft Copilot in January 2026 — employees complained the in-house tool was falling behind, and the maintenance cost was not recoverable. That is not an argument against building; it is an argument against building the layer where a vendor ships weekly.
They train by role, not by tool. A generic “intro to Copilot” session produces a spike in usage and a collapse by week six. Training built around the five workflows above — with the bank's own templates, its own prompt library and its own approval rules — produces habits. This is the whole argument of our piece on AI training that actually sticks, and it is more true in banking than anywhere else because the cost of casual use is higher.
“Nobody in a bank has ever been fired for buying licences. Plenty of programmes have quietly died because nobody owned the workflow. Name the owner before you name the budget.” — Toni Dos Santos, Co-Founder, Spicy Advisory
The Governance Layer UK Banks Need Before Rollout
None of this requires a new rulebook. It requires the existing one applied to a new tool.
| Requirement | What it means for Copilot |
|---|---|
| SM&CR accountability | A named senior manager owns each material use case. The Mills Review is explicit that accountability does not move to the model. |
| Consumer Duty | Any use case touching customer outcomes — complaints, communications, advice support — needs outcome-testing evidence, not just process compliance. |
| Data permissions | Audit SharePoint and OneDrive sharing before deployment. Copilot inherits access; it does not create it, but it does expose it. |
| Data residency and retention | Confirm tenant configuration, EU Data Boundary settings where relevant, and how prompts and responses are retained and discoverable. |
| Shadow AI | A licensed, governed Copilot is the strongest control against staff pasting client data into consumer chatbots. See shadow AI as a governance risk. |
| Record keeping | Decide what is a record. A pre-meeting briefing usually is not. A drafted final response letter to a customer is. |
The Bank of England and FCA's most recent joint survey of AI in UK financial services found 75% of firms already using AI, with a further 10% planning to within three years, and only 2% of use cases fully autonomous. The direction of travel is assisted work with a human in the loop, which is exactly where the five use cases above sit. A fourth edition of that survey is being run in 2026. If you are building a governance framework from scratch, our UK AI governance framework guide is the practical starting point.
What It Costs and How to Build the Business Case
Microsoft lists Microsoft 365 Copilot Business at £16.10 per user per month on an annual commitment, currently discounted to £13.80 per user per month until 30 September 2026, or £19.32 billed monthly. An existing Microsoft 365 plan is required. Enterprise agreements and larger tenants price differently, and Agent 365, Microsoft's governance layer for AI agents, became generally available in May 2026 as a separate line.
The licence is not where the business case is won or lost. At £16 per user per month, a 500-seat deployment costs roughly £96,000 a year. One hour saved per user per week at a fully loaded £45 per hour is worth around £1.17m. The question is never whether the arithmetic works in a spreadsheet — it is whether usage survives contact with a busy quarter.
That is why we advise banks to fund the business case on two or three measured workflows rather than a blanket productivity claim. Measure RM prep time before and after. Measure credit paper first-draft turnaround. Measure complaint handling time and quality-assurance pass rates. Three defensible numbers beat one aspirational one, and they survive the finance director's review. If you are comparing platforms before committing, our ChatGPT Enterprise vs Copilot vs Gemini comparison covers the trade-offs for regulated firms.
A 90-Day Rollout Plan for a UK Bank
| Phase | What happens | What you should have at the end |
|---|---|---|
| Days 1–30: Ground | Permissions and sharing audit. Name a senior manager owner per use case. Pick two use cases, not five. Select 40–60 pilot users across those functions. | A clean permissions baseline, a named owner, a defined pilot cohort and a written acceptable-use standard. |
| Days 31–60: Prove | Role-based training on the two chosen workflows using the bank's own templates. Build a prompt library. Weekly office hours. Baseline and track the two metrics that matter. | Measured before-and-after on two workflows, a bank-specific prompt library, and a list of what did not work. |
| Days 61–90: Scale | Extend to the next function. Convert the best pilot users into champions. Add the third and fourth use cases. Take the evidence pack to the risk committee. | A committee-ready evidence pack, a champions network, and a scaling decision based on data rather than enthusiasm. |
The single most common mistake is skipping days 1–30 because the licences are already bought. The permissions audit is not a technicality; it is the thing that decides whether the first month generates confidence or an incident.
How Spicy Advisory Helps UK Banks Adopt Copilot
We are not a Microsoft reseller and we do not run awareness theatre. We work with banks, building societies and financial firms across the UK on three things:
- Readiness and adoption audit. Where you actually sit — current and shadow AI usage, permissions exposure, SM&CR and Consumer Duty gaps, and the two or three workflows where Copilot pays back fastest and safest. Start with the free AI self-audit or a free audit call.
- Role-based training for regulated teams. Hands-on AI training for financial services built around your approved tools, your templates and your approval rules — for RMs, credit, compliance, operations and leadership. Delivered in person in London and across the UK.
- Governance and scaling strategy. AI strategy consulting to build the operating model the Mills Review implies: named ownership, human-in-the-loop checkpoints, prompt and evidence libraries, champions, and metrics that hold up in front of a risk committee.
Find Out Where Your Bank Actually Stands
Most banks know they have Copilot licences. Far fewer know which teams use them, on what data, with what controls. Our free self-diagnostic gives you a readiness score and the three highest-value workflows for your firm in under ten minutes. Or bring your situation to a call and we will tell you straight whether you have an adoption problem or a governance one.
Run your free AI self-audit Book a free audit callFrequently Asked Questions
What are the best Microsoft Copilot use cases for banks?
The five highest-value Microsoft 365 Copilot use cases in banking are: relationship manager meeting preparation and account reviews; credit analysis and credit paper drafting; regulatory change monitoring and policy gap analysis; complaints handling and customer correspondence under the Consumer Duty; and committee, MI and board reporting. All five are synthesis and drafting tasks performed on data the bank already holds in Microsoft 365, and all five keep the regulated decision with an accountable human.
Is Microsoft 365 Copilot safe for a regulated UK bank to use?
Yes, with configuration. Copilot operates inside the bank's Microsoft 365 tenant and inherits existing Microsoft Graph permissions, so it does not grant users access to data they could not already open. The practical risk is over-shared SharePoint and OneDrive content becoming easily discoverable, which is why a permissions audit should precede deployment. Banks also need to confirm data residency settings, retention and discoverability of prompts and responses, and assign a named senior manager to each material use case under the SM&CR.
Can Copilot make credit decisions?
No, and it should not be configured to. Copilot can draft the narrative sections of a credit paper, summarise management accounts and flag variances, but the rating, the probability of default and the lending decision must come from the credit system and an accountable human. Creditworthiness assessment of individuals is classified as high-risk under Annex III of the EU AI Act, and in the UK the Consumer Duty and Senior Managers & Certification Regime hold the firm and a named individual accountable for the outcome regardless of what drafted the document.
How much does Microsoft 365 Copilot cost in the UK?
Microsoft lists Microsoft 365 Copilot Business at £16.10 per user per month on an annual commitment, with a promotional rate of £13.80 per user per month running to 30 September 2026, or £19.32 per user per month billed monthly. An existing Microsoft 365 plan is required. Enterprise agreements price separately, and Agent 365 — Microsoft's governance layer for AI agents, generally available since May 2026 — is a separate subscription. For most banks the licence is a small fraction of total cost; training and workflow design determine the return.
Which UK banks are using Microsoft Copilot?
Barclays is the most publicly documented UK deployment, rolling Microsoft 365 Copilot out to 100,000 colleagues globally after an initial deployment to around 15,000, and integrating it into the bank's existing colleague productivity tool. Across the sector more broadly, the Bank of England and FCA's joint survey found 75% of UK financial services firms already using AI, up from 58% in 2022, with a further 10% planning adoption within three years. In France, Société Générale decommissioned its in-house SoGPT assistant in favour of Microsoft Copilot in January 2026.
What does the FCA Mills Review mean for Copilot deployments?
The Mills Review, published by the FCA on 6 July 2026, does not create a new AI rulebook but raises the bar on governance, oversight and the evidence firms must be able to produce. For a Copilot deployment this means three things: each material use case needs a named senior manager under the SM&CR; use cases touching customer outcomes need Consumer Duty outcome-testing evidence rather than process compliance alone; and senior managers must be able to demonstrate the reasonable steps they took as work is delegated to AI.
How long does a Copilot rollout take in a bank?
Plan 90 days to a defensible scaling decision. Days 1 to 30 cover the permissions and sharing audit, naming senior manager owners, selecting two use cases and a pilot cohort of 40 to 60 users. Days 31 to 60 cover role-based training on the bank's own templates, building a prompt library and baselining metrics. Days 61 to 90 extend to the next function, convert pilot users into champions and produce an evidence pack for the risk committee. Skipping the first 30 days because licences are already purchased is the most common cause of failure.
Why do Copilot rollouts fail in financial services?
Three reasons dominate. First, licences are distributed without a permissions audit, so early results are either thin or expose over-shared content. Second, training is generic rather than built around specific banking workflows, producing a usage spike that collapses within six weeks. Third, no single person owns the workflow, so nobody is accountable for whether it is used. The fix is narrow and unglamorous: clean permissions, two workflows per function, a named owner, and training delivered on the bank's own templates and approval rules.