Uptime Report Research · Layoff record

Microsoft Layoff History Timeline: Notices in 8 of 13 Years, and a July Filing in 3 of the Last 4

This Microsoft layoff history timeline runs to November 2, 2026. State WARN files name 14,964 workers at Microsoft and its subsidiaries since 2014, in 8 of 13 years and every year since 2023. The newest notice, dated September 22, covers 277 Redmond positions ending November 21. Microsoft’s largest 2026 round, on July 6, was about 4,800 roles.

  1. Oct 26, 2026~60,000eligible for a Voluntary Exit Offer, per an unnamed CNBC source. Exits on Dec 31.
  2. Sep 22, 2026277Redmond positions in a Washington notice. Separations Nov 21.
  3. Jul 6, 20264,800roles stated by Microsoft. Notices dated that day name 1,036 in three states.
  4. Jun 30, 2026223,000people, down 5,000 in a year. 4,000 of the drop was U.S.

Microsoft’s fiscal year starts July 1, so the record below is arranged by fiscal year, then listed date by date. Three kinds of evidence are kept apart: notices Microsoft filed with states, numbers in Microsoft’s own documents, and numbers only reported by the press. For how Microsoft ranks against other employers in the same notice files, see our tracker of tech layoffs in 2026.

Every Microsoft round on one line, 2009 to 2026

Microsoft’s own number or spokesperson Press-reported number WARN notices by date WARN notices dated in July

200920112013201520172019202120232025CompanyPressWARN by dateJan 22, 2009: 5,000. Company document5,000Jul 17, 2014: 18,000. Company document18,000Jul 8, 2015: 7,800. Company document7,800May 25, 2016: 1,850. Company documentJul 28, 2016: 2,850. Company documentJan 18, 2023: 10,000. Company document10,000Jan 25, 2024: 1,900. Press, unconfirmedSep 12, 2024: 650. Press, unconfirmedMay 13, 2025: 6,000. Spokesperson to press6,000Jul 2, 2025: 9,000. Press, unconfirmed9,000Jul 6, 2026: 4,800. Company document4,800Jan 23, 2009: 872 workers in WARN noticesApr 1, 2009: 2 workers in WARN noticesMay 5, 2009: 1,200 workers in WARN noticesSep 3, 2009: 27 workers in WARN noticesJul 17, 2014: 1,729 workers in WARN noticesSep 17, 2014: 94 workers in WARN noticesSep 18, 2014: 813 workers in WARN noticesOct 29, 2014: 175 workers in WARN noticesOct 30, 2014: 635 workers in WARN noticesJul 8, 2015: 129 workers in WARN noticesOct 21, 2015: 4 workers in WARN noticesJan 20, 2016: 2 workers in WARN noticesAug 21, 2020: 29 workers in WARN noticesJan 18, 2023: 924 workers in WARN noticesFeb 9, 2023: 679 workers in WARN noticesFeb 14, 2023: 91 workers in WARN noticesMar 6, 2023: 745 workers in WARN noticesMar 27, 2023: 580 workers in WARN noticesMay 9, 2023: 158 workers in WARN noticesJun 5, 2023: 24 workers in WARN noticesJun 21, 2023: 187 workers in WARN noticesJul 10, 2023: 316 workers in WARN noticesDec 15, 2023: 438 workers in WARN noticesJan 25, 2024: 897 workers in WARN noticesApr 8, 2024: 31 workers in WARN noticesMay 7, 2024: 96 workers in WARN noticesSep 12, 2024: 393 workers in WARN noticesMay 13, 2025: 2,071 workers in WARN noticesMay 27, 2025: 281 workers in WARN noticesJun 2, 2025: 313 workers in WARN noticesJul 2, 2025: 903 workers in WARN noticesJul 3, 2025: 164 workers in WARN noticesAug 4, 2025: 40 workers in WARN noticesAug 18, 2025: 62 workers in WARN noticesSep 8, 2025: 42 workers in WARN noticesMay 15, 2026: 606 workers in WARN noticesJul 6, 2026: 1,036 workers in WARN noticesSep 22, 2026: 277 workers in WARN noticesJul 6, 2026

Circle area scales with the number of positions or workers. Hover for dates and counts. California files before fiscal 2015 were not available, so the 2009 WARN circles are Washington only.

Does Microsoft lay off every year?

