Career recovery · 16 minute practical guide
Microsoft said it would eliminate about 4,800 roles; preserve your work evidence, verify internal options, protect benefits, and run an external search in parallel.
The answer first
Do not wait for an internal transfer before starting an external search. Save non-confidential proof of your scope and outcomes, get every separation deadline in writing, identify internal roles only through the access Microsoft actually gives you, and build an external target list at the same time. Microsoft said these roles were not being replaced by AI, but it also said AI is changing how work gets done—so show where you used AI responsibly without relabeling ordinary work as AI expertise.
July 6, 2026 · confirmed event facts
Swipe horizontally to view the Microsoft internal and external search map
| Question | What is known | Evidence boundary |
|---|---|---|
| Roles announced | Around 4,800 | Microsoft's July 6 company statement |
| Share of workforce | About 2.1% globally | Microsoft's stated estimate |
| Areas named | Mostly Commercial and XBOX; engineering structures also evolving | Company statement, not a complete role list |
| Internal redeployment context | More than 4,000 over the prior year, including 500 that month | Historical aggregate—not individual eligibility or a guarantee |
| AI claim | Microsoft said eliminated roles were not being replaced by AI | The same statement says AI is changing tasks and skill needs |
| Not publicly established | Individual severance, vesting, bonus, visa, device, or internal-application terms | Read your own documents and ask HR |
The first 24 hours
Check: You can explain each date without relying on memory or an expiring work account.
Check: Every resume claim can be supported without showing proprietary material.
Check: You have the policy or an HR answer for your own case.
Check: Your external search can continue even if an internal application stalls.
Saveable checklist · accessible text included
Swipe horizontally to view the full Microsoft checklist
| Window | Actions | Deliverable |
|---|---|---|
| First 24 hours | Save permitted documents; list every deadline; preserve personal contacts; write a non-confidential project inventory; avoid public speculation. | One private separation file and one evidence ledger |
| First 7 days | Confirm unemployment filing, health coverage, equity/bonus treatment, internal eligibility, visa implications if relevant, and two external role families. | Benefits decision calendar plus internal/external target lists |
| First 30 days | Create two resume versions; request references; run five evidence-led conversations weekly; apply selectively; track interviews and objections. | A measured search pipeline, not a spray-and-pray count |
Company-specific resume translation
| Evidence area | Weak or internal wording | What the next employer needs | Accuracy boundary |
|---|---|---|---|
| Commercial program ownership | Named internal initiative and stakeholder list | Customer segment, deployment stage, dependencies, decision made, and verified outcome | Do not imply ownership of revenue or adoption you only supported |
| XBOX or gaming work | Studio, platform, or feature shorthand | Player/customer problem, release scope, reliability or delivery constraint, and your contribution | Do not disclose unreleased products, roadmaps, or confidential player data |
| Engineering impact | Service name and Microsoft-specific architecture | System purpose, scale you can disclose, technical decision, reliability/security effect, and boundaries | Do not turn team-level improvements into personal results |
| AI-enabled work | Copilot or model name | Task changed, safeguards used, human review, quality check, and verified time or decision effect | Do not claim AI strategy or model expertise from ordinary tool use |
Build one evidence ledger first, then use the workflow in How to Tailor Your Resume Without Rewriting It Every Time. The employer, official title, dates, and verified facts stay fixed; the order and emphasis change for each role family.
Choose a path from evidence, not urgency
Keep the external search active until a written offer and transition terms exist.
Silence is not an offer, rejection, or extension of a deadline.
Lead with deployment evidence and customer constraints, not the Microsoft brand alone.
The same experience can signal very different capabilities depending on the target team.
Related company-layoff guides
U.S. benefits and document check
| Topic | Action | Boundary |
|---|---|---|
| Unemployment insurance | The state where you worked generally administers the claim; file promptly and answer with the facts in your notice. | Eligibility, amount, waiting periods, and treatment of severance vary by state. |
| Health coverage | Record the exact employer-plan end date and compare Marketplace special enrollment, COBRA, and any available spouse or partner plan. | HealthCare.gov says Marketplace enrollment is generally available within 60 days after job-based coverage ends; costs and eligibility vary. |
| Severance agreement | Read the payment schedule, release, confidentiality, non-disparagement, cooperation, return-of-property, and rehire terms before signing. | If a waiver includes legal claims—especially age claims—individual facts and federal or state rules can matter. Consider qualified counsel. |
| Retirement account | Inventory the plan, balance, fees, vesting, loan status, and plan contact before moving money. | The IRS lists several possible paths; taxes, penalties, and plan rules can make an irreversible withdrawal costly. |
Microsoft layoff FAQ
Microsoft explicitly said the eliminated roles were not being replaced by AI. It also said AI is changing tasks and skill needs. Treat those as two separate statements; neither tells you why one individual role was selected.
No. Pursue a documented internal path if you are eligible, but run an external search in parallel. Aggregate redeployment numbers do not guarantee placement, timing, or eligibility for an individual employee.
Do not use confidential metrics or materials. Use public facts, approved ranges, non-confidential scale, qualitative outcomes, or a truthful statement that details are confidential. Confirm policy when uncertain.
Use one factual sentence about the company restructuring, then move to your function, verified contribution, and target. Do not speculate about leadership motives or describe the event as a performance decision unless your documents say that.
Editorial method
Company-specific facts were checked against Microsoft's primary statement or securities filing where available; the Verizon count is attributed to Reuters. U.S. action steps use official federal sources. Reddit discussions informed recurring questions only and are not used to establish layoff counts, packages, or policy.
Sources reviewed
Primary July 6 statement for the announced role count, affected areas, redeployment context, and the company's AI wording.
Official candidate guidance; use current internal instructions if Microsoft provides a separate process to affected employees.
Federal overview directing workers to the unemployment program for the state where they worked.
Official comparison of Marketplace special enrollment and COBRA after job-based coverage ends.
Official guidance on knowing and voluntary waivers, including additional rules for certain workers age 40 or older.
Official overview of leaving funds in a plan, rolling over, withdrawing, or moving funds to an IRA.
Use the free analyzer to find visible evidence and gaps, then build a targeted version without inventing metrics, titles, skills, or layoff details.
