← Atlas
Institution

Microsoft

From the IBM PC to Azure, Microsoft repeatedly moved the common layer around which other people organized their work: first an operating system, then a Windows-and-Office enterprise stack, and finally cloud identity and services. Each move widened what customers, developers, and partners could do together while giving Microsoft new authority over the terms of that coordination.

Governing questionHow did Microsoft keep moving the layer that other organizations treated as common infrastructure, and what happened to the people who could not move as quickly?

Period1975-July 2026, tracking PC-platform, enterprise-and-device, and cloud-service transformations across leadership successions

Working · Claim Cited

Three times, the common layer moved

Microsoft's history from 1975 through July 2026 is not one continuous personal- computer success. The corporate chronology places Windows and Office launches, Steve Ballmer's appointment as chief executive in 2000, and Satya Nadella's in 2014 along a sequence in which work crossed each succession.1 The Atlas interpretation is that Microsoft repeatedly moved the layer around which other organizations coordinated: from DOS and Windows, through an enterprise software stack, to remotely operated identity, data, cloud, and AI services.

Those layers let hardware makers, developers, administrators, and users share interfaces and routines. They also placed authority over compatibility, licensing, and service operation inside Microsoft. The recurring question is therefore how the company moved a coalition before its old common layer lost its value—and what happened to customers, partners, and workers whose work had accumulated around the layer being left behind.

IBM licensed an operating system; Microsoft kept a market

When Microsoft contracted with IBM in November 1980, it did not have the operating system IBM wanted. It licensed and then purchased 86-DOS from Seattle Computer Products; author Tim Paterson joined Microsoft and worked with IBM's PC engineers. IBM shipped the result as PC DOS, while Microsoft retained the rights and licensed its version to other computer makers as MS-DOS.2

IBM's own retrospective says the PC team used off-the-shelf components, published a technical reference, and adopted an open architecture. Other firms used the specifications and reverse-engineered the boot code to make “IBM-compatible” computers.3 IBM's account is a participant history, but the combination it describes explains the structure: Microsoft could supply the common software layer without choosing which computer maker won. Hardware makers could enter around a shared target; developers could reach customers across manufacturers; and buyers could change compatible machines without necessarily abandoning every application.

The bargain also shifted authority. A manufacturer could differentiate its price and hardware, but DOS became a common base for applications across IBM PCs and compatible machines.2 Microsoft sat between the people making machines and the people making software. The earlier IBM organized under Thomas J. Watson Sr. and Jr. had integrated much more of its computing system inside one company.3 The PC coalition was looser, and the operating-system supplier—not IBM—became the most durable governor of its shared layer.

Windows and Office made a coalition out of compatibility

Microsoft's own timeline dates its first Office suite to 1989, Windows 3.0 to 1990, and Windows 95 to 1995.1 Those dates establish the product sequence, not the quality or social value of the products. Microsoft supplied interfaces and tools; outside developers supplied applications; computer makers installed the operating system; and users accumulated documents and learned routines.4 The platform's usefulness was coalitional.

The installed base rewarded continuity. A new Windows version had to improve the platform without stranding applications, documents, and learned routines. That constraint benefited customers who could carry work forward, but it also made departure a collective problem. Reviewing the later antitrust record, the D.C. Circuit accepted findings that users faced costs in learning and converting files and that developers' preference for the large Windows base reinforced users' preference for Windows. The court called this the “applications barrier to entry,” while noting that the case concerned Microsoft's maintenance of its position, not whether it had acquired its initial dominance through superior foresight or quality.4

Licensing as well as engineering governed that position. A 1995 consent judgment prohibited new “per processor” licenses, restrictions on an OEM's distribution of non-Microsoft operating systems, minimum commitments, and several kinds of conditional licensing. The judgment was entered without trial, adjudication, evidence, or admission of any issue of fact or law; it therefore establishes the binding restrictions, not that Microsoft admitted the government's allegations.5