No, but it has for four years running. Notices exist for 8 of the 13 calendar years from 2014 to 2026. The empty years are 2017, 2018, 2019, 2021, 2022. Notices in Microsoft’s own name exist for 6 years (2014, 2015, 2016, 2023, 2025, 2026). The rest come from subsidiaries: LinkedIn in 2020, and Activision Blizzard and ZeniMax’s Arkane Austin in 2024.

Fiscal year (Jul to Jun) WARN workers Notice dates People at Jun 30 (10-K) Change Revenue per person Stated or reported round Charge in filings
FY2015 3,446 5 118,000 -10,000 $793K Up to 18,000 (Jul 2014) $2.5B integration and restructuring
FY2016 135 3 114,000 -4,000 $800K Up to 7,800 (Jul 2015); up to 1,850 (May 2016) $480M restructuring
FY2017 0 0 124,000 +10,000 $779K About 2,850 (Jul 2016) $306M severance
FY2018 0 0 131,000 +7,000 $842K None we could find
FY2019 0 0 144,000 +13,000 $874K None we could find
FY2020 0 0 163,000 +19,000 $877K None we could find
FY2021 29 1 181,000 +18,000 $929K None we could find
FY2022 0 0 221,000 +40,000 $897K None we could find
FY2023 3,388 8 221,000 0 $959K 10,000 (Jan 2023) $800M severance, inside a $1.2B charge
FY2024 1,778 5 228,000 +7,000 $1,075K About 1,900 gaming, press (Jan 2024) None we could find
FY2025 3,058 4 228,000 0 $1,236K 650 gaming, press (Sep 2024); about 6,000, spokesperson (May 2025) None we could find
FY2026 1,817 6 223,000 -5,000 $1,488K About 9,000, press (Jul 2025); retirement program (Apr 2026) About $900M retirement program guided; actual lower, not stated
FY2027 (to Oct 29) 1,313 2 not reported yet 4,800 (Jul 2026); Voluntary Exit Offer (Oct 2026) None we could find

WARN workers are grouped by notice date. Headcount is the “employed approximately” sentence in each Form 10-K, rounded by Microsoft, and rises include acquired staff such as LinkedIn in FY2017, Nuance in FY2022 and Activision Blizzard in FY2024. “None we could find” means no dollar figure in that year’s 10-K, 10-Qs or earnings releases, not that no severance was paid.

Headcount fell in 3 of the last 12 fiscal years (FY2015, FY2016, FY2026). FY2015 and FY2016 followed the phone-business plans. FY2026 had press-reported cuts of about 9,000 and the retirement program, for a net fall of 5,000. Headcount went from 228,000 to 223,000, with U.S. staff down from 125,000 to 121,000 and international staff from 103,000 to 102,000. Revenue per person more than doubled from $678K in FY2014 to $1,488K in FY2026, so the 223,000 people today produce $332B of revenue.

How often does Microsoft lay off?

Since January 2023, Microsoft or a subsidiary has filed on 25 separate notice dates in 46 months, or about one every 1.8 months. Filing is not evenly spread: 10 dates in 2023, 4 in 2024, 8 in 2025 and 3 so far in 2026. A single round often produces several notices. After the January 2023 announcement of 10,000 cuts, Washington received seven Microsoft notices between January 18 and July 10.

Testing the July pattern

Jan: 1,823 workers on 3 notice dates, 2014 to 2026Jan1,823Feb: 770 workers on 2 notice dates, 2014 to 2026Feb770Mar: 1,325 workers on 2 notice dates, 2014 to 2026Mar1,325Apr: 31 workers on 1 notice dates, 2014 to 2026Apr31May: 3,212 workers on 5 notice dates, 2014 to 2026May3,212Jun: 524 workers on 3 notice dates, 2014 to 2026Jun524Jul: 4,277 workers on 6 notice dates, 2014 to 2026Jul4,277Aug: 131 workers on 3 notice dates, 2014 to 2026Aug131Sep: 1,619 workers on 5 notice dates, 2014 to 2026Sep1,619Oct: 814 workers on 3 notice dates, 2014 to 2026Oct814Nov: 0 workers on 0 notice dates, 2014 to 2026NovDec: 438 workers on 1 notice dates, 2014 to 2026Dec438

Workers in WARN notices by month of the notice date, all states checked, 2014 to 2026.

The pattern holds up, with limits. July is the largest month, at 4,277 of 14,964 noticed workers (29%, against 8% for an even spread). A July notice exists in 5 of 8 notice years, always in the first 17 days of the new fiscal year: Jul 17, 2014, Jul 8, 2015, Jul 10, 2023, Jul 2, 2025, Jul 6, 2026. It is missing in 2016, 2020, 2024. July was not the biggest month in 2023 (Mar) or 2025 (May): only 2014, 2015, 2026 peaked in July. Anyone watching only July would have missed the larger May 2025 notice of 1,985.

