Microsoft's June 8 Rule of 70 Just Closed. 8,750 Names Are Walking by July 2.
Microsoft's first-ever Voluntary Retirement Program closed June 8. Here's who's actually in the pool, why they're not your usual layoff cohort, and how to source them.
Microsoft's first-ever Voluntary Retirement Program decision window closed June 8 at 11:59 PM Pacific. Roughly 8,750 long-tenured US employees signed (or didn't), separation agreements run June 9 through June 22, and the official termination date is July 2. If you've been bracing for another wave of AI-displaced juniors, stop. This cohort is the inverse.
What actually happened on June 8
Eligible employees got the offer on May 7 from Amy Coleman, Microsoft's EVP and Chief People Officer. Eligibility is the now-famous Rule of 70: age plus years of service totaling 70 or more, Level 67 (senior director equivalent) and below, excluding anyone on a sales incentive plan. That's about 7% of Microsoft's US workforce, the first program of its kind in the company's 51-year history.
The decision deadline was June 8 PT. Separation agreements are being signed between June 9 and June 22, with a rescission window through June 29. Last day worked is July 1. Official termination is July 2. Microsoft is taking a $900 million charge this quarter to fund it.
The severance is real money. Level 65 to 67 employees get two weeks of base pay per six months of service, with a floor of 8 weeks and a cap of 39 weeks. Level 64 and below get one week per six months on the same min/max. Then there's healthcare for up to five years (Microsoft pays Year 1, COBRA rates after), and unvested stock continues vesting for six months if the employee has under 24 years of service, twelve months if they have more.
This is not a layoff. It is self-selection with a cash floor. That single fact reshapes everything downstream.
Why this cohort is the opposite of what you're sourcing for
Most of 2026's layoff pools have skewed AI-adjacent or junior. Meta cut 8,000 on May 20 in an AI restructuring. Atlassian cut 1,600 and replaced its CTO with two AI-focused execs. Oracle eliminated up to 30,000 via 6 a.m. emails. Amazon signaled roughly 30,000 across Alexa, AWS, and Prime Video.
The Microsoft VRP is different in three ways that matter to a recruiter.
First, AI and Copilot teams are explicitly excluded. Engineers on Azure OpenAI Service, GitHub Copilot, and the Turing research group are staying. The March 2026 hiring freeze on Azure cloud and North American sales also exempted them. Whatever you've been told about Microsoft shedding AI talent, this program is the inverse.
Second, the Rule of 70 math disproportionately catches long-tenured employees in their fifties and sixties. These are the people who built pre-AI Microsoft: Windows XP era, Server and Tools division expansion, early Azure buildout. Their expertise centers on technologies and workflows Microsoft is systematically automating or deprecating, which is exactly why Satya Nadella has publicly called Microsoft's 220,000-plus headcount a "massive disadvantage" in the AI race.
Third, it's voluntary. They chose to leave. They are not displaced, not desperate, and they're sitting on 6 to 12 months of continued RSU vesting plus a year of fully paid healthcare. Speed-to-offer is not your edge here. Respect for tenure is.
This cohort isn't desperate. They have a cash floor, a year of healthcare, and a vest clock that keeps ticking after they leave.
Who is actually walking out the door
Strip away the AI press cycle and look at what level 67 and below, non-sales-incentive, long-tenure actually means inside Microsoft. You get a generalist enterprise infrastructure layer:
- Windows Server, System Center, on-prem identity and AD specialists
- Classic Azure infra (Azure Stack, Azure Pack, hybrid scenarios)
- Enterprise sales engineering and solution architects (the non-quota ones)
- Operations and ops generalists across cloud and field
- Long-tenured PMs and EMs in Server and Tools lineage products
You will not find these people by clicking "Azure" in a skills filter. Many of them list internal product codenames, defunct division names ("Server and Tools," "STB," "Windows Server"), or job titles that haven't existed externally for a decade. When we ran a narrow query for "Senior/Principal Azure infrastructure with current Microsoft tenure" against our own index, we got zero clean matches. The cohort is real. It's just under-tagged.
That's the sourcing problem in one sentence: the canonical skill picks miss the candidates you actually want. You need keyword-and-tenure searches, and you need to think in Microsoft's internal vocabulary, not LinkedIn's taxonomy. This is the specific friction Refolk was built for: you describe the person in plain English ("20-plus year Microsoft tenure, infrastructure or ops, not on a Copilot team, Redmond or remote") and get a ranked shortlist, instead of fighting with skill filters that were never designed for a Server and Tools veteran.
The comp anchoring trap
If you pull a Microsoft senior engineer's comp from Levels.fyi and see $230,000, you are reading the wrong number. A 20-year veteran at Level 64 to 65 is likely earning $140,000 to $160,000 base, with the rest in unvested stock. But they will quote total comp, not base, as their benchmark. They've been doing it for two decades.
This is where offers blow up in week two. You come in at $190,000 base thinking you're 35% above their cash comp. They hear "you cut my number by 17%." Both of you are technically right. Neither of you is going to close.
The fix is a structured comp conversation before you write the offer: cash floor (severance covers near-term runway), benefits continuity (they have a year of paid healthcare already), and a clear breakdown of base, bonus, and equity that maps to their actual cash burn, not their Microsoft total-comp benchmark.
The Medicare cliff is your hidden urgency calendar
Healthcare continuation under the VRP ends early if a participant becomes Medicare-eligible. For candidates in their early-to-mid 60s, that creates a hard reason to land somewhere with benefits before January 1, 2027. They may accept a lower base if the medical plan is real.
Candidates in their 50s have the opposite profile. They have a year of paid Microsoft healthcare, six to twelve months of continued vest, 8 to 39 weeks of severance, and no urgency. Some of them will take the summer off. The ones you actually convert in July are people with a specific reason to move now: a spouse's geography, a project they want to ship, or a Medicare countdown.
Segment the list by age band before you write a single message. The opener for a 62-year-old enterprise architect is not the opener for a 54-year-old ops lead.
"Azure on a resume" does not mean what you think it means
This is the single biggest screening mistake teams will make in July. Azure knowledge from inside Microsoft is not the same as Azure knowledge from the market. The gap is not certifications. It's internal tooling, proprietary APIs, and infrastructure assumptions that simply do not exist outside Redmond.
A 22-year Microsoft veteran who "ran Azure" may have spent a decade on a fabric layer no external customer can see. They are brilliant. They are also going to need 90 days of ramp to be productive in a normal cloud team that uses the public ARM API, Terraform, and the same managed services you do.
Screen for: external customer-facing experience, current AZ-104/AZ-305/AZ-400 certs (recent recerts are a tell), and any open source or community footprint. If they've been speaking at Ignite about a public product, they're probably portable. If their entire career is internal, you're hiring a deep specialist who needs a runway, not a plug-and-play architect.
Who is best positioned to buy
Not AI startups. The fit is wrong on every axis: tenure, comp expectations, comfort with chaos, and stack.
The natural buyers are regulated and enterprise:
- Microsoft partner ecosystem: Avanade, Insight, and the SADA-equivalent shops. These firms speak the internal Microsoft dialect and have client demand that maps exactly to the cohort's skills.
- Federal integrators: CACI, Leidos, Booz Allen. Many of these candidates are security-clearable, and the federal Azure Government practice is a near-direct lift.
- Regulated enterprise IT: JPMorgan tech, UnitedHealth/Optum, Boeing IT. They run hybrid environments where Windows Server depth is still load-bearing.
- PE-backed enterprise software: ISVs with Azure-heavy roadmaps that need architects who can actually negotiate with a Microsoft field team.
The off-ramp infrastructure for this cohort is more mature than most recruiters realize. Wealth advisors like Avier, TrueWealth, and Gevers Wealth have been running VRP decision webinars for weeks. Your candidate already has a financial plan. They are not hunting; they are choosing.
The 21-day playbook
Publication date to July 2 is roughly three weeks. Here is what actually moves the needle.
Build the list in internal-Microsoft vocabulary
Search by tenure, division lineage, and internal product names, not LinkedIn skill picks. "Server and Tools," "Windows Azure" (yes, the old name), "System Center," "Azure Stack Hub," "MSIT," "CSEO." This is the kind of plain-English-to-shortlist query Refolk handles well: skip the boolean and just describe the person.
Segment by age band before you write the first message
60+ with Medicare pressure gets the benefits-forward opener. 50s with no pressure gets the project-forward opener. Don't send one template to both.
Lead with respect for tenure, not urgency
These candidates have heard "we move fast" their entire careers and learned to distrust it. The opener that works is specific: name the product they shipped, the codename they owned, the team they ran. If you can't name it, you're not ready to send the message yet, which is another place sourcing tools like Refolk earn their keep, by surfacing the team and product context alongside the profile.
Pre-negotiate comp framing
Before the first call, decide how you're going to frame base, bonus, and equity against their Microsoft total-comp anchor. If you can't make the math feel respectful, push the conversation to August. The cohort will still be there. They are not in a hurry.
FAQ
Is the Microsoft VRP a layoff?
No. It is a voluntary buyout. Eligible employees chose whether to accept. That changes the candidate's psychology, their leverage, and their timeline. They have a cash severance floor (8 to 39 weeks), Year 1 healthcare paid, and 6 to 12 months of continued RSU vesting. Counter-offer dynamics look nothing like the displaced cohorts coming out of Meta or Oracle this year.
How is this cohort different from other 2026 tech layoffs?
The other 2026 cuts skewed toward AI-adjacent restructurings or younger workers. The Microsoft VRP is the inverse: long-tenured employees in their fifties and sixties, concentrated in enterprise infrastructure, operations, and pre-AI Microsoft products. AI and Copilot teams are explicitly excluded. If you're sourcing ex-Microsoft engineers for an AI startup, you're fishing in the wrong pool.
When do these candidates actually become available?
Separation agreements run June 9 to June 22, with a rescission window through June 29. Last day worked is July 1. Official termination is July 2. They are technically employed through that date and most will not engage in serious conversations until late June. The right time to be in their inbox is now, with the goal of a July conversation, not an immediate offer.
Why don't standard sourcing filters surface these people?
Because their internal Microsoft vocabulary doesn't map to LinkedIn's skill taxonomy. A 20-year veteran who built Azure Stack may have "Cloud Computing" listed and nothing else useful. You have to search by tenure, division lineage, and internal product names, which is exactly the kind of plain-English query Refolk is built to answer: describe the person, get the shortlist.