The Internet Explorer campaign shows how browser integration, OEM restrictions, and distribution contracts later became part of one response to middleware. In 2001 the D.C. Circuit affirmed in part the judgment that Microsoft had maintained its operating-system monopoly through anticompetitive means. It reversed attempted-monopolization liability for the browser market, vacated the per se tying ruling for reconsideration under a different standard, and vacated the remedy—including the breakup order—for new proceedings before another judge.6 That mixed appellate outcome matters: it preserved monopoly-maintenance liability but did not affirm every district-court theory or remedy.

Ballmer extended the stack while the center shifted

Under Ballmer, Microsoft extended the coordination layer beyond the desktop. In its 2010 annual report, Microsoft placed Windows Server, Windows Azure, SQL Server, Visual Studio, and System Center in the Server and Tools group and reported that about half of that group's revenue came from annuity volume-licensing agreements.7 The filing establishes the company's product and revenue description; its claims of customer superiority remain management's claims.

Azure was therefore not a sudden Nadella-era invention. Ray Ozzie announced Windows Azure in October 2008 as a Microsoft-hosted foundation intended to join cloud services with enterprise datacenters; the announcement also described a limited developer preview and Microsoft's datacenter network.8 The service model moved part of the relationship from periodically installed products toward infrastructure Microsoft continuously operated.

Yet mobile computing changed the competitive center. Microsoft's 2014 filing identified Apple, Google / Alphabet, iOS, and Android as principal competitors to Windows and Windows Phone.9 Microsoft announced the Nokia Devices and Services transaction in 2013 and completed it on 25 April 2014. The same filing recorded a $9.5 billion purchase price, including $1.5 billion in acquired cash, and about 25,000 employees transferred with the business. The Atlas reads the deal as an attempt to bring hardware and platform authority closer together; the filing does not by itself prove that interpretation.

Cross-platform service moved from exception to center

Under Satya Nadella, a cross-platform, service-based transition already underway became more central. In 2012, while Nadella led Server and Tools, Azure had announced preview support for both Windows and Linux virtual-machine images; Office for iPad shipped in March 2014, weeks after Nadella's appointment.10 Those dates matter: a chief executive did not create the products at the moment of succession. The change was not an instantaneous invention but an elevation of cross-platform service over Windows exclusivity.

The turn required abandoning work as well as embracing it. In July 2015, Microsoft announced a $7.6 billion impairment associated with the Nokia assets and reductions of up to 7,800 positions, primarily in the phone business. The same announcement projected $750 million to $850 million in restructuring charges and said the phone segment's prospects were below the original expectations.11 Those are company-announced ceilings and charges, not a worker census. They identify phone workers as the primary group exposed when Microsoft reversed the device strategy.

The 2018 agreement to acquire GitHub made the new coalition especially visible. Nadella promised that GitHub would retain a developer-first ethos and operate independently under Nat Friedman, while reporting into Scott Guthrie's Cloud + AI group; GitHub cofounder Chris Wanstrath would become a technical fellow. The announcement also promised that developers could keep using their chosen languages, tools, operating systems, clouds, and devices.12 This is evidence of Microsoft's acquisition commitments, not independent proof of permanent GitHub autonomy. The promise itself marked the coalition the company needed to sustain.

Workers were not only recipients of strategy. In November 2024, the Communications Workers of America reported that hundreds of unionized ZeniMax workers held a one-day strike over bargaining progress, remote-work options, and outsourcing of quality-assurance work; quoted members framed those disputes as job-security concerns.13 In July 2025 CWA reported that more than 300 quality-assurance workers had ratified a first contract after two years of negotiations and that Microsoft recognized two additional ZeniMax units. The union said the contract included a crediting policy and an agreement governing AI at work.14 These worker-controlled sources record members' experience and organizing claims. They are neither a representative survey of Microsoft's global workforce nor neutral adjudications of every allegation.

Continuous service turned reliability into governance