Every round, date by date

65 entries, newest first, with stated rounds beside the notices that followed. Numbers from different evidence types overlap and must not be added together.

Date Evidence Number What the record says
Oct 26, 2026 Spokesperson to press not stated Voluntary Exit Offer in the U.S., Canada, India and the UK. Staff decide in early December and leave December 31. About 60,000 eligible, per an unnamed source. CNBC; memo; FY27 Q1 call.
Sep 22, 2026 WARN notice 277 Redmond. Separations from Nov 21, 2026. Washington ESD.
Jul 6, 2026 WARN notice 52 Obsidian, a Microsoft subsidiary. Irvine. Separations from Sep 4, 2026. California EDD.
Jul 6, 2026 WARN notice 379 ZeniMax, a Microsoft subsidiary. 2 sites. Separations from Sep 4, 2026. Maryland DOL.
Jul 6, 2026 WARN notice 605 Redmond. Separations from Sep 4, 2026. Washington ESD.
Jul 6, 2026 Company document 4,800 About 4,800 roles, 2.1% of staff, mostly Commercial and Xbox. Xbox alone cuts about 3,200 through fiscal 2027, 1,600 of them that day. Microsoft blog; Xbox post.
May 15, 2026 WARN notice 606 LinkedIn, a Microsoft subsidiary. 5 California sites. Separations from Jul 13, 2026. California EDD.
Apr 29, 2026 Company document not stated First Voluntary Retirement Program. The CFO guided to about $900M of one-time cost. Microsoft later said more than 30% of those eligible took it. FY26 Q3 earnings call.
Sep 8, 2025 WARN notice 42 Redmond. Separations from Nov 7, 2025. Washington ESD.
Aug 18, 2025 WARN notice 62 ZeniMax, a Microsoft subsidiary. Cockeysville. Separations from Oct 15, 2025. Maryland DOL.
Aug 4, 2025 WARN notice 40 Redmond. Separations from Oct 3, 2025. Washington ESD.
Jul 3, 2025 WARN notice 164 ZeniMax, a Microsoft subsidiary. Rockville. Separations from Sep 1, 2025. Maryland DOL.
Jul 2, 2025 WARN notice 73 Activision Blizzard, a Microsoft subsidiary. Irvine. Separations from Aug 31, 2025. California EDD.
Jul 2, 2025 WARN notice 830 Redmond and Bellevue. Separations from Aug 31, 2025. Washington ESD.
Jul 2, 2025 Press, unconfirmed 9,000 About 9,000, under 4% of staff, on the second day of fiscal 2026. The number came from a person familiar with the matter. The spokesperson did not state it. CNBC, unconfirmed number.
Jun 2, 2025 WARN notice 8 2 California sites. Separations from Aug 1, 2025. California EDD.
Jun 2, 2025 WARN notice 305 Redmond. Separations from Aug 1, 2025. Washington ESD.
May 27, 2025 WARN notice 281 LinkedIn, a Microsoft subsidiary. 4 California sites. No later separation date on file. California EDD.
May 13, 2025 WARN notice 86 3 California sites. Separations from Jul 12, 2025. California EDD.
May 13, 2025 WARN notice 1,985 Redmond. Separations from Jul 12, 2025. Washington ESD.
May 13, 2025 Spokesperson to press 6,000 About 6,000 jobs, 3% of staff, across levels, teams and geographies. A spokesperson gave the reason to CNBC. CNBC, with spokesperson statement.
Sep 12, 2024 WARN notice 393 Activision Blizzard, a Microsoft subsidiary. 3 California sites. Separations from Oct 11, 2024. California EDD.
Sep 12, 2024 Press, unconfirmed 650 650 at Microsoft Gaming, largely corporate and support roles, in a memo from Phil Spencer. Fortune, citing the memo.
May 7, 2024 WARN notice 96 ZeniMax (Arkane Austin), a Microsoft subsidiary. Austin. Separations from Jul 6, 2024. Texas TWC.
Apr 8, 2024 WARN notice 31 Activision Blizzard, a Microsoft subsidiary. 4 California sites. Separations from Jun 7, 2024. California EDD.
Jan 25, 2024 WARN notice 897 Activision Blizzard, a Microsoft subsidiary. 6 California sites. Separations from Mar 30, 2024. California EDD.
Jan 25, 2024 Press, unconfirmed 1,900 About 1,900 at Microsoft Gaming after the Activision deal. The total is derived from Fortune’s running count of 2,550 less the September 650. Fortune, September 2024.
Dec 15, 2023 WARN notice 438 LinkedIn, a Microsoft subsidiary. 4 California sites. Separations from Dec 15, 2023. California EDD.
Jul 10, 2023 WARN notice 40 Mountain View. Separations from Sep 8, 2023. California EDD.
Jul 10, 2023 WARN notice 276 Redmond and Bellevue. Separations from Sep 8, 2023. Washington ESD.
Jun 21, 2023 WARN notice 187 LinkedIn, a Microsoft subsidiary. 3 California sites. No later separation date on file. California EDD.
Jun 5, 2023 WARN notice 2 Mountain View. Separations from Aug 4, 2023. California EDD.
Jun 5, 2023 WARN notice 22 Redmond. Separations from Aug 4, 2023. Washington ESD.
May 9, 2023 WARN notice 158 Redmond. Separations from May 26, 2023. Washington ESD.
Mar 27, 2023 WARN notice 21 3 California sites. Separations from May 26, 2023. California EDD.
Mar 27, 2023 WARN notice 559 Redmond and Bellevue. Separations from May 26, 2023. Washington ESD.
Mar 6, 2023 WARN notice 56 3 California sites. Separations from May 5, 2023. California EDD.
Mar 6, 2023 WARN notice 689 Redmond, Bellevue, Issaquah. Separations from May 5, 2023. Washington ESD.
Feb 14, 2023 WARN notice 91 LinkedIn, a Microsoft subsidiary. 3 California sites. No later separation date on file. California EDD.
Feb 9, 2023 WARN notice 62 7 California sites. Separations from Apr 10, 2023. California EDD.
Feb 9, 2023 WARN notice 617 Redmond, Bellevue, Issaquah. Separations from Apr 10, 2023. Washington ESD.
Jan 18, 2023 WARN notice 46 4 California sites. Separations from Mar 20, 2023. California EDD.
Jan 18, 2023 WARN notice 878 Redmond, Bellevue, Issaquah. Separations from Mar 20, 2023. Washington ESD.
Jan 18, 2023 Company document 10,000 10,000 jobs through the end of fiscal Q3, under 5% of staff. $1.2B charge, $800M of it severance. Form 8-K, Exhibit 99.1 (Nadella email).
Aug 21, 2020 WARN notice 29 LinkedIn, a Microsoft subsidiary. Sunnyvale. Separations from Aug 21, 2020. California EDD.
Jul 28, 2016 Company document 2,850 About 2,850 further roles globally during fiscal 2017, on top of the 1,850. Fiscal 2016 Form 10-K.
May 25, 2016 Company document 1,850 Up to 1,850 jobs in smartphone hardware, up to 1,350 of them in Finland. Charge of about $950M, about $200M of it severance. Form 8-K, Exhibit 99.1.
Jan 20, 2016 WARN notice 2 San Diego. Separations from Mar 20, 2016. California EDD.
Oct 21, 2015 WARN notice 4 San Diego. Separations from Dec 20, 2015. California EDD.
Jul 8, 2015 WARN notice 129 San Diego. Separations from Sep 6, 2015. California EDD.
Jul 8, 2015 Company document 7,800 Up to 7,800 positions, mainly the phone business, with an impairment charge of about $7.6B. Form 8-K, Exhibit 99.1.
Oct 30, 2014 WARN notice 635 Redmond. Separations from Dec 28, 2014. Washington ESD.
Oct 29, 2014 WARN notice 175 3 California sites. Separations from Dec 28, 2014. California EDD.
Sep 18, 2014 WARN notice 66 2 California sites. Separations from Nov 17, 2014. California EDD.
Sep 18, 2014 WARN notice 747 Redmond. Separations from Nov 17, 2014. Washington ESD.
Sep 17, 2014 WARN notice 94 Mountain View. Separations from Nov 17, 2014. California EDD.
Jul 17, 2014 WARN notice 378 San Diego. Separations from Sep 15, 2014. California EDD.
Jul 17, 2014 WARN notice 1,351 Redmond. Separations from Sep 15, 2014. Washington ESD.
Jul 17, 2014 Company document 18,000 Up to 18,000 positions over a year, about 12,500 of them from the Nokia devices business. Pre-tax charge of $1.1B to $1.6B. Form 8-K, Item 2.05.
Sep 3, 2009 WARN notice 27 Redmond. Separations from Nov 1, 2009. Washington ESD.
May 5, 2009 WARN notice 1,200 Redmond. Separations from Jul 4, 2009. Washington ESD.
Apr 1, 2009 WARN notice 2 Seattle. Separations from Jun 30, 2009. Washington ESD.
Jan 23, 2009 WARN notice 872 Redmond. Separations from Mar 23, 2009. Washington ESD.
Jan 22, 2009 Company document 5,000 Up to 5,000 positions over 18 months, 1,400 that day, across R&D, marketing, sales, finance, legal, HR and IT. Form 8-K, Exhibit 99.2 (Ballmer email).
Aug 23, 2004 WARN notice 67 Redmond. Separations from Oct 25, 2004. Washington ESD.

