AI and automation
Copilot
Microsoft 365 Copilot
Microsoft 365 Copilot is Microsoft's generative AI assistant embedded directly into the Office and Teams applications, Word, Excel, PowerPoint, Outlook, Teams, and the standalone Copilot Chat experience.
Why Copilot matters in a Microsoft estate
Copilot matters when teams want AI support without losing control of identity, data, approvals, and audit evidence. In the EfficientEther portfolio, AI terms usually connect to governed workflows, Copilot readiness, or agentic packaging where humans still review important outputs.
How Copilot shows up in practice
It uses large language models combined with the Microsoft Graph to answer questions, draft and summarise content, and generate insights grounded in a user's own emails, documents, meetings, and chats rather than only general knowledge. Its defining architectural feature, and the one with the most direct operational consequence for IT teams, is that Copilot answers strictly within the data a given user can already access through their existing Microsoft 365 permissions: it does not grant new access to anything, but it also does not add any new restriction beyond what already exists.
That means Copilot is only as safe as an organisation's underlying SharePoint, OneDrive, and Teams permission model already was, and years of accumulated over-sharing, broad "Everyone except external users" links, stale site permissions, oversized security groups, that were a low, mostly theoretical risk when finding an over-shared file required someone to manually search for it become a materially higher risk once Copilot can synthesise and surface that same content instantly in response to a normal question. This is why Copilot rollouts that skip a permissions and data governance review before enabling licences are one of the most consistently flagged mistakes in early Microsoft 365 Copilot deployments, and Microsoft Purview's sensitivity labelling, data loss prevention, and the specific Copilot-related oversharing assessment tooling exist largely to close that exact gap before, rather than after, Copilot is switched on broadly.
Licensing is a distinct commercial consideration from the AI features bundled into other Microsoft 365 tiers: Microsoft 365 Copilot is a separate per-user add-on licence on top of an existing qualifying Microsoft 365 plan, priced at a level that makes usage justification a genuine ongoing question rather than a one-off purchasing decision.
Adoption tracking, whether licensed users are actually using Copilot regularly across the apps it's enabled in, is one of the more common areas where organisations discover meaningful licence waste months after a rollout, since it's straightforward to assign a Copilot licence during onboarding and considerably less straightforward to notice, without deliberate usage reporting, that a meaningful share of licensed users never adopted it. Copilot also exists in variants beyond the core Microsoft 365 experience worth distinguishing, including Copilot Chat, a lighter-weight, more limited experience available without the full per-user Copilot licence, and Copilot Studio, a separate product for building custom agents rather than the assistant itself. Conflating these different Copilot products during budgeting or planning is a common and avoidable source of licensing confusion.