Microsoft’s chief people officer Amy Coleman has set a new hybrid-work baseline: starting in late February 2026, Puget Sound employees living within a 50-mile radius of a company office will be required to work on-site three days a week. The announcement, shared via an internal blog and public communications, frames the change as essential for accelerating collaboration on complex AI projects rather than a headcount reduction. The policy will phase in across other U.S. sites and then internationally throughout 2026.

The Policy in Detail

The new rule establishes three days a week as the minimum—not a ceiling. Teams that require more frequent overlap can mandate four or five days, though some customer-facing roles remain exempt. The rollout begins with the Puget Sound region (Redmond and nearby campuses) by the end of February 2026, then expands to other U.S. offices before reaching international locations. A 50-mile radius from a Microsoft worksite defines which employees must comply, though managers have discretion to grant exceptions on a case-by-case basis, according to Coleman’s blog post.

Who’s Affected and What It Means for You

For Microsoft Employees in the Puget Sound Area

If you’re a Microsoft employee living within 50 miles of Redmond or another Puget Sound campus, you’ll need to be in the office three days each week starting in early 2026. That means planning your commute, potentially adjusting childcare, and coordinating with your team on which days make the most sense for collaborative work. If you have constraints that make commuting impractical—such as caregiving responsibilities or a long commute within the radius—now is the time to start discussing exceptions with your manager. Microsoft says managers will adjudicate exceptions, but the criteria and consistency remain unclear.

For Microsoft Employees Outside Puget Sound

The policy will eventually apply to you, but the timeline is longer. U.S. offices beyond Puget Sound will adopt the three-day requirement later, and international offices will follow after that. This phased approach gives you months, perhaps over a year, to prepare. However, if you currently work fully remote and live more than 50 miles from any Microsoft office, the policy may not affect you immediately, but you should monitor how the company defines your primary work location.

For Tech Workers at Other Companies

Microsoft’s move will pressure other tech firms to set clearer hybrid expectations. If your employer has been vague about remote work, this could accelerate a shift toward a three-day baseline. On the flip side, companies that remain fully remote may use that flexibility as a recruiting edge, potentially drawing talent away from companies with stricter mandates. Watch how your own organization responds—especially if it competes with Microsoft for AI talent.

For IT and Business Leaders

This mandate signals where the broader industry is heading on hybrid work. As the company behind Teams and Microsoft 365, Microsoft’s policy carries weight. If you’re designing your own return-to-office strategy, consider that three days a week may become the standard expectation for commutable employees. You may need to rethink office layouts (more collaboration spaces, fewer assigned desks) and invest in tools that bridge in-person and remote workers effectively. Also, examine your exception process to avoid perceptions of unfairness.

The Road to a Mandate: Why Microsoft Is Tightening In-Office Time

Microsoft has steadily shifted its tone on remote work since 2020. Initially, the company embraced a flexible model, allowing many employees to work remotely up to 50% of the time. But through 2023 and 2024, executives increasingly emphasized the value of in-person collaboration, particularly for onboarding new hires and tackling complex cross-team projects. In early 2025, Microsoft conducted multiple rounds of layoffs, with reputable outlets reporting cuts in the thousands. Some employees saw these layoffs as a precursor to a stricter in-office policy. Amy Coleman’s latest announcement makes the expectation explicit: in the AI era, where rapid iteration and cross-disciplinary teamwork are critical, physical presence is now a baseline requirement for those within commuting distance.

The company’s public rationale centers on collaboration velocity—whiteboard sessions, informal hallway conversations, and faster decision-making. While some of these benefits are hard to measure, Microsoft argues that integrating work across Windows, Azure, Microsoft 365, and Copilot demands high-bandwidth interaction that virtual meetings can’t fully replicate.

The Enforcement Question

The most consequential unknown is enforcement. Past return-to-office waves have been enforced through explicit tie-ins to performance reviews, promotion eligibility, project assignment, and informal cultural pressure. Microsoft’s initial communications emphasize manager discretion and an exceptions process—but will office attendance become an explicit performance metric? Will exception adjudication be auditable and consistent across organizations and geographies? Early coverage and internal analysis flag these exact risks: managers often default to visible inputs (badge swipes, calendar presence) when judgments are ambiguous, and that bias can conflate attendance with impact. Any systematic linkage of office presence to career progression will materially alter employee incentives. Because enforcement will likely vary by team, the policy will feel stricter in pockets where delivery timelines and cross-disciplinary dependencies are highest. Expect uneven implementation: some teams may quietly mandate four or five days while others remain at the three-day floor. That heterogeneity raises fairness and retention issues that Microsoft’s HR apparatus will need to manage carefully.

What You Should Do Now

If You’re a Microsoft Employee

  • Check your home address against the 50-mile radius of your assigned office. If you’re near the boundary, confirm with HR how distance is calculated.
  • Discuss with your manager which days you’ll be in the office and what types of activities require co-location. Document these plans.
  • If you have a legitimate need for an exception, start the request process early. Gather documentation and articulate how you’ll still meet collaboration goals.
  • Prepare for potential changes in performance evaluation. While Microsoft hasn’t tied attendance to reviews officially, be mindful that visible presence may influence perceptions.

If You’re a Manager at Microsoft

  • Define clear, measurable goals for in-office days: what specific outcomes do you expect? Communicate these to your team in writing.
  • Create fair and transparent exception criteria. Avoid ad-hoc decisions that could lead to perceptions of favoritism.
  • Track whether mandatory office days actually improve key metrics (delivery speed, bug rates, team morale) and be ready to adjust if they don’t.

If You’re a Microsoft Partner or Customer

  • Expect that the people you work with at Microsoft may shift their availability patterns. In-person meetings may become more common if you’re local, while remote collaboration will still be supported for those outside the radius.
  • If your contracts involve on-site support, clarify with your Microsoft contacts how the new policy might affect staffing.

What to Watch Next

The success or failure of this mandate hinges on three factors: enforcement consistency, measured productivity gains, and employee retention. Keep an eye on whether Microsoft publishes any data linking in-office time to project outcomes—or if the policy becomes a matter of cultural pressure without hard evidence. Also watch how international offices adapt, as labor laws in Europe could force different implementations. Finally, note how competitors react: if other big tech firms follow suit, the three-day hybrid model could become the industry norm; if they don’t, Microsoft risks losing top talent to more flexible employers.