TL;DR
I agree with JD Vance and the White House that immigration programs shouldn’t be used to displace qualified American workers.
Microsoft’s H-1B filing statistics challenge a simple comparison with layoffs. They don’t establish whether particular jobs were eliminated and later filled with comparable work.
The larger question for Microsoft’s leaders is what their workforce decisions achieved, including the expertise lost through layoffs and office mandates.
On October 8, Vice President JD Vance accused Microsoft of laying off American workers while sponsoring foreign workers through immigration programs. The administration announced it was suspending Microsoft from PERM, the federal labor-certification process used for certain employment-based green cards, amid an ongoing investigation.
I agree with Vance and the White House on the concern that matters. Companies shouldn’t be allowed to lay off qualified American workers and use immigration programs to replace them with cheaper, more dependent labor. If that happened at Microsoft, it deserves a serious investigation and appropriate consequences.
My concern isn’t with people working here on visas. Many are skilled employees whose immigration status depends heavily on an employer. They didn’t make Microsoft’s hiring or layoff decisions. Those decisions belong to its leadership.
Microsoft responded that about 80% of its roughly 6,000 H-1B filings last fiscal year involved existing employees. It said the remaining filings concerned new employees already legally in the United States, a number equivalent to about 1% of its U.S. workforce. Microsoft also said it pays H-1B workers comparably to employees doing similar work.
Fine. Those details matter. But they don’t answer the question I’m interested in.
Did Microsoft eliminate jobs held by qualified American workers and then hire others to perform substantially the same work?
Microsoft’s numbers don’t answer that question
Let’s separate the numbers first. An H-1B petition can involve an existing employee. A PERM labor certification concerns a different process: an employer’s sponsorship of a worker for permanent residency. Neither figure, by itself, tells us which jobs were eliminated or who took over the work.
That distinction matters because a misleading comparison makes a legitimate concern easier to dismiss. But Microsoft’s response stops short of the employment records needed to examine the allegation.
A new Microsoft hire who already lives in the United States is still a new Microsoft hire. Their location tells us nothing about whether the job resembles one the company recently eliminated. And saying that two employees doing comparable work earn comparable wages doesn’t establish whether a qualified U.S. worker was available or considered for a particular opening.
I’d want investigators to match the positions Microsoft eliminated against positions it later filled. Not just job titles, which companies can change. The actual duties, location, timing, required skills, recruiting records and compensation matter. So does whether the underlying work continued on another team.
The rules also need to be applied to the right program. For a PERM labor certification, the Department of Labor generally requires an employer to show that there aren’t sufficient qualified and available U.S. workers for the position and that hiring the foreign worker won’t adversely affect comparable U.S. workers’ wages and conditions. An H-1B petition isn’t the same application, and Microsoft’s H-1B percentages don’t establish compliance with every PERM requirement.
We don’t know what nonpublic evidence the administration has. The announced suspension and investigation aren’t a finding that Microsoft broke the law. They’re also not something Microsoft’s short statement can resolve on its own.
The records could clear Microsoft. They could also substantiate the allegation. Preserve the original hiring, layoff and immigration records and let investigators test them. If improper displacement is established, the people who made or approved those decisions should be held accountable.
If the jobs disappeared, why didn’t the work?
Some layoffs are necessary. Demand changes, products fail and companies can’t keep every role indefinitely. What bothers me is when executives point to a smaller payroll as though that alone proves they made the right decision.
Consider a company that eliminates a team responsible for keeping critical systems running. The salaries disappear from the budget, but the systems still need maintaining. Someone else inherits the alerts, the on-call shifts and the problems those employees used to prevent.
The company cut the people. Did it actually eliminate the work?
That’s a hypothetical, not a claim about a particular Microsoft team. It’s also something leadership can measure. Which responsibilities were transferred? Did customers wait longer? Did the remaining employees take on more risk? Was the expertise later replaced at a higher cost?
I’ve written about the operational cost of losing experienced people in The Security Team You Cut Doesn’t Come Back on Incident Day. The point applies beyond security. A cut can look successful for months before the cost becomes visible.
I would expect Microsoft’s board to examine that cost, not just the immediate savings. Otherwise, we can’t tell whether a layoff improved the business or simply moved the work and its risks onto fewer people.
Return to office: What happens when experienced people leave?
There’s another Microsoft decision that deserves the same scrutiny.
In September 2025, Microsoft announced that employees living within 50 miles of an office in the Puget Sound area would generally be expected on site three days a week by the end of February 2026. Exceptions were possible, and business groups could set different expectations. The company said the change was about collaboration and results, not reducing headcount.
That may be the goal. I’d still want to see who left and whether the collaboration improved.
Research on earlier return-to-office mandates at Microsoft, Apple and SpaceX found that longer-tenured and senior employees were more likely to leave after those policies. A separate study of more than three million technology and finance workers found higher turnover following office mandates, particularly among senior and skilled employees, along with longer times to fill vacancies.
Neither study establishes why Microsoft adopted its September 2025 policy or what happened after that particular rollout. In-person work can help some teams. But the studies give executives a real risk to measure, especially after major layoffs: experienced employees may leave voluntarily, taking knowledge the company never intended to lose.
I’d want Microsoft to report retention by tenure and role, the cost of replacing departing employees and evidence that teams are actually working better together. Badge swipes tell you who entered a building. They don’t tell you whether the work improved.
If the policy delivers better results, show them. If it doesn’t, change it.
Following the crowd isn’t leadership
There’s a broader management problem here. When a large technology company announces layoffs, it’s easy for other executives to point to the news as proof that their own cuts make sense.
Maybe their business really does need to shrink. But somebody else’s decision isn’t the analysis. Leaders still need to show what work disappeared, what alternatives they tried and why the reduction was the right choice for their company.
Other approaches exist. In Fortune’s May 2026 reporting, Costco CEO Ron Vachris said the company had moved employees into other responsibilities as technology changed their tasks, rather than displacing them. He also explained that Costco’s business was growing faster than those changes eliminated work. That distinction matters. A growing retailer and a software company facing different pressures aren’t directly comparable.
Still, it demonstrates that executives have more than one choice. They can retrain people, move them to work that’s growing or redesign a job before eliminating it. Sometimes those options won’t be enough.
I’d respect a leadership team that could show why it rejected them. If your justification for layoffs is that another big company did it, you haven’t made your case.
Show us what happened
Microsoft has supplied a specific explanation of its H-1B filing totals. The White House has made a serious allegation and announced an investigation. Neither a press conference nor a corporate statement supplies the job-by-job evidence needed to settle the dispute.
So I’d like Microsoft’s leadership to answer a more useful set of questions. Which jobs actually disappeared? Which duties remained? Were comparable positions filled afterward, and how were qualified U.S. workers considered? What did the company save after accounting for the expertise it lost?
Those are fair questions for any large employer.
If the records clear Microsoft, the findings should say so. If they establish improper displacement, the response should reach the people responsible for it. Either way, I’d rather see the evidence than another round of carefully chosen statistics.
Resources
JD Vance’s October 8, 2026 press conference, transcript via Roll Call
University of Chicago Becker Friedman Institute, Return to Office and the Tenure Distribution
Ding et al., Return to Office Mandates, Brain Drain and Gender Difference
Fortune, Ron Vachris on Costco, technology and employment, May 28, 2026