WARN rows group a filer’s sites by state and notice date, using the employer’s notice date. Earlier-than-notice separation dates appear in LinkedIn’s California filings, so those rows carry no later date.

Washington: where the Redmond and Bellevue cuts were filed

Washington holds 67% of noticed workers since 2014 (10,016 of 14,964), and its database goes back to 2004. Since May 2025, the cover letters have split in-office positions from remote workers living in the Puget Sound area. 914 of 4,084 positions in those seven letters (22%) were remote.

Received Location as filed Workers In-office Remote Remote share Layoff start Document
Sep 22, 2026 Redmond 277 252 25 9% Nov 21, 2026 Database entry
Jul 6, 2026 Redmond 605 493 112 19% Sep 4, 2026 Notice PDF
Sep 8, 2025 Redmond 42 33 9 21% Nov 7, 2025 Notice PDF
Aug 4, 2025 Redmond 40 29 11 28% Oct 3, 2025 Notice PDF
Jul 2, 2025 Redmond and Bellevue 830 601 229 28% Aug 31, 2025 Notice PDF
Jun 2, 2025 Redmond 305 252 53 17% Aug 1, 2025 Notice PDF
May 13, 2025 Redmond 1,985 1,510 475 24% Jul 12, 2025 Notice PDF
Jul 10, 2023 Redmond and Bellevue 276 n/a n/a Sep 8, 2023 Grid entry only
Jun 5, 2023 Redmond 22 n/a n/a Aug 4, 2023 Grid entry only
May 9, 2023 Redmond 158 n/a n/a May 26, 2023 Grid entry only
Mar 27, 2023 Redmond and Bellevue 559 n/a n/a May 26, 2023 Grid entry only
Mar 6, 2023 Redmond, Bellevue, Issaquah 689 n/a n/a May 5, 2023 Grid entry only
Feb 9, 2023 Redmond, Bellevue, Issaquah 617 n/a n/a Apr 10, 2023 Grid entry only
Jan 18, 2023 Redmond, Bellevue, Issaquah 878 n/a n/a Mar 20, 2023 Grid entry only
Oct 30, 2014 Redmond 635 n/a n/a Dec 28, 2014 Grid entry only
Sep 18, 2014 Redmond 747 n/a n/a Nov 17, 2014 Grid entry only
Jul 17, 2014 Redmond 1,351 n/a n/a Sep 15, 2014 Grid entry only
Sep 3, 2009 Redmond 27 n/a n/a Nov 1, 2009 Grid entry only
May 5, 2009 Redmond 1,200 n/a n/a Jul 4, 2009 Grid entry only
Apr 1, 2009 Seattle 2 n/a n/a Jun 30, 2009 Grid entry only
Jan 23, 2009 Redmond 872 n/a n/a Mar 23, 2009 Grid entry only
Aug 23, 2004 Redmond 67 n/a n/a Oct 25, 2004 Grid entry only
All Washington notices, 2004 to November 2026 12,184 3,170 914 22% of letters

