Microsoft’s Copilot branding has reached a point where even careful observers are struggling to keep score, and the best public count now sits at about 80 distinct products, services, and features carrying the name. That total, mapped by AI strategy consultant Tay Bannerman from product pages, launch posts, and marketing materials, is less a neat statistic than a warning sign: Microsoft has turned Copilot into a sprawling umbrella for everything from Windows and Microsoft 365 to developer tools, cloud services, hardware branding, and custom agent platforms. The scale is impressive, but the clarity problem is becoming impossible to ignore. osoft’s Copilot push began with a simple promise: make generative AI feel like a natural part of everyday computing. The company first positioned Copilot as a productivity companion inside the software people already knew, especially Windows and Microsoft 365, where it could summarize, draft, search, and automate without forcing users into a wholly new interface. That strategy was appealing because it matched the way Microsoft has always won: by making new capabilities feel native rather than bolted on.
Over time, though, boundaries of a single assistant. Copilot became a label attached to consumer chat, workplace copilots, security tools, developer services, device categories like Copilot+ PC, and the builder layer behind custom AI solutions such as Copilot Studio. Microsoft’s own official documentation now frames Microsoft 365 Copilot as a work assistant that sits across Word, Excel, PowerPoint, Outlook, and Teams, while also connecting to Microsoft Graph, search, and enterprise controls. That makes Copilot less a product and more a naming system for an entire AI stack.
The problem with that naming system is not that it lacks ambition. It is that the ambition has outgrown user comprehension. Bannerman’s public mapping effort reportedly started because he could no longer explain what “Copilot” meant without first sorting through Microsoft’s various implementations. His chart had to be built manually because Microsoft does not publish a single official catalog, and that alone says a lot about how fragbecome.
Microsoft has also continued to expand the Copilot idea at a product pace that makes simplification harder, not easier. In March 2026, Microsoft described the next wave of Microsoft 365 Copilot as more agentic, more integrated, and more model-diverse, with capabilities embedded directly into Word, Excel, PowerPoint, Outlook, and Copilot Chat. That is a powerful vision, but it also deepens the challenge: every new extension strengthens the ecosystem while making the umbrella name more overloaded.
The result is a classic Microsoft tension. The company wants a brand that signals everything AI to consumers and enterprises at once. But the broader the brand gets, the more it risks losing the very specificity that made it useful in the first place. As one community comparison put it, the current Copilot spread recall branding of the early 2000s, when the label was attached to nearly everything Microsoft touched.
The number itself is not the story; the organizational behavior behind it is. An 80-product count suggests that Microsoft’s internal teams are shipping quickly and often, and that many groups see value in tagging their work with the Copilot name. That kind of proliferation usually happens when ale brand to capture a fast-moving category before rivals define it for them.
That breadth gives Microsoft an enormous distribution advantage. If Copilot becomes the default AI word attached to Microsoft products, then the company wins mindshare before a purchase decision even begins. But breadth also creates a comprehension tax. Users can recognize the term instantly and stihey are looking at a chatbot, a licensing tier, a developer toolkit, or a policy-controlled enterprise feature.
The key issue is that Microsoft has already reached the stage where “Copilot” can mean too many different things in one conversation. That is not just a branding problem; it is a support problem, a sales problem, and a training problem. It makes documentation harder to navigate and dn. It also increases the odds that enterprises buy something they do not fully understand.
This matters because a brand that keeps adding new nodes without pruning old ones can become self-defeating. Growth is good when the category is still forming. But once the market starts asking for clarity, more names can become less helpful than fewer, bicrosoft seems to be learning that the hard way.
This is where the strategy gets clever. A platform layer creates switching costs. Once a buss, automations, and internal habits around Microsoft’s Copilot tooling, moving away becomes harder. Microsoft is not just trying to sell AI prompts; it is trying to sell an operating layer for work.
Still, platform logic can collide with user logic. Users do not want to learn a taxonomy of Copilots. They want to know which one helps themge a cloud workload, automate a support queue, or buy a device. The more Microsoft behaves like a platform company, the more it must behave like a product education company too.
Azure extends that logic into infrastructure. Microsoft’s own documentation and product pages position C cloud operations and development stack, where organizations can integrate AI into business systems and workflows. That means the Copilot name is not just a consumer-facing label; it is now a wrapper over enterprise plumbing.
Microsoft still has to answer
The average person does not care how many Copilots exist. They care which one they should open and what it can do. That is where the current strategy gets shaky. If a brand creates recognition without comprehension, it becomes a logo first and a product second.
Microsoft has tried to make Copilot feel ubiquitous, but ubiquity can backfire when it looks like repetition rather than usefulness. A brand that appears everywhere may seem dominant, yet if each appearance requires a different explanation, trust erodes. That is especially true for AI, where users already worry about correctness, privacy, and hidden behavior.
The company’s revised behavior on some integrations suggests it recognizes this risk. Reports say Microsoft backed away from integrating Copilot into system notifications after negative reaction, a move that reads like a small but important concession: not every surface should become a Copilot surface.
That said, the name still matters. A procurement team trying to understand whether it is buying a chatbot, a reporting feature, a security copilot, an agent runtime, or a full workflow platform may spend extra time untangling Microsoft’s labels before making a decision. That friction can slow adoption even when the underlying technology is sound.
There is also a licensing problem. Copilot has become not just a product family but a packaging system, and packaging systems are only elegant when they are easy to explain. Microsoft’s recent push toward more agentic offerings underscores that the company is increasingly selling outcomes, not just access. That can be good for revenue, but it can also make budget conversations more opaque.
It also helps Microsoft compete on more than model quality. In enterprise AI, distribution and governance often matter more than who has the flashiest demo. Microsoft’s advantage is that it can package AI where companies already work, and that makes the Copilot brand strategically valuable even when the naming is messy.
But the desktop is also where users are least forgiving. If an AI feature slows the system, adds clutter, or behaves unpredictably, people notice immediately. Unlike cloud services, Windows is visible every minute, and that means Copilot’s reputation can be shaped by memory use, UI friction, and architectural choices as much as by capability.
That sensitivity helps explain why Microsoft has occasionally pulled back. The reported decision to remove Copilot from certain notifications after user backlash suggests the company understands that OS-level AI cannot feel invasive if it wants broad acceptance. The desktop rewards restraint more than hype.
The broader issue is that Windows users already worry about bloat, background processes, and hidden complexity. If Copilot is associated with browser wrappers, memory overhead, or extra prompts, the brand can pick up the wrong kin In the consumer market, convenience has to feel lightweight, not merely powerful.
Still, rivals can exploit Microsoft’s naming confusion. Simpler brands are easier to explain, and in AI markets where many buyers are still learning what these tools do, clarity can beat completeness. If a competitor can explain its value in one sentence while Microsoft requires three, the simpler story may win the first meeting.
There is also soft has been pushing harder into agentic AI, with recent announcements around more advanced Copilot behavior, Work IQ, and agent management concepts. That suggests the company believes the market is moving from chat to execution. If that proves true, Copilot’s brand sprawl may be judged less harshn a pure chatbot era.
The competitive question, then, is whether Microsoft can turn Copilot into a trusted categoe label will become so overloaded that it loses meaning. That is a big strategic fork, because category ownership is valuable only if the category still communicates something clear.
This is why some users have reacted so strongly to Microsoft’s AI branding. They are not merely resisting AI; they are resisting ambiguity. When aename too much too quickly, customers can start to suspect that branding is doing the work that product clarity should be doing.
The danger is that Microsoft’s own success creates the conditions for confusion. The more Copilot is embedded, the more likely it is that users will encounter it in contexts they did tes recognition, but not necessarily confidence.
That does not necessarily mean less Copilot. It means more disciplined Copilot. Microsoft could keep the umbrella while making the taxonomy easier to understand: consumer, work, cloud, devices, and builder tools. Without that kind of structure, the name risks becoming a catchall, and catchalls rarely age well.
But the company now has to prove that the layer can be legible. If Microsoft keeps expanding the brand without adding structure, the Copilot name could turn into a synonym for confusion. If it introduces clearer segmentation, stronger naming rules, and better product education, the same brand could become the shorthand that makes Microsoft’s AI stack easier to buy, deploy, and trust.
Source: mezha.ua Microsoft already has 80 Copilot products – and no one fully understands what they are
Over time, though, boundaries of a single assistant. Copilot became a label attached to consumer chat, workplace copilots, security tools, developer services, device categories like Copilot+ PC, and the builder layer behind custom AI solutions such as Copilot Studio. Microsoft’s own official documentation now frames Microsoft 365 Copilot as a work assistant that sits across Word, Excel, PowerPoint, Outlook, and Teams, while also connecting to Microsoft Graph, search, and enterprise controls. That makes Copilot less a product and more a naming system for an entire AI stack.
The problem with that naming system is not that it lacks ambition. It is that the ambition has outgrown user comprehension. Bannerman’s public mapping effort reportedly started because he could no longer explain what “Copilot” meant without first sorting through Microsoft’s various implementations. His chart had to be built manually because Microsoft does not publish a single official catalog, and that alone says a lot about how fragbecome.
Microsoft has also continued to expand the Copilot idea at a product pace that makes simplification harder, not easier. In March 2026, Microsoft described the next wave of Microsoft 365 Copilot as more agentic, more integrated, and more model-diverse, with capabilities embedded directly into Word, Excel, PowerPoint, Outlook, and Copilot Chat. That is a powerful vision, but it also deepens the challenge: every new extension strengthens the ecosystem while making the umbrella name more overloaded.
The result is a classic Microsoft tension. The company wants a brand that signals everything AI to consumers and enterprises at once. But the broader the brand gets, the more it risks losing the very specificity that made it useful in the first place. As one community comparison put it, the current Copilot spread recall branding of the early 2000s, when the label was attached to nearly everything Microsoft touched.
Why the 80-Product Count Matters
The number itself is not the story; the organizational behavior behind it is. An 80-product count suggests that Microsoft’s internal teams are shipping quickly and often, and that many groups see value in tagging their work with the Copilot name. That kind of proliferation usually happens when ale brand to capture a fast-moving category before rivals define it for them.A brand that now spans layers
Copilot no longer describes one layer of the stack. It now covers user-facing chat, embedded productivity features, enterprise assistants, cloud management, security workflows, and even hardware-adjacent positioning like Copilot+ PC. Microsoft Copilot Studio extends that reach further by letting customers build and publish agents across Microsoft 365 surfaces and external systems.That breadth gives Microsoft an enormous distribution advantage. If Copilot becomes the default AI word attached to Microsoft products, then the company wins mindshare before a purchase decision even begins. But breadth also creates a comprehension tax. Users can recognize the term instantly and stihey are looking at a chatbot, a licensing tier, a developer toolkit, or a policy-controlled enterprise feature.
The key issue is that Microsoft has already reached the stage where “Copilot” can mean too many different things in one conversation. That is not just a branding problem; it is a support problem, a sales problem, and a training problem. It makes documentation harder to navigate and dn. It also increases the odds that enterprises buy something they do not fully understand.
The number is still moving
Bannerman’s count was dynamic, not static. The public tally reportedly stood at 78 at the end of March, then rose to 80 after users pointed out missing entries such as Gaming Copilot and Microsoft Dragon Copilot. Tder that the Copilot family is not only large, it is still expanding.This matters because a brand that keeps adding new nodes without pruning old ones can become self-defeating. Growth is good when the category is still forming. But once the market starts asking for clarity, more names can become less helpful than fewer, bicrosoft seems to be learning that the hard way.
- The 80-product count is a snapshot, not a ceiling.
- The brand now spans consumer, enterprise, developer, and device categories.
- Microsoft does not maintain a single public master list.
- Community feedback is actively finding additional Copilot entries.
- Expansion improves reach but worsens legibility.
How Microsoft Built This Sprawl
Microsoft’s Copilot strategy did not emerge as a random pile-up. It followed a deliberate logic: put AI inside the tools people already use, then extend that logic to adjacent products, then to custom agents, then to hardware and cloud infrastructure. That sequence is commercially rational, even if it is messy from the outside.From assistant to platform layer
The most important shift is that Copilot is no longer being sold as a single assistant. Microsoft’s official materials now describe it as a shared layer that can be embedded, extended, and governed across the Microsoft stack. In Microsoft 365, it uses tenant-scoped data and honors permissions; in Copilot Studio, it becomes something that organizations can customize with connectors, tools, and agents. That is platform thinking, not app thinking.This is where the strategy gets clever. A platform layer creates switching costs. Once a buss, automations, and internal habits around Microsoft’s Copilot tooling, moving away becomes harder. Microsoft is not just trying to sell AI prompts; it is trying to sell an operating layer for work.
Still, platform logic can collide with user logic. Users do not want to learn a taxonomy of Copilots. They want to know which one helps themge a cloud workload, automate a support queue, or buy a device. The more Microsoft behaves like a platform company, the more it must behave like a product education company too.
The role of Copilot Studio and Azure
Copilot Studio is one of the clearest signals that Microsoft wants Copilot to become an ecosystem rather than a feature. Microsoft describes it as a way to build AI-driven agents and workflows, connect them to knowledge sources, and deploy them across Microsoft 365 and other channels. That moves the brand from “assistant” to “builder tool.”Azure extends that logic into infrastructure. Microsoft’s own documentation and product pages position C cloud operations and development stack, where organizations can integrate AI into business systems and workflows. That means the Copilot name is not just a consumer-facing label; it is now a wrapper over enterprise plumbing.
- Copilot Studio turns Copilot into a development surface.
- Azure makes Copilot part of the enterprise cloud story.
- Microsoft 365 makes it the productivity layer.
- Windows makes it the OS-level identity.
- Hardware branding makes it visible before software even launches.
Consumer Confusion and the Clarity Problem
For consumers, the real issue is not whether Copilot is useful. It is whether Microsoft has made it understandable. A user who sees the Copilot name on Windows, Edge, Bing, mobile apps, and hardware packaging may assume the experience is unified, only to discover that each surface behaves differently and sometimes requires different accounts, licenses, or setups.Microsoft still has to answer
The average person does not care how many Copilots exist. They care which one they should open and what it can do. That is where the current strategy gets shaky. If a brand creates recognition without comprehension, it becomes a logo first and a product second.
Microsoft has tried to make Copilot feel ubiquitous, but ubiquity can backfire when it looks like repetition rather than usefulness. A brand that appears everywhere may seem dominant, yet if each appearance requires a different explanation, trust erodes. That is especially true for AI, where users already worry about correctness, privacy, and hidden behavior.
The company’s revised behavior on some integrations suggests it recognizes this risk. Reports say Microsoft backed away from integrating Copilot into system notifications after negative reaction, a move that reads like a small but important concession: not every surface should become a Copilot surface.
The .NET comparison is not accidental
The comearly-2000s .NET branding is telling because it captures a familiar Microsoft pattern. The company likes to unify product identity around a powerful umbrella, but if the umbrella becomes too broad, it can feel like marketing overlay instead of coherent architecture. The result is not always failure, but it often creates years of naming cleanup latealso highlights a deeper cultural issue. Microsoft has historically loved platform narratives, and platform narratives reward scale. But scale does not automatically create legibility. In consumer tech, simple often beats complete. A smaller, cleaner naming system can be easier to trust than a more ambitious but fragmented one.- Recognition is not the same as understanding.
- More branding can reduce perceived clarity.
- AI products need trust as much as visibility.
- Small naming mistakes become support headaches.
- Simpler product taxonomy can be a competitive advantage.
Enterprise Implications: Selling AI to Businesses
The enterprise side is where Microsoft’s Copilot strategy makes the most sense financially. Businesses already buy Microsoft in bundles, already trust its identity controls, and already rely on Microsoft 365, Azure, and security tooling. That gives Microsoft a natural path to sell AI as an upgrade to existing workflows rather than a separate category of software.Why businesses tolerate sprawl better than consumers
Enterprise buyers are more willing to navigate complexity if the payoff is governance, integration, and scale. They care less about a cute product name and more about whether the assistant respects permissions, stays inside the tenant boundary, and connects cleanly to their data. Microsoft leans hard on those concerns in its document65 Copilot.That said, the name still matters. A procurement team trying to understand whether it is buying a chatbot, a reporting feature, a security copilot, an agent runtime, or a full workflow platform may spend extra time untangling Microsoft’s labels before making a decision. That friction can slow adoption even when the underlying technology is sound.
There is also a licensing problem. Copilot has become not just a product family but a packaging system, and packaging systems are only elegant when they are easy to explain. Microsoft’s recent push toward more agentic offerings underscores that the company is increasingly selling outcomes, not just access. That can be good for revenue, but it can also make budget conversations more opaque.
The enterprise upside is real
If Microsoft gets this right, the company can use Copilot to deepen lock-in across work apps, cloud operations, and internal automation. Copilot Studio can becomtogether custom agents, while Microsoft 365 Copilot acts as the daily interface, and Azure provides the backend. That is a strong business model because it makes AI part of the client’s workflow fabric.It also helps Microsoft compete on more than model quality. In enterprise AI, distribution and governance often matter more than who has the flashiest demo. Microsoft’s advantage is that it can package AI where companies already work, and that makes the Copilot brand strategically valuable even when the naming is messy.
- Businesses value governance more than naming elegance.
- Existing Microsoft estates make adoption easier.
- Copilot Studio adds customization and stickiness.
- Azure supports infrastructure-level monetization.
- Licensing complexity can still slow purchasing decisions.
Consumer Hardware, Windows, and the OS Layer
Windows remains one of Microsoft’s most important distribution channels, and Copilot is increasingly tied to the operating system’s identity. Microsoft and its partners have positioned Copilot+ PC as the AI-ready hardware category, while support materials show Copilot arriving by default on new Windows 11 machines and being installed or surfaced through Microsoft’s consumer ecosystem.The desktop is wherysical
When an AI brand appears on a keyboard key, it stops being an abstract software initiative and becomes part of the machine. That is smart distribution, because it makes AI feel native and unavoidable. It also raises the stakes every time Microsoft experiments with deeper integration. ([blogs.microsoft.crosoft.com/blog/2024/05/20/introducing-copilot-pcs/)But the desktop is also where users are least forgiving. If an AI feature slows the system, adds clutter, or behaves unpredictably, people notice immediately. Unlike cloud services, Windows is visible every minute, and that means Copilot’s reputation can be shaped by memory use, UI friction, and architectural choices as much as by capability.
That sensitivity helps explain why Microsoft has occasionally pulled back. The reported decision to remove Copilot from certain notifications after user backlash suggests the company understands that OS-level AI cannot feel invasive if it wants broad acceptance. The desktop rewards restraint more than hype.
Consumer utility vs platform ambition
There is a meaningful difference between a feature people use occasionally and a platform they live inside. Copilot on Windows is trying to be both. That is a difficult balance because consumers usually evaluate operating-system features on immediate utility, not strategic coherence.The broader issue is that Windows users already worry about bloat, background processes, and hidden complexity. If Copilot is associated with browser wrappers, memory overhead, or extra prompts, the brand can pick up the wrong kin In the consumer market, convenience has to feel lightweight, not merely powerful.
- Copilot+ PC gives Microsoft physical branding leverage.
- Windows makes AI feel native but also exposes flaws.
- User trust drops quickly when integrations feel intrusive.
- Performance costs become brand costs on the desktop.
- re in consumer OS contexts.
Competitive Pressure and Market Positioning
Microsoft is not the only company trying to make AI a defining layer of the personal computing experience. Google, OpenAI, Adobe, and others are all building assistant-like products and workflow automation features. But Microsoft’s strength is breadth: through operating systems, productivity apps, cloud infrastructure, and enterprise security all at once.A scale advantage rivals can’t ignore
That breadth makes Copilot hard to avoid. A rival may have a cleaner product story, but Microsoft can place AI in front of users through channels that already sit in their daily work path. That is a strategic advantage because distribution often matters more than novelty.Still, rivals can exploit Microsoft’s naming confusion. Simpler brands are easier to explain, and in AI markets where many buyers are still learning what these tools do, clarity can beat completeness. If a competitor can explain its value in one sentence while Microsoft requires three, the simpler story may win the first meeting.
There is also soft has been pushing harder into agentic AI, with recent announcements around more advanced Copilot behavior, Work IQ, and agent management concepts. That suggests the company believes the market is moving from chat to execution. If that proves true, Copilot’s brand sprawl may be judged less harshn a pure chatbot era.
The strategic trade-off
Microsoft is betting that users will forgive the branding chaos if the underlying tools become indispensable. That may be true in enterprise environments, where workflow integration can outweigh naming messiness. But in consumer AI, where products are often tested quickly and compared casually, friction can be fatal.The competitive question, then, is whether Microsoft can turn Copilot into a trusted categoe label will become so overloaded that it loses meaning. That is a big strategic fork, because category ownership is valuable only if the category still communicates something clear.
- Microsoft’s distribution is broader than most AI rivals.
- Simpler competitors may benefit from better legibility.
- Agentic AI could make breadth more valuable.
- Enterprise and consum differently.
- Brand ownership only matters if the brand remains understandable.
The Risk of Brand Inflation
Brand inflation happens when a name is stretched so far that it loses its ability to differentiate. Microsoft is flirting with that outcome now. If every assistant, feature, servstamped Copilot, then the label begins to describe corporate intent rather than user value.When one name tries to do too much
A strong umbrella brand can simplify a product family. But an overextended one can do the opposite. The more Copilot is ung from chat interfaces to cloud workflows, the less useful it becomes as a shorthand. That is especially problematic for buyers trying to evaluate different licensing and deployment paths.This is why some users have reacted so strongly to Microsoft’s AI branding. They are not merely resisting AI; they are resisting ambiguity. When aename too much too quickly, customers can start to suspect that branding is doing the work that product clarity should be doing.
The danger is that Microsoft’s own success creates the conditions for confusion. The more Copilot is embedded, the more likely it is that users will encounter it in contexts they did tes recognition, but not necessarily confidence.
The market may force simplification
Microsoft has already shown some willingness to adjust. Backing away from notification integration after user backlash is a sign that the company understands the limits of saturation. If it wants the Copilot brand to endure, it may need to impose sharper boundaries and clearer sub-brand rules.That does not necessarily mean less Copilot. It means more disciplined Copilot. Microsoft could keep the umbrella while making the taxonomy easier to understand: consumer, work, cloud, devices, and builder tools. Without that kind of structure, the name risks becoming a catchall, and catchalls rarely age well.
- Too many meanings weaken brand memory.
- Ambiguity undermines trust in AI tools.
- Licensing complexity magnifies confusion.
- User education becomes more expensive.
- Microsoft may eventually need naming discipline.
Strengths and Opportunities
Microsoft’s Copilot strategy still has real strengths, and they are worth acknowledging. The company has a distribution machine few competitors can match, and it is pairing that with infrastructure, enterprise governance, and a growing builder ecosystem. If Microsoft can impose more order on the branding, it could convert today’s sprawl into tomorrow’s platform advantage.- Massive distribution across Windows, Microsoft 365, Azure, and devices.
- Enterprise trust through permissionsand compliance controls.
- Builder extensibility via Copilot Studio, connectors, and custom agents.
- Hardware visibility with Copilot+ PC and the Copilot key.
- Monetization breadth across subscriptions, cloud services, and premium tiers.
- Workflow stickiness once organizations embed Copilot into daily operations.
- Brand recognition that already gives Microsoft a head start in AI awareness.
Risks and Concerns
The largest risk is that Microsoft’s own branding success becomes a liability. If Copilot is everywhere, but not clearly differentiated, users may stop seeing it as a helpful AI layer and start seeing it as another example of Microsoft complexity. That would be especially damaging in consumer environments, where simplicity often matters more than enterprise logic.- User confusion about which Copilot to use and why.
- Brand dilution as the name becomes attached to too many things.
- Enterprise procurement friction from unclear product boundaries.
- Consumer backlash if OS-level integrations feel invasive.
- Trust erosion if AI features appear overhyped or underdefined.
- Support overhead from fragmented licensing and onboarding.
- Competitive openings for rivals with cleaner, simpler naming.
Looking Ahead
The next phase of Microsoft’s Copilot story will be shaped less by whether the company adds features and more by whether it can explain them. The recent move xperiences in Microsoft 365, the expansion of Copilot Studio, and the continued integration into Windows and cloud workflows all point in the same direction: Microsoft wants Copilot to become a true AI layer, not a standalone app.But the company now has to prove that the layer can be legible. If Microsoft keeps expanding the brand without adding structure, the Copilot name could turn into a synonym for confusion. If it introduces clearer segmentation, stronger naming rules, and better product education, the same brand could become the shorthand that makes Microsoft’s AI stack easier to buy, deploy, and trust.
- Watch whether Microsoft formalizes Copilot categories or sub-brands.
- Watch whether more features get removed from invasive OS surfaces.
- Watch whether enterprise buyers get clearer licensing and packaging.
- Watch whether Copilot Studio becomes the real center of gravity.
- Watch whether Microsoft simplifies the consumer story around Windows and mobile.
- Watch whether the company starts pruning overlapping names instead of adding more.
Source: mezha.ua Microsoft already has 80 Copilot products – and no one fully understands what they are