Customers interviewed in the UK cloud inquiry described public cloud's advanced functionality, elasticity, scalability, flexibility, and resilience; many also said non-public systems were not good substitutes or would be costly to adopt.15 The operating bargain is different from buying a copy of Windows. Microsoft engineers continuously change the service; customer administrators configure their tenants; data, permissions, contracts, and learned practice make exit a migration rather than a product swap.

The 2023 compromise of Microsoft Exchange Online made the resulting division of responsibility concrete. The U.S. Cyber Safety Review Board reported that a threat actor used tokens signed with a Microsoft key created in 2016 to compromise mailboxes at 22 organizations and more than 500 individuals, including senior U.S. officials. It concluded that the intrusion was preventable, that a cascade of avoidable Microsoft errors enabled it, and that Microsoft's security culture was inadequate.16 The Board also recorded Microsoft's full cooperation with its review. The State Department detected anomalies in logs available through its G5 government license; no customer could rotate Microsoft's signing key or repair the service's authentication foundation. Scale concentrated capability and a duty customers could not discharge for themselves.

Cloud integration again became a competition question

The cloud did not eliminate the compatibility bargain. It added switching work, data transfer, and software-licensing terms to it. In its July 2025 final cloud-infrastructure decision, the UK Competition and Markets Authority found that technical barriers and egress fees raised costs for some customers seeking to switch or use multiple clouds. It also found that Microsoft's licensing practices materially disadvantaged AWS and Google for workloads using relevant Microsoft software, weakened those rivals as competitive constraints, and reduced competition.15 This was a market investigation under the Enterprise Act, not an adjudication that Microsoft had infringed the Competition Act; the CMA expressly said participation or remedies did not imply wrongdoing.

European scrutiny of Teams reached a different legal form. In September 2025, the European Commission made Microsoft commitments legally binding: versions of business suites without Teams at lower prices, switching rights for customers with long-term licenses, specified interoperability, and data portability.17 An Article 9 commitments decision addresses the Commission's concerns without a finding that the company infringed EU antitrust law. The distinction is the same one the 1995 U.S. consent judgment requires: a binding constraint is not automatically an admission or adjudicated violation.

As of 14 July 2026, the CMA was also conducting an open investigation into whether Microsoft's business-software ecosystem should receive strategic-market- status designation. The agency said its customer research would examine purchase alternatives and ability to switch; its case page scheduled a proposed decision for October 2026 and a final decision by February 2027.18 An open investigation is evidence of the question regulators are asking, not a finding that Microsoft has strategic market status or violated a rule.

Financial scale and physical infrastructure distribute different returns

Microsoft's fiscal 2025 annual report recorded $281.7 billion in revenue and $128.5 billion in operating income. It also recorded $24.7 billion in dividends declared and $13.0 billion of share repurchases for the year; the shareholder letter said Azure revenue exceeded $75 billion.19 Those disclosures establish financial scale and returns to owners. They do not show that every customer, partner, worker, or community shared the gains.

The physical foundation distributes burdens differently. In July 2026, Microsoft reported that its total Scope 1, 2, and 3 emissions had increased 25% year over year in fiscal 2025, primarily because of datacenter expansion and its pause in using non-additional, unbundled renewable-energy certificates. The same self-report said Scope 2 had risen from nearly 2% to 13% of its footprint and acknowledged that global water replenishment alone was insufficient without local watershed attention.20 These are company-reported aggregates and explanations, not independent measurements of burdens in each host community.

Independent U.S. energy research supplies scale context but not company attribution. Lawrence Berkeley National Laboratory's June 2026 bottom-up model estimated that data centers could use 11.8% of U.S. electricity in 2030, with a 9.5%–15.3% scenario range.21 The study is industry-wide. It does not allocate a share to Microsoft or establish which local communities bear a particular facility's costs. That allocation, along with community-controlled accounts of land, grid, and water decisions, remains a research need.

The concept fingerprint follows the moving common layer