n/a: the state grid gives no cover letter for that year, so no split is available.

The August and September 2025 attachments list 25 different buildings for just 82 positions, from numbered Redmond campus buildings to One Esterra and Studio A, B, D and G. The 2026 letters name only One Microsoft Way. Bellevue and Issaquah appear in location labels in 2023 and 2025, never alone, so no Bellevue-only total can be computed from the state’s data.

Other states and subsidiaries

Site Filer Workers Notice dates First Latest
Mountain View, CA LinkedIn 942 5 Feb 2023 May 2026
Irvine, CA Activision Blizzard 707 4 Jan 2024 Jul 2025
San Diego, CA Microsoft 680 6 Jul 2014 Jan 2016
Mountain View, CA Microsoft 413 10 Sep 2014 Jun 2025
Santa Monica, CA Activision Blizzard 333 3 Jan 2024 Sep 2024
Sunnyvale, CA LinkedIn 332 6 Aug 2020 May 2026
Rockville, MD ZeniMax 330 2 Jul 2025 Jul 2026
San Francisco, CA LinkedIn 321 5 Feb 2023 May 2026
Cockeysville, MD ZeniMax 275 2 Aug 2025 Jul 2026
Los Angeles, CA Activision Blizzard 143 1 Sep 2024 Sep 2024
Austin, TX ZeniMax (Arkane Austin) 96 1 May 2024 May 2024
Novato, CA Activision Blizzard 85 1 Jan 2024 Jan 2024
San Mateo County office, CA Activision Blizzard 76 1 Jan 2024 Jan 2024
Sunnyvale, CA Microsoft 67 3 Sep 2014 Jun 2025

