Scan a website for consumer and competition risks, report a problem, and search live cases. Not a law firm.

CounterLayer
← Case library

Both · remedy · ~10 min read

Microsoft / Activision Blizzard

2022–2023 · AAA video games, game consoles, cloud gaming services

Microsoft bought Activision Blizzard, home of Call of Duty and World of Warcraft, for roughly $69 billion. Regulators worried Microsoft might make those games exclusive to Xbox or its cloud service. The UK initially said no, then yes after Microsoft promised to license games to other cloud platforms. The US FTC failed to stop the deal in court, and the EU cleared it with conditions. Gamers still see Call of Duty on PlayStation—for now, under negotiated deals.

The story

Video game mergers attract scrutiny because hit franchises can shift console and subscription battles overnight.

Sony argued losing Call of Duty on PlayStation would harm competition; Microsoft promised continued cross-platform releases.

The UK's Competition and Markets Authority became the highest-profile obstacle, fearing cloud gaming foreclosure, before accepting licensing remedies.

A federal judge denied the FTC's request to pause the merger, allowing closure while administrative proceedings continued—a split outcome across jurisdictions.

Why it matters

Content ownership drives platform competition in games, streaming, and cloud.

Remedy design—licensing vs block—decided one of the decade's biggest tech mergers.

Shows multinational deals can clear in some regions while facing lingering challenges in others.

What was claimed

The merger would lessen competition in consoles, multi-game subscriptions, and cloud gaming.

Microsoft could withhold must-have titles from rivals post-acquisition.

Behavioral promises were insufficient without structural relief (according to some enforcers).

The other side

Microsoft said the deal would expand games to more devices and consumers via Game Pass.

It argued Sony remained dominant on consoles and had many exclusive titles itself.

Microsoft offered long-term licensing and access commitments to address foreclosure fears.

What it means for you

Game Pass may include more Activision titles over time.

Cloud gaming providers may receive licensed access under UK/EU conditions.

Future exclusivity battles could still emerge game-by-game despite current deals.

Bottom line

Microsoft–Activision closed with cloud licensing remedies and public promises on Call of Duty—a merger victory for the buyer after intense global review.

Timeline

  1. 2022

    Largest gaming merger announced

    Microsoft sought Activision's blockbuster franchises to bolster Game Pass and cloud gaming.

  2. 2023

    Split global decisions

    The UK CMA blocked then cleared a revised deal; the EU approved with cloud licensing conditions; a US judge denied the FTC's emergency block.

  3. Late 2023

    Integration begins

    Microsoft completed the acquisition and negotiated multi-year Call of Duty availability on PlayStation.

Key dates

Deal announced
January 2022
FTC sued to block
December 2022
Deal closed
October 2023

Formal snapshot

Summary: Microsoft's $69 billion acquisition of Activision Blizzard faced global merger review, with the FTC seeking to block it and the EU ultimately clearing subject to cloud gaming licensing commitments.

Regulator / plaintiff argument: Enforcers feared Microsoft could withhold Activision games like Call of Duty from rival consoles or cloud services, foreclosing competition in gaming and subscription markets.

Outcome: Deal closed after UK CMA initially blocked then accepted restructured cloud licensing remedies; FTC preliminary injunction denied though administrative case continued separately.

Remedies: Cloud gaming content licensing commitments in the UK and EU; behavioral assurances on Call of Duty availability on rival platforms.

Conduct tags

merger

Laws referenced

  • Clayton Act §7 — 15 U.S.C. §18
  • EU Merger Regulation — Reg. (EC) No 139/2004
  • Hart-Scott-Rodino Act — 15 U.S.C. §18a

Companies

Sources

Reader signals

0 reads · synced via local demo storage — add NEXT_PUBLIC_SUPABASE_* to enable shared likes and comments

Comments

    No comments yet — start the thread.