Coordination, communication, and common understanding and structure, hierarchy, and scale explain how Microsoft repeatedly organized products and partners around a shared technical layer. Knowledge, expertise, and professional autonomy, strategy, competition, and adaptation, and innovation, entrepreneurship, and renewal identify the expert and competitive choices that moved that layer from operating systems to cloud services. Governance, stewardship, and accountability and executive attention, information, and organizational sensing ask who could inspect and redirect the dependencies created at each transition.

Evidence boundaries

The worker-controlled evidence here represents particular unionized U.S. game workers, not Microsoft's worldwide workforce.1314 The GitHub record establishes acquisition promises, not a longitudinal test of whether developer autonomy was preserved.12 The environmental record combines company aggregates with an industry-wide model; it cannot establish local consent or distribute Microsoft-specific effects among host communities.2021 Those boundaries rule out claims of uniform worker experience, permanent GitHub independence, or measured community impact from the present record.

Across fifty-one years, Microsoft did more than preserve a software franchise.1 The Atlas interpretation is that it repeatedly persuaded a changing coalition to organize around a common layer, then moved that layer while much of the old one still mattered. The IBM arrangement shows how a shared interface can widen a market while shifting authority. The Nokia reversal shows the worker and capital costs of changing course. The Exchange intrusion shows why a service used as infrastructure inherits duties customers cannot perform themselves. The open question is who should share authority when the next common layer—now increasingly built from cloud and AI services—is too useful for large organizations to ignore and too consequential for its owner to govern alone.

