Microsoft's Six Copilots Create Pricing and Feature Confusion

Microsoft markets six distinct Copilot products with different pricing, audiences, and capabilities, leaving enterprise buyers and developers struggling to determine which product solves their specific problem.

A developer evaluates GitHub Copilot for their engineering team. An IT buyer down the hall is evaluating Microsoft 365 Copilot for the whole company. A manager googles "Copilot pricing" and gets numbers that range from $0 to $30 per user per month. All three are looking at different products. All three share a name. Nobody at Microsoft appears to have found this confusing enough to fix.

Microsoft currently sells six distinct products under the Copilot brand. They serve different audiences, solve different problems, require different procurement processes, and have pricing structures with almost nothing in common. The only thing they share is the name - and that shared name consistently derails purchasing decisions, distorts benchmarks, and produces budget conversations that are quietly off-target from the start.

TL;DR

Microsoft sells six products called "Copilot" to different audiences at vastly different price points. Developers need GitHub Copilot ($10/month). Enterprise buyers need Microsoft 365 Copilot ($30/user/month). Knowing which one you mean before comparing features or discussing budgets is not optional - it determines everything else about the conversation.

Six products, one brand

Product	Primary audience	Price	Key function
GitHub Copilot	Developers	$10/month individual, $19/month business	Code completion, chat, multi-file edits in IDEs
Microsoft 365 Copilot	Enterprise employees	$30/user/month add-on	Email drafting, document generation, meeting summaries, spreadsheet analysis
Microsoft Copilot (web/Windows)	Consumer and general users	Free ($20/month Pro)	Conversational AI with web search
Copilot in Power Platform	Business automation teams	Variable, included with some licenses	Low-code app building, workflow automation
Copilot for Azure	Cloud and DevOps teams	Included with Azure subscription	Infrastructure templates, cost optimization, diagnostics
Security Copilot	Security operations teams	Usage-based enterprise billing	Threat analysis, incident response, security posture

The pricing gap between GitHub Copilot and Microsoft 365 Copilot alone is a factor of three - and that is before considering that 365 Copilot is a per-employee add-on layered on top of existing Microsoft 365 licensing costs. A 500-person engineering team paying for GitHub Copilot spends $60,000 annually. A 500-person company licensing Microsoft 365 Copilot across all departments spends $180,000 annually on the Copilot add-on alone, before the base Microsoft 365 cost.

Where the products actually diverge

GitHub Copilot lives inside your IDE. It completes code as you type. It answers technical questions in a side panel. It handles multi-file edits. An individual developer gets value from day one without involving IT, procurement, or legal review. The product competes directly with Cursor and Tabnine. More than 1.8 million developers paid for it as of late 2025.

Microsoft 365 Copilot is an enterprise productivity layer across Outlook, Word, PowerPoint, Teams, and Excel. It summarizes email threads, drafts documents from bullet points, transcribes and summarizes meetings, and can query organizational data. An individual contributor does not buy this. The CIO's office buys it, after security reviews and contract negotiations that take weeks.

The technical integration requirements reflect this difference completely. GitHub Copilot needs your development environment and source code context. Microsoft 365 Copilot needs access to your email, calendar, documents, and Teams history. One reads code. One reads corporate communication. The permissions models, data governance requirements, and security postures are entirely different.

The core issue

GitHub Copilot and Microsoft 365 Copilot are not comparable products. Evaluating them against each other is like comparing a database query tool to a word processor because both run on company hardware. They solve different problems for different people. Treating them as variants of the same thing wastes evaluation time.

Why the naming persists

Microsoft's logic is visible if not convincing. Unified branding creates consistent market presence. It mirrors how Amazon put everything intelligent under AWS and how Google spent years attaching its name to products to signal quality. A unified brand identity across AI products theoretically builds trust faster than six separate brand names.

The strategy works when your customers naturally buy multiple products from the same catalog. AWS customers buying Lambda often also buy DynamoDB - the products cluster because they serve the same infrastructure. Microsoft's Copilots do not cluster the same way. A developer evaluating GitHub Copilot rarely has budget authority over Microsoft 365 Copilot. Those are different cost centers, different approval chains, different business justifications.

The naming also corrupts benchmarks and comparisons. An article claiming "Copilot's code generation outperformed competitors" is uninterpretable without specifying GitHub Copilot. GitHub Copilot's code completion has nothing in common with the consumer Copilot on your Windows taskbar. Benchmarked results apply to one and not the other, but the brand name obscures which.

Who should use which product

Your situation	The right product
Developer evaluating AI coding tools for personal or team use	GitHub Copilot - compare it against Cursor directly, not against 365 Copilot
Enterprise IT buyer implementing org-wide AI productivity	Microsoft 365 Copilot - different procurement model, different ROI calculation, different security review
Casual user exploring AI assistance without a paid commitment	Microsoft Copilot free tier in Edge or Windows - different product from both of the above
Team building internal automation and low-code workflows	Copilot in Power Platform - separate product, not the same as the coding or productivity tools
Cloud infrastructure and DevOps teams	Copilot for Azure - specialized, not a general coding tool despite also serving developers
Security operations and incident response	Security Copilot - standalone product with usage-based enterprise billing

The naming will not change. Microsoft has invested too heavily in the unified brand to walk it back, and the internal politics of renaming six products across six different divisions are considerable. The practical response is simple: before any conversation about Copilot features, pricing, or capabilities, establish which Copilot is actually under discussion.

When someone says "we should implement Copilot," ask them which one. The answer will often reveal that they have not fully thought through which problem they are trying to solve. That question is how clarity starts.

If you are a developer comparing coding tools, the Cursor vs GitHub Copilot comparison covers what actually matters for that decision. If you are evaluating general AI assistants, you are probably looking at the consumer Copilot product or comparing against ChatGPT or Claude - which is a different decision with different criteria entirely. Pick your product first. Then evaluate it.