LinkedIn’s May 15, 2026 filing of 606 California workers is the largest single-state filing of 2026 in this ledger, one more than Microsoft’s July notice in Washington, and it landed seven weeks earlier. On July 6, 2026 ZeniMax filed for 379 in Maryland (213 in Cockeysville, 166 in Rockville), on the same date Microsoft filed in Washington and Obsidian filed for 52 in Irvine.

Which teams the 2026 notices name

The two 2026 Washington notices carry a per-position job title. Parsing them gives exact counts: 605 of 605 and 277 of 277, matching the letters. We publish only title counts. Names and home addresses are confidential in these filings, and we did not keep them.

Job family (our grouping) Jul 6, 2026 Share Sep 22, 2026 Share
Engineering and data 217 36% 80 29%
Product and program management 181 30% 37 13%
Sales and partner roles 60 10% 0 0%
Marketing and communications 39 6% 34 12%
Design, research and writing 42 7% 29 10%
Game art, design and production 7 1% 77 28%
Business, finance, HR and support 59 10% 20 7%
All positions 605 100% 277 100%

The two notices look different. July’s top titles are Software Engineering (133), Product Management (82), Business Program Management (51), Technical Program Management (34), Product Design (22), which fits Microsoft’s own description of changes “mostly” in Commercial and Xbox, with engineering restructured as well. September’s are Software Engineering (60), Art (29), Technical Writing (20), Game Producers (19), Game Design (16). Game art, design and production went from 7 positions (1%) to 77 (28%). Microsoft has not said what the September notice is for. These titles are consistent with part of the remaining 1,600 Xbox cuts, but that is our inference, not a filing statement. Managers were 20% of July positions and 21% of September’s.

WARN totals versus company-announced totals

Round Stated or reported Basis WARN workers in window WARN share
January 2009 plan 5,000 Company, 8-K exhibit 2,101 42%
July 2014 plan 18,000 Company, 8-K Item 2.05 3,446 19%
July 2015 plan 7,800 Company, 8-K exhibit 135 2%
January 2023 round 10,000 Company, 8-K exhibit 3,704 37%
May and July 2025 rounds 15,000 Press (6,000 + 9,000), CNBC 3,876 26%
July 2026 round, that date only 4,800 Company, Microsoft blog 1,036 22%

WARN never comes close to the global number, because the company figure is worldwide and notices are per state. The 2014 plan’s 18,000 included about 12,500 Nokia positions. The WARN share here is a coverage measure and should not be read as a U.S. count. A tracker that adds notices can double up as well: WARNTracker’s Microsoft page lists 18,179 workers, but several rows repeat one notice under its layoff date, such as 1,985 on both May 13 and July 12, 2025. Our 2014-to-2026 count of 14,964 removes those repeats and adds subsidiaries.

Severance dollars and what filings say next

Microsoft has put a dollar figure on severance only for some rounds. The 2014 plan guided to $750M to $800M of severance. The 2016 charge carried about $200M. FY2017 shows $306M. The January 2023 charge carried $800M. For 2025 and for the July 2026 round we found no severance amount in any 10-K, 10-Q or earnings release. The July 29, 2026 earnings release says only that “lower-than-expected expenses related to the Voluntary Retirement Program” were partly offset by “severance expense and impairment charges in XBOX”, and FY26 operating expense rose in part on “impairment and other related expenses” at Xbox. The retirement program was guided at roughly $900 million on the April call, split about $350M in cost of revenue and $550M in operating expenses.

