Microsoft offers voluntary exits to 60,000 staff, Copilot teams included

Microsoft is offering voluntary exit packages to roughly 60,000 employees — about 27% of its global workforce — including staff on the teams that build Copilot and its other AI products, as the company reallocates money toward AI infrastructure spending that will exceed $50 billion in the September quarter alone.

Chief People Officer Amy Coleman announced the Voluntary Exit Offer (VEO) in an internal memo on Monday, which Microsoft republished on its official blog. "This offer gives eligible employees who may be considering a future outside the company a new choice to make that transition now with support," Coleman wrote.

Who is eligible, and who is not?

The offer covers employees at level 70 and below in participating teams in the US, Canada, India and the UK. Reuters, citing a person familiar with the matter, reported that participating organizations include AI experiences, Copilot, Xbox, and Windows + Devices.

• Excluded: marketing, sales, commercial business and security teams, plus some data center staff.
• Employees have until early December to decide; those who accept leave at the end of the year.
• The memo describes the offer as time-limited, with financial support and career planning resources, but does not disclose package terms.

Coleman's memo did not specify the eligible headcount; the 60,000 figure comes from Reuters. In short, the offer touches AI product teams directly but spares revenue-facing and security functions.

What came before it?

The VEO builds on the Voluntary Retirement Program Microsoft introduced in April for long-serving US employees. CFO Amy Hood said that program would carry roughly $900 million in one-time costs; by July she said expenses came in lower than expected.

Unlike the retirement program, the exit offer is not tied to age or years of service and extends beyond the US. "The Voluntary Exit Offer is new for us. We'll learn from it," Coleman wrote in the blog post.

Is a smaller Microsoft deliberate?

Yes, by management's own statement. "We expect headcount will decrease year-over-year," Hood said on the April 29 earnings call, referring to fiscal 2027, which began July 1. She said Microsoft was changing how it operates "to increase our pace and agility."

Microsoft employed about 223,000 people full-time as of June 30, 2026, down from 228,000 a year earlier, according to its SEC annual report. Hood said on the July 29 call that total headcount had declined 2% year over year. The contraction runs alongside the spending surge: $41 billion in capital expenditures in the quarter ended June 30, guided above $50 billion for the September quarter.

What should CIOs watch on their accounts?

Coleman wrote that participation varies with each business's "priorities, customer commitments and workforce needs," and Microsoft has not said whether the 89,000 operations staff (support, consulting, data centers) or 43,000 sales and marketing employees are eligible.

Sanchit Vir Gogia, chief analyst at Greyhound Research, cautioned against treating Microsoft's internal AI use as proof that roles can be cut elsewhere. "Microsoft's internal AI use does not establish substitution of particular roles," he said. He advised enterprises to measure completed work at agreed quality across representative roles and difficult exceptions before changing staffing, and to keep experienced staff available throughout.

"Workforce savings earn credibility through the capability that remains," Gogia said. "The practical test is whether customer-critical capability remains available throughout the transition."

He recommended CIOs confirm the accountable account owner and a qualified backup, test the successor on an unresolved exception, and compare support cases against a recent baseline.

Is Microsoft adding customer-facing capacity too?

Yes. On the July earnings call, CEO Satya Nadella said Microsoft had launched Microsoft Frontier Co., embedding 6,000 industry and engineering experts with customers. Nadella also said on the April call that IT budgets would be reshaped by business outcomes and "reallocation from other line items on the income statement, like OpEx."

Gogia said delivery commitments still need granular checking: "Aggregate headcount does not identify the expertise required by an Azure migration or a Dynamics implementation." He advised verifying Azure dependencies by subscription and region, reconfirming Dynamics implementation specialists, and distinguishing previews from contractual milestones on product roadmaps. Microsoft did not immediately respond to a request for comment.

Buyers, not just employees, now have a December deadline to watch.