Source notes

  1. Microsoft, “Facts About Microsoft,” table “Important Dates,” rows for 1975, 1 August 1989, 22 May 1990, 24 August 1995, 13 January 2000, 4 February 2014, and 27 March 2014, current through 31 March 2026 and accessed 14 July 2026, company chronology. This is Microsoft's participant chronology; it establishes the dates the company reports, not an independent assessment of the products or leaders.

    ↩ ↩ ↩

  2. Leonard J. Shustek, “Microsoft MS-DOS Early Source Code,” Computer History Museum (25 March 2014), sections “IBM did something very unusual for their 1981 personal computer” and “More about the origins of MS-DOS,” especially paragraphs beginning “When Microsoft signed” and “Microsoft originally licensed,” museum account. This museum reconstruction accompanies a source-code release and relies in part on participant records and recollections; it is stronger for the transaction sequence than for disputed motives.

    ↩ ↩

  3. IBM, “The IBM PC,” sections “A radical new approach for an entirely new market” and “The unveiling,” paragraphs beginning “But the team decided” and “A few companies,” accessed 14 July 2026, IBM history. This is IBM's participant history of the design and compatible-machine ecosystem.

    ↩ ↩

  4. United States v. Microsoft Corp., 253 F.3d 34 (D.C. Cir. 2001) (en banc), slip opinion pp. 15–22, especially the discussion of user switching costs and the “applications barrier to entry,” D.C. Circuit opinion. The appellate court accepted the relevant factual findings while separating initial acquisition of monopoly power from the challenged maintenance acts.

    ↩ ↩

  5. United States v. Microsoft Corp., Final Judgment, Civil Action No. 94-1564 (D.D.C. 21 August 1995), opening recital and §§ II.11 and IV.B–F (PDF pp. 1, 4, and 6–7), final judgment. The recital expressly says the consent judgment followed no trial or adjudication and constituted no evidence or admission of fact or law.

    ↩

  6. United States v. Microsoft Corp., 253 F.3d 34 (D.C. Cir. 2001) (en banc), slip opinion pp. 4–6 (disposition), 67 (per se tying), 97–99 (remedy and modified liability), and 104–118 (judicial conduct), D.C. Circuit opinion. This controlling appellate decision, rather than the district court's original breakup order alone, defines which liability and remedy holdings survived review.

    ↩

  7. Microsoft, 2010 Annual Report, “Business—Operating Segments—Server and Tools,” paragraphs “Approximately 50%” and “Products and Services,” company filing. The filing establishes Microsoft's segment composition and reported revenue mix; nearby claims about product advantages are management's assertions.

    ↩

  8. Microsoft, “Microsoft Unveils Windows Azure at Professional Developers Conference” (27 October 2008), opening paragraphs and sections “Empowering Cloud Development” and “State-of-the-Art Datacenter Infrastructure,” company announcement. This participant source establishes the announcement and intended design, not the later service's independent performance.

    ↩

  9. Microsoft, 2014 Annual Report, “Devices and Consumer—D&C Licensing—Competition,” “Employees,” and Note 9, “Business Combinations—Nokia's Devices and Services Business,” especially the opening paragraph and purchase-price table, company filing. The filing's expected synergies were forward-looking management claims; the purchase price, completion date, and employee count are reported facts.

    ↩

  10. Microsoft, “Microsoft Ushers in the ‘Era of the Cloud OS’” (11 June 2012), “Windows Azure” bullet, company announcement; Microsoft, “Facts About Microsoft,” “Important Dates” rows for 4 February and 27 March 2014, company chronology. Both are participant records and establish the product and leadership sequence, not its causal interpretation.

    ↩

  11. Microsoft, “Microsoft Announces Restructuring of Phone Hardware Business” (8 July 2015), opening announcement and paragraphs beginning “As a result” and “Accordingly,” company announcement. The source announced “up to” 7,800 reductions and projected charges; it does not identify every person ultimately displaced.

    ↩

  12. Satya Nadella, “Microsoft + GitHub = Empowering Developers” (4 June 2018), paragraphs beginning “First,” “Most importantly,” and “Once the acquisition closes,” company announcement. This is an acquiring chief executive's statement of commitments, not independent outcome evidence.

    ↩ ↩

  13. Communications Workers of America, “ZeniMax Video Game Workers Walk Off the Job in Maryland and Texas” (14 November 2024), paragraphs beginning “Earlier this week,” “What we want,” and “In January 2023,” union account. This worker-controlled source preserves members' stated experience and the union's allegations; it is not a labor-board finding.

    ↩ ↩

  14. Communications Workers of America, “Video Game Developers and Customer Service Workers at Microsoft Form New Unions with CWA” (2 July 2025), opening paragraphs and paragraphs beginning “The formation of these two unions” and “The collective bargaining agreement,” union account. The worker-controlled record establishes what CWA reported about recognition, ratification, and contract terms; it is not a representative measure of the full workforce.

    ↩ ↩

  15. UK Competition and Markets Authority, Cloud Infrastructure Services: Final Decision Report (31 July 2025), paras. 3.133–3.136 (report pp. 84–85), 7.767–7.776 (pp. 561–563), and 9.41–9.64 (pp. 601–606); see also paras. 1.5–1.8 (pp. 18–19) and 7.2 (pp. 390–391) on the legal character of a market investigation, final report. This is an independent regulator's final market finding, but expressly not an infringement adjudication under the Competition Act 1998.

    ↩ ↩

  16. U.S. Cyber Safety Review Board, Review of the Summer 2023 Microsoft Exchange Online Intrusion (2024), executive summary pp. iii–v and “1.1 Overview,” report pp. 1–3, CISA-hosted report. The public-private Board describes its review as independent and records that Microsoft fully cooperated; its conclusions are scoped to the incident and the evidence it gathered.

    ↩

  17. European Commission, “Commission Accepts Commitments Offered by Microsoft to Address Competition Concerns Relating to Teams” (12 September 2025), commitment list and “Background,” Commission press release. The regulator's Article 9 decision makes commitments binding without concluding that Microsoft infringed EU antitrust law.

    ↩

  18. UK Competition and Markets Authority, “Microsoft's Business Software Ecosystem,” headings “Case information,” “Qualitative customer research,” and “Indicative timetable,” updated 23 June 2026 and accessed 14 July 2026, open case record. The page describes an investigation and future decision schedule, not a designation or finding.

    ↩

  19. Microsoft, 2025 Annual Report, shareholder letter paragraph beginning “Financially,” and “Share Repurchases and Dividends” tables, company filing. The report establishes company-reported results and owner distributions; the shareholder letter's explanation of demand and trust is management's interpretation.

    ↩

  20. Brad Smith and Melanie Nakagawa, “Responsibly Building the AI Future” (Microsoft, 9 July 2026), sections “Progress amid growth” and “What this moment requires,” accessed 14 July 2026, company sustainability report introduction. This is Microsoft's self-report of fiscal 2025 aggregates, methods, and explanation; it does not independently allocate local environmental effects.

    ↩ ↩

  21. Sarah Josephine Smith et al., United States Data Center Energy Usage Report: 2025 Update (Lawrence Berkeley National Laboratory, June 2026), “Abstract,” including the reference case, sensitivity range, and bottom-up model description, LBNL publication record. The independent estimate covers the U.S. data-center industry and does not attribute consumption or community effects to Microsoft.

    ↩ ↩
