Microsoft Severance: Gaming Paid for the AI Buildout, and No Confirmed Number Anywhere
On 6 July 2026 Microsoft cut roughly 4,800 roles (about 2.1% of its workforce), and the striking thing is where they fell. Roughly two-thirds were in Xbox and gaming: about 3,200 gaming roles were slated to go across the FY27 year, with around 1,600 eliminated immediately, and the announcement landed alongside the spin-off of four gaming studios. Most of the rest were in sales. This was not a company-wide trim spread evenly across product areas; it was a gaming-division restructuring, executed while Microsoft's capital spending races toward roughly $190 billion, the bulk of it on AI infrastructure.
That juxtaposition is the story: the entertainment division was reshaped while the company pours money into the AI buildout. And here is what almost every article about it leaves out: Microsoft has never published a per-employee severance formula. Not for this cut, not for the multiple 2025 waves before it. So every specific weeks-of-pay number now circulating for a July 2026 Microsoft exit is leaked, recycled from an internal document, or employee-reported. Not one carries the company's own confirmation. Keeping that distinction visible on every figure is this article's whole job.
The Short Answer
Microsoft has confirmed the headcount and the shape of the cut, and essentially nothing about what departing employees are paid. The most consistent leaked-and-employee-reported description of Microsoft severance (drawn from recycled internal documents and forum posts, and it should be read as exactly that) runs roughly:
- Up to ~39 weeks of base pay, scaled by job level (reported): for levels 64 and below, about 1 week per 6 months of service; for levels 65–67, about 2 weeks per 6 months of service
- A 60-day minimum notice period (reported)
- Roughly 6 months of healthcare continuation plus 12 months of COBRA (reported)
- Stock/RSU vesting reported to continue through the notice period (reported, not confirmed)
Treat every one of those as an estimate, not a company-confirmed schedule: they are recycled from internal documents and forum reports, actual packages may come in above or below these figures, and Microsoft has confirmed none of them. Separately, an April 2026 Voluntary Separation Programme was reported at about 12 weeks plus 2 weeks per year of service, capped at 52 weeks. That is a different mechanic from the involuntary cut, and also never company-published. What is company-confirmed is only the structure of the event: ~4,800 roles, ~2.1%, the gaming concentration, the four studio spin-offs, and a Washington WARN notice.
Why There's No Confirmed Number
The reason this article reads differently from a Meta or a 2023-Google write-up is simple: there is no primary source to point at. Google put its 2023 formula in a signed blog post; Meta's 2022 terms are widely treated as company-confirmed. Microsoft has done neither. No blog post, no separation memo, and no SEC filing discloses standard non-executive severance terms; Microsoft's filings book aggregate charges, not per-employee schedules. The company's public statements about the July cut described strategy and headcount, not package terms.
Into that vacuum flows the leaked level-tier structure: the 1-week-per-6-months (levels ≤64) and 2-weeks-per-6-months (levels 65–67) figures above. They come from internal documents that recirculate on forums such as Blind, are periodically described as out of date, and have never been confirmed by Microsoft for any specific round. So when a figure like "39 weeks" gets quoted as the Microsoft severance number, it is a reported ceiling attached to a reported formula. It is useful for calibration, but it is the kind of number that should carry a label every single time, which most coverage drops.
The Level-Tier Math, as Reported
Because the level tiers are the only formula in circulation, it is worth showing what they sketch, with the heading doing the heavy lifting: this is the reported formula, not a Microsoft-confirmed one. Against an illustrative $175,000 base salary (~$3,365/week), the reported tiers work out roughly as below. These are illustrative estimates only, not statements of what any individual will receive, and actual packages vary in both directions (above these figures and below them):
| Tenure | Levels ≤64 (reported: 1 wk / 6 mo) | Levels 65–67 (reported: 2 wk / 6 mo) | |---|---|---| | 3 years | ~6 weeks → ~$20,000 | ~12 weeks → ~$40,000 | | 5 years | ~10 weeks → ~$34,000 | ~20 weeks → ~$67,000 | | 8 years | ~16 weeks → ~$54,000 | ~32 weeks → ~$108,000 | | 12 years | ~24 weeks → ~$81,000 | ~39 weeks (reported cap) → ~$131,000 |
Two cautions sit on that table in both directions. Upward: the ~39-week ceiling is a reported cap, and a higher-level or longer-tenured employee could be told a different number entirely. Downward: the tiers themselves are unconfirmed, the level boundaries are reported, and an actual offer may land under these figures. The table is a way to understand the shape of what's being reported (a starting point, not a final figure), not a schedule you can hold Microsoft to. For a version tuned to your own salary and level, the free severance calculator and the Microsoft severance page both produce illustrative estimates on the same basis.
The RSU Question
For tenured Microsoft staff, the cash formula above is frequently not the biggest number: the unvested equity is. Microsoft grants stock awards (RSUs) that vest over multiple years, and at any given moment a long-serving employee is carrying a meaningful unvested balance. The reported terms say vesting continues through the notice period, but that is reported, not confirmed, and it would recover only whatever happens to vest inside a 60-day-plus window, not the whole unvested balance.
The general rule at most employers is that unvested RSUs are forfeited at separation unless a package says otherwise, and where they land relative to your separation date can move the total more than the severance cheque. A rough illustration, and it is only that: for a tenured employee, one to three years of unvested RSUs can outweigh even the reported 39-week cash ceiling, sometimes by a multiple. The figure most worth quantifying before responding to anything isn't the weeks of pay; it's what sits unvested in the equity portal on the separation date, and which vest dates fall inside the notice period. Our guide to stock options and equity in severance covers the general mechanics; the specifics of any grant vary enormously and are worth confirming against your own award documents.
Why the WARN Notice Matters Here
Unlike the leaked severance numbers, the WARN notice filed with Washington's Employment Security Department is a primary source. The state's database records 605 affected jobs and an effective date of 4 September 2026, with the notice received on 6 July. As of this timing check on 12 September 2026, that effective date has passed. It is historical notice information, not a current signing deadline or proof of when a particular person's severance became payable.
The federal WARN Act (and Washington has its own framework) can require 60 days' advance notice for covered employers, generally those with at least 100 full-time employees, where a closing or mass layoff meets the separate event thresholds. Whether any particular round met those conditions, whether notice was adequate, and how an effective date interacts with pay and benefits are fact-specific legal questions, not something a formula answers. Our WARN Act overview explains the general framework, and the specifics of any individual situation are best reviewed with a licensed employment attorney in your state.
The Release and the Review Window
Any Microsoft severance payment is generally conditioned on signing a separation agreement that includes a release of claims. For workers 40 and over in a group exit programme, federal law (the OWBPA, 29 U.S.C. § 626(f)) sets minimum windows: at least 45 days to consider the agreement (21 days for an individual separation), 7 days to revoke after signing, and a written disclosure of the ages and job titles of who was and wasn't selected. Those are general statutory facts, not Microsoft-specific terms. Whether and how Microsoft's 2026 agreements applied them hasn't been publicly confirmed.
A release with material unvested RSUs at stake, or different dates in the offer and layoff notice, is the kind of situation many people choose to have reviewed before committing. Our note on age discrimination and severance 40 or older covers the review-window mechanics in general terms; whether to sign, and when, is a decision only you can make, ideally with advice this article deliberately doesn't provide.
Microsoft vs Meta, Google, Amazon in 2026
Peer comparisons help with calibration, but note the sourcing: the companies sit at very different points on the confirmed-versus-reported spectrum:
- Meta: its "16 weeks of base plus 2 weeks per year" formula is widely treated as company-confirmed, dating to its 2022 terms and reported to carry through its 2026 round. (Confirmed baseline; current-round application reported.)
- Google: published a formula once, in a January 2023 blog post (16 weeks + 2 weeks per year, at least 16 weeks of accelerated vesting), and has confirmed nothing for its 2025–26 buyout wave. (One confirmed figure, three years old.)
- Amazon: no published formula at all; the package centres on a reported ~90-day paid runway before separation, with a smaller employee-reported lump sum behind it. (Employee-reported.)
- Microsoft: no published formula, no confirmed figure for any round; only the leaked level tiers above. (Reported throughout.)
Microsoft's position is the least documented of the four: Meta has a confirmed baseline, Google has a dated one, Amazon at least has a confirmed structure, and Microsoft has neither a formula nor a runway it has stated in its own words. Our 2026 tech-layoff severance comparison puts the reported peer figures side by side.
Negotiation Angles
These are options and factors people commonly weigh, not recommendations; the right move depends on facts this article can't see:
- The unvested-RSU balance. Many people begin by quantifying what they'd forfeit at their separation date and which vest dates fall inside the reported notice period. For tenured staff that figure can exceed the cash severance, which makes it worth knowing whichever way a conversation goes.
- Which reported tier applies. Because the formula scales sharply at the level 64/65 boundary, some people ask directly how their level and service are being counted rather than assuming the leaked numbers apply as written.
- Healthcare and COBRA duration. The reported ~6 months of continuation plus 12 months of COBRA is a common discussion point given none of it is company-published.
- The review window. Where an agreement carries a signing deadline, many people 40+ use the statutory consideration period to have the release, the age-disclosure schedules, and any non-compete or non-solicit terms reviewed before signing.
- Unemployment interactions. A voluntary-separation exit can be treated differently from an involuntary layoff for unemployment purposes in some states, a state-specific question with real money attached. Our guide to severance and unemployment covers the general mechanics; the specifics are for an attorney in your state.
The Bottom Line
A Microsoft exit in 2026 is unusual for how little of it is confirmed. What's certain is the event: ~4,800 roles cut on 6 July, about 2.1% of the workforce, two-thirds of them in Xbox and gaming, four studios spun off, and 605 Washington jobs (493 in Redmond) on a 4 September WARN date. What's not confirmed is anything about the pay: the level tiers (up to ~39 weeks, scaled 1 or 2 weeks per 6 months), the 60-day notice, the ~6 months of healthcare plus 12 months of COBRA, the vesting-through-notice, and the separate ~12-weeks-plus-2-per-year Voluntary Separation Programme are all leaked or employee-reported, and Microsoft has published none of them. For many tenured employees the decisive number is none of those: it's the unvested RSUs that could forfeit at separation.
This article is a guide, not legal advice. Every figure above is an estimate drawn from the source named beside it, actual packages vary in both directions, and Microsoft has confirmed no 2026 severance formula. For a release with material unvested equity at stake, or an unresolved question about the historical 4 September notice date, a licensed employment attorney in your state can review the specifics against the actual offer.
For a starting-point estimate of what the reported tiers sketch for your own salary and level, see the Microsoft severance page and the free severance calculator; both produce illustrative estimates, not final figures.