— The short version
It hinges on which account is signed in. Staff should always use Copilot signed in with the bank’s authenticated Microsoft 365 credentials — never a personal login. That single choice is what determines whether bank data stays safe.
Most financial institutions never budgeted for enterprise Copilot licenses across every employee — and now, at roughly $30 per user each month, it’s becoming a significant cost item: for a 100-person bank, on the order of $36,000 a year. So when a free Copilot add-in turned up inside Word, Excel, Outlook, and Teams, the leadership question wrote itself — “is the free one safe?”
There are two free versions of Copilot — the web/personal one and the Office add-ins — and they’re two very different things wearing nearly the same name. The protection your bank gets flips entirely depending on which account an employee is signed in with. As the next section shows, the protections differ sharply between the two.
Two things, one name
Telling these apart is the whole game. They can look almost identical on screen, which is exactly why the distinction gets missed.
Copilot Chat — signed in with a work account · Protected
The Copilot included free with most Microsoft 365 business subscriptions, used while signed in with the bank’s Microsoft Entra (work) account. When signed in this way, Microsoft applies Enterprise Data Protection (EDP) automatically: prompts and responses are not used to train Microsoft’s AI models, data stays within the Microsoft 365 service boundary, interactions are logged for audit, and Microsoft’s GDPR and contractual commitments apply. A green shield in the interface signals it’s active.
Consumer Copilot — personal or no account · Unprotected
The free Copilot at copilot.microsoft.com, in the Windows taskbar, or the Edge sidebar, used signed out or with a personal Microsoft account. This is a general-purpose consumer tool with no enterprise data protection, no compliance commitments, and terms under which data may be used to improve Microsoft’s models. Microsoft’s own guidance is explicit: never put sensitive or proprietary work information into it.
— The distinction
Same brand, same Copilot icon, often the same employee — but one path keeps customer data inside the bank’s protected boundary, and the other can send it somewhere the bank can neither see nor control.
The three options, side by side
Institutions can choose among three tiers. The table below lays them side by side — making the jump in both protection and capability clear, so you can decide the right path for your bank.
| Capability | Consumer Copilot | Copilot Chat | Microsoft 365 Copilot |
|---|---|---|---|
| — Tier & Cost | |||
| Tier | Free · Personal account | Free · Work account | Paid add-on |
| Cost | Free | Included with most M365 business plans | Paid per user / month |
| — Data Protection | |||
| Enterprise Data Protection | No | Yes | Yes |
| Used to train Microsoft's AI? | Possibly | No | No |
| Stays in M365 boundary | No | Yes | Yes |
| Logged for audit / eDiscovery | No | Yes | Yes (+ Purview) |
| — Capability | |||
| Works inside Word, Excel, Outlook | Chat only | Side-by-side chat in apps | Full in-app authoring |
| Reasons over your own files & email | No | Uploaded files only | Yes, under user permissions |
| Sensitivity labels & DLP enforced | No | No | Yes |
| GDPR / contractual commitments | No | Yes | Yes |
| Safe for customer data? | Never | With controls | Yes, best-governed |
The middle column is the safe, no-extra-cost starting point most banks already have. The paid tier is what adds the deeper governance — and the ability to work across the bank’s own data — that a heavier compliance posture often warrants.
Choose by your data sensitivity — and your budget
Train staff on the difference — and on safe use.
Give employees plain-language guidance on how to tell the two versions apart — a work-account sign-in and the green shield mean protected; a personal login or the public web app does not — and on what data may never be entered into either. Most rogue use isn’t malicious; it’s a well-meaning employee reaching for the nearest tool without realizing the two aren’t the same. Training, not trust, closes that gap.
Block the consumer version so the safe path is the only path.
Training sets the expectation; technical controls enforce it. Direct IT to shut the door on the consumer tool rather than relying on staff to avoid it:
- Block personal-account sign-in in Microsoft 365 apps using Tenant Restrictions v2, so a bank device can’t be used to log Office in with a personal Microsoft account.
- Restrict the consumer Copilot endpoints — copilot.microsoft.com and the consumer app — via web/app site restrictions, while leaving the work-account experience available.
- Govern the work experience in the Microsoft 365 admin center (Integrated Apps / Copilot Control System), including the tenant-level web-search and file-upload settings, rather than leaving defaults in place.
Microsoft’s controls change often, so treat this as direction for IT to verify against current documentation — the principle is fixed: make the protected, work-account version the only Copilot reachable from a bank device.
Recognize you may be ahead of regulatory and insurance guidance.
Choosing the free tier means deciding on today’s threats and practical adoption — often ahead of formal direction from your regulator or cyber-insurance carrier. That’s reasonable, but watch it: AI expectations are still forming, and both regulators and insurers lean conservative. Either could later require the deeper governance — logging, sensitivity labels, DLP — that only the paid tier provides. Document the basis for your decision now, and revisit it as guidance catches up.
— The leadership takeaway
The risk isn’t the tool — it’s the uncontrolled use of it. The free Copilot, used through the bank’s work accounts with the right controls, is a legitimate and protected starting point. The danger is the version your staff can reach in one click without thinking — the consumer tool, signed in with a personal account — which carries none of those protections and is exactly where a customer file can quietly leave the bank. The job for leadership is not to ban Copilot. It is to make sure the only Copilot your people can use for bank work is the protected one — and to back that with a clear policy, the right tenant settings, and staff who know the difference.
Six checks for leadership — make the safe path the only path
Run these with your IT and compliance leads. Hesitation on any one is the place to focus first.
Are staff signing in with work accounts?
Confirm the green-shield, EDP-protected experience is what people actually use.
Have we blocked personal-account sign-in for Microsoft 365 apps on bank devices?
Tenant Restrictions v2 closes the door rather than relying on staff discipline.
Does our acceptable-use policy name Copilot?
Which version is allowed, and what data may never go in — in writing.
Have we set tenant controls for web search and file upload?
Don’t leave Microsoft 365 admin defaults in place — configure them deliberately.
Do we need the paid tier’s governance?
Purview logging, sensitivity labels, DLP — required for higher-risk profiles.
Have staff been trained on the difference?
Plain-language guidance on protected vs. consumer versions — and on what may never be entered into either.
Educational; reflects Microsoft’s Copilot tiers and terms as of June 2026. Microsoft’s products and terms change frequently — verify current details against Microsoft’s documentation and your licensing. Not legal advice; consult qualified counsel and your primary regulator on your institution’s obligations.