Research record

Evidence basis

Claim Cited. Material claims carry source locators; comparative interpretation may still evolve.

Open questions and affected lives

Benefit-to-life status: Seed

  • When do compatibility and bundling lower coordination costs, and when do they make customers or developers unable to refuse Microsoft's terms?
  • What duties follow when public institutions depend on identity, productivity, and cloud systems they cannot readily inspect or replace?
  • Which workers and communities bear the costs when a platform strategy reverses or when cloud and AI infrastructure expands?
  • What structural safeguards can keep a platform owner from privileging its adjacent products over dependent builders and users?

Customers And Users · Mixed Compatible PCs and public cloud services broaden shared capabilities, while court and regulatory records identify switching barriers and concentrated dependency. Source Anchored

Suppliers And Partners · Mixed Microsoft's common platforms give developers and partners access to customers, while Microsoft retains authority over interfaces, licensing, and the terms on which adjacent products compete. Source Anchored

Workers · Mixed The Nokia acquisition transferred about 25,000 workers to Microsoft in 2014; Microsoft then announced reductions of up to 7,800 positions in 2015, while later unionized game workers used strikes and bargaining to gain contract protections. Source Anchored

Owners And Investors · Benefit Microsoft reported $281.7 billion in fiscal 2025 revenue, $128.5 billion in operating income, $24.7 billion in dividends, and $13.0 billion in share repurchases. Source Anchored

Public Institutions · Mixed Public institutions used Microsoft-hosted email for sensitive work, while the 2023 Exchange Online intrusion showed that core authentication and security obligations remained concentrated in Microsoft. Source Anchored

Ecosystems · Burden Microsoft reported that its total emissions rose 25% year over year in fiscal 2025, driven primarily by datacenter expansion and a change in renewable-certificate practice; industry-wide U.S. electricity projections show why local allocation and mitigation need further research. Source Anchored

Ledger
L33
Research
Working
Evidence
Claim Cited
Ethical review
Seed
Period
1975-July 2026, tracking PC-platform, enterprise-and-device, and cloud-service transformations across leadership successions
Archetype
Long-lived developer and enterprise platform company repeatedly shifting coordination from software licenses to integrated systems and remotely operated services
Structured atlas record

Idea coverage

Organizational profile

Authority sources
Market Capital, Technical Substrate, Professional Expertise
Decision loci
Central Executive, Divisional, Professional Cell
Ownership forms
Public Corporation
Coordination mechanisms
Hierarchy, Standards, Markets, Modular Interfaces
Knowledge flows
Bidirectional, Specialist Staff, Embedded Practice
Measurement modes
Financial, Operational
Learning modes
Experimentation, Formal Research, Market Feedback
Adaptation modes
Central Reconfiguration, Local Iteration, Modular Recombination
Beneficiary groups
Customers, Workers, Shareholders, Suppliers
Failure risks
Capture, Bureaucratic Rigidity, Siloing, Externalized Harm

Provenance and sources

Corpus
governance-reference-atlas-2026-07-11
Source section
Microsoft
Imported
2026-07-11

Online anchors

Continue exploring

7 connected ideas