Company profile — Microsoft: history, ownership, strategy and current technology portfolio

Microsoft’s 2026 technology portfolio is built around a common enterprise spine: identity, Azure, Microsoft 365, GitHub, Windows and business applications increasingly feed the same cloud and AI services.

Software licensing became a cloud platform

Microsoft was founded in 1975 by Bill Gates and Paul Allen and built its early scale through PC software. Windows and Office established the company as a desktop-software giant, while Windows Server and developer tools deepened its enterprise role. Azure then changed the centre of gravity by moving Microsoft into large-scale cloud infrastructure and recurring services.

The modern company still benefits from Windows and Office, but it is no longer dependent on selling packaged software upgrades. Subscriptions, cloud consumption, security, developer services and business applications now create a more continuous relationship with organisations.

Ownership is conventional; customer dependence is not

Microsoft Corporation is a publicly traded US company without a controlling founder or parent company. Large institutional investors hold substantial positions, while strategic authority sits with the board and executive team.

The more important source of power is commercial rather than voting control. Many organisations depend on Microsoft identity, productivity, endpoint management, cloud infrastructure or developer tooling. That installed base gives the company a ready path for new products but also makes migrations, licensing changes and service outages unusually consequential.

Azure is the infrastructure layer under the strategy

Azure provides computing, storage, networking, databases and AI services to enterprises and also supports Microsoft’s own software portfolio. That gives the company a direct way to connect infrastructure demand with higher-level products such as Microsoft 365, Dynamics 365 and GitHub.

AI increases the strategic importance of that infrastructure because model training and inference require large amounts of compute and networking. Microsoft has to manage accelerator supply, data-centre construction, energy use and model partnerships while keeping cloud economics acceptable for customers.

Copilot is becoming a product layer rather than one application

Microsoft uses the Copilot name across productivity, development, security, business applications and agent-building tools. The shared branding can make the portfolio look simpler than it is: each Copilot operates with different permissions, data sources, licensing and administrative controls.

The success of the strategy will depend on whether these assistants save measurable time in real workflows. Enterprise adoption requires permissions, auditability, data quality and predictable cost, not only model capability. That is why identity and governance remain as important as the underlying AI model.

GitHub connects Microsoft to software development

GitHub gives Microsoft a major role in source-code hosting and developer collaboration, while GitHub Copilot brings AI directly into coding workflows. Visual Studio, .NET, Azure and GitHub can therefore reinforce one another without forcing every developer to use Windows.

That cross-platform stance is a notable change from Microsoft’s earlier history. The company increasingly competes by owning services developers choose rather than by requiring its own operating system at every layer.

Windows and Surface remain reference points

Windows is still central to Microsoft’s reach in personal and business computing. Surface hardware gives the company a way to demonstrate Windows features, Copilot+ PC requirements and new processor architectures, even though most Windows PCs are built by partners.

This creates a partnership tension similar to Google’s Pixel strategy. Surface needs to showcase new ideas without making Dell, HP, Lenovo, ASUS and other Windows manufacturers feel that Microsoft is competing unfairly with the platform it supplies to them.

Gaming and business applications broaden the risk profile

Xbox, game studios and subscription services place Microsoft in entertainment, while Dynamics 365 and Power Platform extend it deeply into finance, sales, supply chain and low-code application development. Those businesses have different customers and economics, but they increasingly share identity, cloud infrastructure and AI services.

The breadth can be useful for customers that want one vendor across multiple layers, yet it also creates licensing complexity and platform dependence. Organisations have to decide when integration outweighs the risk of concentrating too much infrastructure and workflow data with one supplier.

What to watch in the next Microsoft phase

The key questions are whether Copilot usage becomes durable enough to justify its cost, how Azure capacity keeps pace with AI demand, whether GitHub remains the preferred developer platform, and how Microsoft handles security across an expanding set of connected services.

Microsoft’s advantage is not one product. It is the ability to place a new capability inside tools organisations already use. The weakness is the same: when identity, cloud, productivity and business applications become tightly coupled, operational failures or poor licensing decisions can spread across a customer’s entire environment.

Security is now a platform in its own right

Microsoft sells identity, endpoint, cloud and threat-protection products that sit across the same enterprise estate as Windows, Azure and Microsoft 365. That gives the company extensive telemetry and integration opportunities, but it also raises the consequences of security failures in shared services.

Customers increasingly evaluate Microsoft not only on feature breadth but on how quickly vulnerabilities are fixed, how clearly incidents are communicated and whether administrative defaults reduce or increase risk. Security quality can therefore influence adoption across unrelated Microsoft products.

LinkedIn adds a data and distribution asset that does not depend on Windows

LinkedIn gives Microsoft a large professional network, recruitment marketplace and advertising business. Its user identity and economic graph are different from the corporate directories managed through Microsoft 365, but the two can complement sales, learning and recruiting products.

The acquisition also demonstrates Microsoft’s broader strategy of owning services that remain valuable on competing devices. A LinkedIn user does not need Windows, just as a GitHub developer can work on macOS or Linux. That reduces dependence on the PC operating-system share that defined earlier Microsoft eras.

Licensing complexity can become a strategic weakness

Microsoft’s breadth lets customers combine cloud, security, productivity and business applications, but the licensing rules can be difficult to model across users, devices, capacities and premium add-ons. A bundle that begins simply can become expensive as Copilot, security or analytics features are layered on.

For enterprise customers, procurement discipline matters. The technical convenience of one integrated supplier should be weighed against renewal leverage, contract flexibility and the cost of moving workloads later if priorities change.