Microsoft: Jack of All Trades

Microsoft has an enormous amount of products under their portfolio. Spanning cloud, productivity, gaming, AI, social media, developer tools and many more. Many of them are good and some are even great. However, few are best in category. Microsoft tends to dominate through their integrations and ecosystem lock-in rather than having the best product suites.

Microsoft 365 / Office

Microsoft Office is the suite most people know: Word, Excel, PowerPoint, Outlook, OneNote, Access, and Publisher. In its modern form it is Microsoft 365, which technically extends well beyond those apps into Entra, Purview, Intune, Compliance, Defender, and more. The suite has evolved into a cloud-powered platform offering real-time collaboration, OneDrive storage, Teams for communication, and SharePoint for intranet and document management.

This is, genuinely, one of Microsoft's strongest modern products. Decades of development and steady improvement have made it the default for businesses and personal users alike.

That said, it is not uncontested. Google Workspace is considered by many to either match or surpass Office. Google was the first to ship true real-time collaboration, and while Microsoft has since caught up, the reliability of Google Workspace still has Microsoft beat in the eyes of many users.

Microsoft Teams

Teams is an enterprise-ready app combining messaging, video calling, calendar integration, and webinar hosting. Positioned as the "hub for teamwork," it aims to be the single pane of glass through which a modern professional conducts their entire workday.

Teams is perhaps the clearest example of the pattern this post is about: dominance through integration rather than pure product excellence. Compared to Slack, Teams often feels heavy and unintuitive. Slack's UX is more fluid, its search is superior, and its "huddles" offer a level of frictionless spontaneity that Teams' formal meeting structure struggles to replicate.

Despite this, Teams has become the de facto enterprise standard. Why? Because it is already in your Microsoft 365 subscription. While Slack may be the "best" messaging product in a vacuum, Teams wins by being "good enough" while bundled into licences businesses are already paying for. It is a classic moat strategy: the cost of entry is zero for M365 subscribers, and the cost of leaving (in terms of broken integrations) is extremely high. Teams remains the titan of enterprise communication, even if it is not everyone's favourite tool to actually use.

Cloud - Azure

Azure is a major cloud platform, but the crown goes to Amazon Web Services (AWS).

AWS launched in 2006, giving Amazon nearly a decade head start over Azure (general availability in 2010). That head start matters. AWS has broader service depth, more mature tooling, a larger global infrastructure footprint, more comprehensive documentation, and a bigger community and third-party ecosystem. For many engineers, AWS is still the default when starting a greenfield project without existing vendor ties. Google Cloud Platform (GCP) also deserves mention, particularly for data and machine learning, where it arguably surpasses both AWS and Azure.

Where Azure actually wins is Microsoft integration. If your organisation already runs Microsoft 365, Entra ID, Intune, or Defender, Azure becomes a compelling choice. The tie-in between Entra ID and Azure RBAC, the native integration with Defender for Cloud, and the familiarity of the Azure Portal and PowerShell all lower the barrier significantly for organisations already embedded in the Microsoft ecosystem.

Azure is not the best cloud platform in isolation. But for enterprises already paying for Microsoft 365 licences and embedded in the broader Microsoft stack, it is often the most pragmatic and cost-effective choice. The switching cost, once you are deeply integrated, is enormous. And Microsoft knows that.

AI Coding

Microsoft has placed an enormous bet on AI through their multi-billion dollar investment into OpenAI, powering the Copilot product line across Microsoft 365, Azure, GitHub, and beyond. On paper, a decisive move. In practice, it is a little more complicated.

Microsoft's AI story is largely a borrowed one. The underlying models powering Copilot are OpenAI's. Microsoft's contribution is the integration layer, weaving those models into the products businesses already use daily. Copilot in Word, Excel, Teams, and Outlook is genuinely useful, and for many professionals it represents their first meaningful encounter with AI in a workplace context.

GitHub Copilot was genuinely groundbreaking when it launched in 2021. It was one of the first AI coding assistants to reach mainstream adoption and, for a time, felt like magic. That novelty has worn off. The competition has moved well ahead:

• Cursor, built on VS Code, understands your entire project rather than just the file in front of you. Multi-file edits, architectural reasoning, and one-click changes feel like a generational leap. Developers who switch rarely go back.

• Claude Code operates in the terminal as a genuine pair programmer. It can autonomously navigate a codebase, plan multi-step changes, run commands, and iterate. GitHub Copilot does not operate at that level.

• OpenAI's own Codex, somewhat ironically, pulls ahead of the Copilot product it underpins. Used directly as an agentic tool it can tackle entire features end to end, producing pull-request ready code with minimal hand-holding.

GitHub Copilot remains a sophisticated autocomplete tool. Good at the next line and boilerplate; weaker on deep reasoning, agentic work, and the contextual awareness its rivals now offer as standard. The gap is widening, not closing.

And yet the familiar pattern emerges. Copilot is bundled into many developer licences, offered through enterprise agreements, and sits inside the VS Code and GitHub ecosystem most developers already live in. For organisations where IT policy dictates approved tooling, Copilot wins by default. Not because it is the best tool, but because it is already there.

Conclusion

This has not been an argument against using Microsoft. It has been an argument about understanding why. Teams, Azure, and Copilot all follow the same shape: not always the strongest standalone option, but already there in the licence, the tenant, the approved tooling list. Microsoft's greatest product is arguably the ecosystem itself.

Running a business on Microsoft is a perfectly rational decision. Lock-in is a legitimate strategy, and if the trade-off between convenience and best-in-class capability works for your organisation, there is no shame in that. Just make sure it is a conscious one.

The teams that produce the best outcomes are those who question their defaults. They ask not just "what do we have?" but "what is the right tool for this problem?" Sometimes the answer is still Microsoft. Sometimes it is Slack, or AWS, or Cursor. Knowing the difference matters.