Early in 2025, I watched Microsoft 365 Copilot shift from a pilot curiosity to an everyday tool in many tenants. The turning point came in mid-January with the broad rollout of Microsoft 365 Copilot Chat. Anyone with a licence could now open the app and start prompting. People no longer had to look for the right entry point, because there was one central place for their AI assistant. In several organisations I work with, Copilot only started to make a noticeable difference to productivity from that point on, much more than the separate integrations in Word or Teams ever did. Some teams still only experimented, while others built Copilot into how they work every day. In my experience, the gap comes down to governance, security and change management, which is reason enough for an honest Copilot year in review 2025.

Copilot Chat for all raised expectations that reality did not always meet

The dedicated Microsoft 365 Copilot Chat app, launched in January 2025, changed how people used Copilot. Until then it lived mostly inside individual Office apps. Now the cross-app search and chat model moved to the front. Plenty of users who had hardly touched Copilot found real use cases, such as summarising documents, searching emails or automating small tasks. Expectations ran very high, and some people assumed Copilot would query the entire company and answer anything. That isn't how it works. Without good data quality, well-planned sensitivity labels and clean permissions, the AI is only as smart as your legacy tenant mess, and that was still true in 2025.

Practical tip: When rolling out Copilot Chat, set up meaningful usage and adoption analytics early on. That’s the fastest way to spot blind spots and target support where it’s needed.

I’ve relied on usage reports from the Microsoft 365 admin centre and Viva Insights. If you want more detail on tracking and improving adoption, see Copilot usage reports: Tracking adoption and license ROI.

Agents and the spring release brought automation and new risks

The spring release put Copilot Pages and the first agent features in the spotlight. Pages, built on Loop, gave teams a new workspace for collaboration, and agents took automation a good deal further than before. Once the first excitement wore off, the governance questions started, and permissions and oversharing quickly became the main concern. In many projects I saw agents with access far beyond what they were meant to have. The new controls in SharePoint Advanced Management turned out to be necessary very quickly. Being able to set agent permissions at a fine-grained level is a real step forward. For details, see Agents in SharePoint: Permissions, pitfalls, and admin control and SharePoint Advanced Management: Real Copilot readiness controls.

This is the simple diagram I use with customers to show how requests move between user, Copilot, agent and data:

flowchart TD
  User["User"] --> Chat["Copilot Chat app"]
  Chat --> Agent["Copilot Agent"]
  Agent --> Data["Protected Data (SharePoint, Teams)"]
  Data --> Agent
  Agent --> Chat
  Chat --> User

Figure: Simplified flow of Copilot Chat requests to agents and back. Permissions on the data matter at every step.

If you enable agents, check permissions, sensitivity labels and access paths before launch. Otherwise you will run into unpleasant surprises later.

New models like GPT-5 and Anthropic did not help every workload

Copilot also got new models in 2025. GPT-5 and the Anthropic options promised better context handling and faster answers. Several tenants tried switching models per user or per workload. In practice, routine tasks didn't always get better with the newest or most expensive model. For specialist work, such as complex research or highly sensitive data, the new models did sometimes make a real difference. Licensing, model selection and performance still have to be assessed tenant by tenant, and not everyone gains from a switch.

To keep track of model management and Copilot updates, I follow the Microsoft 365 Copilot Overview and the broader Copilot Overview. Admins should also read up on Copilot extension governance best practices.

EchoLeak, oversharing and audit findings pushed security and governance to the top

The major Copilot security topics of 2025 were prompt injection (EchoLeak in particular) and data being overshared by accident. Many organisations had to tighten their controls and work out who can see what, how SharePoint search is scoped and what Copilot actually has access to. These are the controls I have used most in practice:

  • Granular sensitivity labelling and automation reviews
  • Limiting Copilot search to specific SharePoint areas
  • Restrictive default permissions
  • Reviewing Copilot interactions in the Purview audit log

For more on getting oversharing under control, see Copilot oversharing: Blueprint priorities, site risk in practice and Restricted SharePoint Search: Copilot pilots done right. Extension governance (plugins) kept coming up as well, mostly around who builds them and how they get vetted. Microsoft did improve the admin controls (see Manage Copilot extensibility), but consistent governance is still required.

When I need to check whether Copilot touched sensitive data, I usually go to the Purview audit logs (requires E5 or Microsoft 365 Copilot licence, role: Compliance Data Admin, location: Microsoft Purview portal → Audit):

# Example PowerShell snippet: search for Copilot interactions in audit log
# Prerequisite: Compliance PowerShell module, 'Compliance Data Admin' role
Search-UnifiedAuditLog -StartDate "2025-06-01" -EndDate "2025-06-30" -Operations "CopilotInteraction"

Licence reviews and agent controls became part of Copilot management

Better usage reporting, improved licence assignment and a full year of daily Copilot use led many organisations to review their deployments. They wanted to know who actually uses Copilot and where licences sit idle. The Copilot Usage Dashboard became the main tool for keeping costs in check and planning training. For decentralised rollouts, I recommend quarterly reviews and targeted re-training for teams with low usage. You'll find the licence usage reports in the Microsoft 365 admin centre → Reports → Copilot usage. I've written more on reassignment and practical workflows in Copilot licence review: Tracking usage, reallocating smartly.

If agents are used productively, they need structured management. The new controls introduced at Ignite 2025 let you classify agents by source, permissions and approval status, which matters a lot once the first serious security audit comes around. For practical admin guidance, see Managing Copilot agents: Control, approval, and cost risks.

My takeaway is that Copilot in 2025 became routine and needs controls

Looking back, 2025 was the year the Copilot hype ran into reality. What looked like a shiny new thing in 2024 is now a normal part of Microsoft 365 for many organisations. It brings real productivity gains, but also new challenges and clear limits. The main thing I learned is that getting value from Copilot, Chat and agents at scale requires solid governance, security and licensing processes. With those in place, the benefits show up and the risks stay manageable. For 2026, I would put the focus on agent permissions, sensitivity labelling and regular usage reviews rather than chasing every new feature. Copilot will keep changing, and in my experience the groundwork and discipline always pay off.