On further cuts, the documents are direct. Amy Coleman’s July 6 post says “there will be more changes ahead; other parts of our business will need to make similar changes.” The CFO said in April that headcount “will decrease year-over-year” in fiscal 2027, and on the July call that total headcount “declined 2% year-over-year”. The October 28 call says fiscal Q2 cost guidance “includes an estimate” for the Voluntary Exit Offer, with no amount given. Microsoft has used Form 8-K Item 2.05, the SEC’s item for exit and restructuring costs, only once since 2014: on July 17, 2014. The 2023 round went under Item 7.01, and the 2025 and 2026 rounds drew no 8-K of their own. Coleman also wrote that the eliminated roles “are not being replaced by AI”, a claim worth setting beside employers’ statements in our AI layoffs ledger.

What this means for MSPs

The checkable part: 60 of the 605 July positions in Washington were sales and partner titles, 25 of them with “Partner” in the title. Microsoft described the July cuts as mostly Commercial and Xbox. Advice, not a finding: if you rely on a named Microsoft partner contact, confirm that person and their backup now, and do it again after December 31, when Voluntary Exit Offer departures take effect. Do not plan for reduced Microsoft 365 or Azure support from these numbers alone: nothing in these filings measures support capacity.

Frequently asked questions

Does Microsoft lay off every year?

Not across its history, but it has since 2023. WARN notices from Microsoft or a subsidiary exist for 8 of the 13 calendar years from 2014 to 2026. There are none in 2017, 2018, 2019, 2021 or 2022 in the states we checked. Notices appear in every year from 2023 to 2026.

How often does Microsoft lay off?

Since January 2023 Microsoft or a subsidiary has filed WARN notices on 25 separate dates, about one every 1.8 months. In 2023 alone there were 10 notice dates. Across the whole 2014 to 2026 record there were 34 dates in 8 years.

Does Microsoft lay off every July?

Often, not always. A July notice exists in 5 of the 8 notice years (2014, 2015, 2023, 2025, 2026), each in the first 17 days of the fiscal year that starts July 1. July holds 29% of noticed workers since 2014, against 8% if months were even. But July was the biggest month in only 3 of those 5 years.

How many people has Microsoft laid off in 2026?

Microsoft stated about 4,800 roles on July 6, 2026, or 2.1% of staff, and Xbox said it will cut about 3,200 through fiscal 2027. WARN notices dated 2026 name 1,919 workers: 1,036 on July 6, 277 on September 22 and 606 at LinkedIn on May 15.

Why do WARN totals sit far below Microsoft’s announced numbers?

Company figures are global and WARN is per state and per site. Across six rounds, the notices we found equal 2% to 42% of the stated or reported total. Washington alone is 67% of noticed workers since 2014, and many U.S. states we could not reach or that post no list are absent.

Will Microsoft lay off more people?

Its own statements say more change is coming. Chief people officer Amy Coleman wrote on July 6, 2026 that other parts of the business will need to make similar changes. The CFO said on the April 2026 call that headcount will fall year over year in fiscal 2027. Xbox has about 1,600 cuts left to make through fiscal 2027, and the Voluntary Exit Offer closes December 31.

Download the data. microsoft-layoff-history-ledger.csv (CSV). Licensed under CC BY 4.0: free to reuse with attribution to The Uptime Report.

Methodology

Sources and dates. Retrieved November 2, 2026. Washington ESD WARN database (all 1,550 grid rows, January 2004 to October 29, 2026, plus every notice PDF available for Microsoft). California EDD fiscal-year PDFs from July 2014 and the current spreadsheet through October 28, 2026. New York DOL dashboard export, notice years 2019 to 2026. Texas open-data WARN file, 2019 to June 23, 2026. Maryland DOL annual tables, 2014 to October 29, 2026. SEC EDGAR: every Microsoft 10-K and 10-Q from 2014, and the 8-Ks linked here. Microsoft blog, Xbox Wire and investor event pages.

States checked. Complete files read: Washington, California, New York, Texas and Maryland. We found no Microsoft-group row in New York or, since 2019, in Texas other than Arkane. Pages opened with no usable employer list, or blocked: Virginia, Georgia, Oregon, Colorado, Illinois, Massachusetts, Michigan, Pennsylvania, Nebraska, Iowa, Utah, Wisconsin, Minnesota, Ohio, New Jersey, Tennessee, Florida, D.C. and North Carolina (2026 list read, no match). So this ledger is a floor. WARNTracker lists Microsoft notices in Wilsonville, Oregon in 2017 and we could not confirm them because Oregon’s database timed out, so they are excluded from our totals and from the year count. If confirmed, 2017 would join the notice years.

