Category: Microsoft Copilot, M365 | Read time: 8 minutes
Microsoft Copilot for M365 is one of the most significant productivity investments an organisation can make. At £30 per user per month on top of existing M365 licensing, it is also one of the easiest to waste money on. After deploying Copilot across multiple UK organisations, Infynex Limited has identified a consistent pattern: the implementations that fail share the same root causes, and they are all avoidable.
This post covers what those failure modes look like, what a proper deployment architecture involves, and the governance controls you need in place before a single licence is activated.
The Four Reasons Copilot Implementations Fail
1. Deploying Before Cleaning the Data Estate
Copilot is a semantic search and generation layer sitting on top of your Microsoft Graph — which means it has access to everything your users have access to. If your SharePoint permissions are overly permissive, if sensitive files are shared with “Everyone,” or if your data classification is non-existent, Copilot will surface that data to users who have no business seeing it.
We have seen this firsthand: a financial services client activated Copilot across 200 seats before conducting a permission audit. Within a week, a junior employee used Copilot to summarise a document containing board-level salary information — a document technically accessible to all staff but never practically discoverable before.
Before you deploy Copilot, run a permissions audit. At minimum:
- Review SharePoint site-level sharing settings (disable “Anyone with the link” where possible)
- Run Microsoft Purview’s Content Explorer to understand your sensitive data footprint
- Ensure Microsoft Information Protection (MIP) labels are applied to documents containing confidential, financial, or personal data
- Review OneDrive external sharing policies
2. No Prompt Engineering Training for End Users
Copilot is not magic. It is a large language model interface over your data, and like all LLMs, the quality of output is directly proportional to the quality of input. Deploying Copilot and expecting users to instinctively write effective prompts is equivalent to deploying Excel and expecting people to write pivot tables without training.
Effective prompt engineering for business contexts requires understanding:
- How to provide context (role, audience, format, constraints)
- When to use Copilot in Teams vs. Word vs. Outlook vs. Loop
- How to iterate — treating Copilot as a conversation, not a one-shot query
- What Copilot cannot reliably do (real-time data, complex multi-step reasoning, verified factual claims)
Build a prompt library for your organisation. Start with the five or ten tasks that consume the most time across teams — meeting summaries, email drafts, report generation, data extraction from documents — and write tested, reusable prompts for each.
3. No ROI Measurement Framework
This is the failure that finance directors notice. Organisations spend tens of thousands of pounds on Copilot licences and, six months later, cannot quantify the return. Without a measurement framework in place before go-live, you cannot demonstrate value — which means budget renewal becomes a political argument rather than a data-driven decision.
Before activation, define your baseline:
- Time spent on email management per week
- Time spent on meeting follow-up and action item documentation
- Time spent on first-draft document creation
- Number of meetings per week and average duration
After deployment, survey the same metrics at 30, 60, and 90 days. Microsoft Viva Insights can automate much of this if you have the appropriate licensing.
4. Treating It as an IT Project Rather Than a Change Management Initiative
The final and most common failure: Copilot lands in users’ inboxes, they use it sporadically for a few weeks, and adoption flatlines. This is not a technology problem. It is a change management problem.
Effective adoption requires:
- Executive sponsorship with visible usage — if the CTO is not using Copilot, why would anyone else?
- Copilot champions embedded in each department, not just IT
- Weekly or fortnightly prompts and use-case sharing via Teams or Viva Engage
- Celebration of wins — sharing examples of time saved or work quality improved
The Technical Prerequisites Checklist
Before activating Copilot licences, verify the following:
Licensing
- M365 E3 or E5 (or Business Standard/Premium equivalent) — Copilot requires this as a prerequisite
- Copilot for M365 add-on licences assigned in Entra ID
Identity and Access
- MFA enabled for all users — non-negotiable
- Conditional Access policies in place
- Privileged Identity Management (PIM) configured for admin accounts
Data Governance
- Microsoft Purview compliance centre active
- Sensitivity labels created and applied to high-risk content
- DLP policies configured for your regulatory context (GDPR, FCA, SRA, etc.)
- SharePoint permission review completed
Tenant Configuration
- Copilot enabled at tenant level in the M365 Admin Centre
- Plugin settings reviewed
- Microsoft Search configured and content sources indexed
End User Readiness
- Training delivered or scheduled
- Prompt library created
- Feedback channel established
- Champions identified
What Good Looks Like at 90 Days
A successful Copilot deployment at the 90-day mark shows:
- Adoption rate above 60% (weekly active users vs. assigned licences)
- Measurable time saving in at least two business processes
- Documented prompt library with department-specific examples
- A feedback loop feeding into the IT team
- A plan for expanding use cases in quarters two and three
If you are at 90 days and adoption is below 30%, the deployment has stalled. At that point, the conversation shifts from technical configuration to organisational intervention.
Summary
Microsoft Copilot is a genuinely transformative tool when deployed correctly. The organisations seeing 3x productivity uplift in specific workflows are not using different technology — they invested in the prerequisites: clean data, trained users, measurement frameworks, and change management.
The organisations wasting their licence spend skipped those steps.
If you are evaluating or planning a Copilot deployment and want an independent readiness assessment, Infynex Limited offers a structured pre-deployment audit that covers all of the above. Book a free discovery call to discuss your specific environment.
Infynex Limited is a UK-based Microsoft Partner specialising in Microsoft 365 consultancy, Copilot implementation, and AI consultancy. infynex.co.uk