Rule for what counts. A notice counts when the filer is Microsoft or a subsidiary Microsoft owned on the notice date. Close dates from Microsoft’s 10-Ks: LinkedIn December 8, 2016; GitHub October 25, 2018; Nuance March 2022; Activision Blizzard October 13, 2023. ZeniMax is counted from March 9, 2021, and Obsidian as an Xbox Game Studios studio, judged by its site’s shop and legal links. No GitHub or Nuance notice appears in these files. Excluded: earlier Blizzard and Activision notices before the deal closed (2018 to 2021), a 2015 ZeniMax notice, and contractors at Microsoft sites, including a TCWGlobal notice of July 3, 2025 for 30 workers contracted by ZeniMax. All other Microsoft-named rows were matched to the filer’s own name.

Counting. Workers as listed. Year and month use the employer’s notice date (Washington: the date received, which matches). Rows repeated exactly are dropped. Job titles come from a text layer (September 2026) and on-device OCR of a scanned file (July 2026), with counts checked against each letter’s total. Two OCR rows that joined adjacent cells were split by hand. Job family groupings are ours. FY2027 runs only to October 29, 2026.

Limits. WARN covers site-level cuts above a size threshold: in Washington 50 or more workers at a site, in California 50 or more at an employer with at least 75, and in New York 25 or more. Layoffs abroad, smaller cuts and voluntary exits do not appear. A notice is a plan, and some separations change. Press-reported figures are labelled and are not Microsoft’s own unless stated. We found no notices or filing figures for fiscal 2018, 2019, 2021 or 2022; reported cuts below notice thresholds in those years would not show up here.

Not advice. An analysis of public filings, not employment, legal or investment advice.

Cite as:The Uptime Report. "Microsoft Layoff History Timeline: Notices in 8 of 13 Years, and a July Filing in 3 of the Last 4." November 2026. https://theuptimereport.com/microsoft-layoff-history/

References

  1. Washington Employment Security Department, WARN layoff and closure database and notice PDFs. Accessed November 2026.
  2. California Employment Development Department, WARN reports, fiscal 2014-15 to current. Accessed November 2026.
  3. Maryland Department of Labor, WARN log and annual tables. Accessed November 2026.
  4. Texas Open Data Portal, WARN notices. Accessed November 2026.
  5. New York State Department of Labor, WARN dashboard. Accessed November 2026.
  6. Microsoft Corporation, Forms 10-K, fiscal 2014 to 2026, SEC EDGAR. Accessed November 2026.
  7. Microsoft, Form 8-K Exhibit 99.2, Ballmer email, January 22, 2009. Accessed November 2026.
  8. Microsoft, Form 8-K Item 2.05, July 17, 2014. Accessed November 2026.
  9. Microsoft, Form 8-K Exhibit 99.1, July 8, 2015. Accessed November 2026.
  10. Microsoft, Form 8-K Exhibit 99.1, May 25, 2016. Accessed November 2026.
  11. Microsoft, Form 8-K Exhibit 99.1, Nadella email, January 18, 2023. Accessed November 2026.
  12. Microsoft, earnings release, July 29, 2026. Accessed November 2026.
  13. Amy Coleman, “The latest in our company transformation”, Official Microsoft Blog, July 6, 2026. Accessed November 2026.
  14. “Resetting XBOX”, Xbox Wire, July 6, 2026. Accessed November 2026.
  15. Microsoft FY26 Q3 earnings call. Accessed November 2026.
  16. Microsoft FY26 Q4 earnings call. Accessed November 2026.
  17. Microsoft FY27 Q1 earnings call. Accessed November 2026.
  18. CNBC, May 13, 2025 (press, with spokesperson statement). Accessed November 2026.
  19. CNBC, July 2, 2025 (press, unconfirmed number). Accessed November 2026.
  20. CNBC, October 26, 2026 (press, memo and unnamed source). Accessed November 2026.
  21. Fortune, September 12, 2024 (press). Accessed November 2026.
  22. WARNTracker, Microsoft page (used only to find unverified leads). Accessed November 2026.

Research library

More original data reports from The Uptime Report. Every report includes its methodology and a free CSV download. Browse all research

Threats and breaches

Infrastructure and uptime

Regulation and disclosure

Workforce and pay

MSP market and spending

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *