Microsoft Requires 3 In-Office Days per Week for Near-Redmond Staff

(REDMOND, WASHINGTON) Microsoft will require many employees to return to the office at least three days per week starting in February 2026, beginning with those who live within 50 miles of the company’s Redmond headquarters. The company outlined the change in a memo dated September 10, 2025, from Chief People Officer Amy Coleman, with a firm window for affected staff to start meeting the three-day office minimum by the end of that month. The plan will roll out in phases to other U.S. locations and later to international offices. Employees can ask for exceptions, but they must submit requests by Friday, September 19, 2025.

Microsoft says internal data shows workers who spend at least three days a week together in person report higher “thriving scores,” which the company defines as feeling more engaged, energized, and effective. Leadership argues in-person time helps teams coach junior staff, share ideas quickly, and build trust that can fade with long-term remote work. While the company stresses the policy is not designed to push people out, it warns that choosing not to follow the attendance rules could affect performance reviews, promotions, and access to marquee projects.

Rollout Phases and Scope

• Phase 1 (first wave): Employees who live within 50 miles of Redmond HQ (Puget Sound area) must meet the three-day office requirement by the end of February 2026. Those employees received personalized emails outlining timelines and expectations.
• Phase 2: Other U.S. offices.
• Phase 3: International locations, with a full rollout anticipated by late 2026.

Some roles—such as account management, consulting, and field marketing—are generally exempt due to customer-facing responsibilities and travel or flexible schedules. Other exceptions may be possible where a role lacks local teammates or clients, or where commutes are especially complex, but approvals are not guaranteed and must be requested before the September deadline.

Policy Details and Timeline

• Who is first: Employees within 50 miles of Redmond HQ.
• Start date for Redmond area: February 2026 (three-day minimum in effect by the end of that month).
• Rollout plan: Puget Sound → other U.S. offices → international locations (by late 2026).
• Exemptions: Request by September 19, 2025; certain customer-facing roles generally exempt.
• Non-compliance: Policy not intended to reduce headcount, but attendance will be factored into performance evaluations, promotions, and project assignments.

“Thriving scores” are a key internal measure Microsoft cites to justify the shift: the company says these scores improve with more in-office time. Fully remote roles will remain but will be rare and based on specific business needs.

Context: Why Now?

The policy comes amid restructuring and layoffs at Microsoft. Since May 2025, the company has cut more than 15,000 roles across divisions including Xbox, LinkedIn, engineering, product management, and legal. Analysts view the return-to-office shift as part of broader culture tightening across large tech firms; peers like Google, Meta, and Amazon have likewise scaled back remote options or set minimum in-office days.

Microsoft’s leadership frames the move as a push for collaboration as it invests heavily in AI product development and builds new teams to support that work.

Employee Impact and Concerns

For employees who moved away from hubs during remote-friendly years, the new requirement could mean difficult choices:

• Longer commutes and higher travel costs
• Need to relocate closer to offices
• Childcare gaps and schedule conflicts for parents/caregivers
• Additional accommodation needs for workers with disabilities

According to analysis by VisaVerge.com, companies that set in-office minimums often see mixed reactions: some welcome the energy and faster promotion paths; others lament loss of flexibility and added commuting expense.

Practical Steps for Affected Employees

1. Confirm your status
   • If you live within 50 miles of Redmond, expect to be in the first wave.
   • Read your personalized email and discuss team expectations with your manager.

1. Consider an exception
   • If your role lacks local teammates or clients, or your commute poses unusual challenges, review the exception process.
   • Submit exception requests by September 19, 2025.
2. Map your logistics
   • Test your commute, check parking or transit options, and estimate added costs.
   • Decide whether relocation or hybrid arrangements could work.
3. Track updates
   • Microsoft says more details for other U.S. offices and international sites will follow—monitor official messages.

How to Prepare an Exception Request

• Document specifics: role responsibilities, client locations, and teammates’ locations.
• Gather commute evidence: time estimates, transit options, and cost analysis.
• If applicable, include health or family considerations and discuss supports with managers and HR early.

For official U.S. immigration information and services, employees can consult U.S. Citizenship and Immigration Services.

Management and Team Considerations

• Managers will need to set predictable in-office days for collaboration so that team members can plan accordingly.
• Attendance expectations are likely to be noted directly in goals and performance reviews.
• Uneven application of the rule across teams could harm morale; consistent standards and transparent exception reviews are critical.
• Office days should be structured—planned meetings, mentoring, and collaboration—otherwise in-person time may be wasted.

Microsoft’s internal data suggests new hires and early-career staff often learn faster with face time, especially in complex product groups where informal knowledge-sharing matters.

Potential Outcomes: Benefits vs. Risks

Benefits:
– Stronger team cohesion and mentorship
– Faster decision-making and cleaner handoffs
– Greater visibility for career growth

Risks:
– Added commuting costs and scheduling burdens
– Potential pressure on quieter team members to be physically present
– Employee churn if the policy is seen as inflexible or unevenly enforced

If implemented well, the policy could create steady collaboration rhythms: shared office days for brainstorming and planning, and remote days for deep work. If poorly implemented—uneven schedules, unclear exceptions, or poorly planned meetings—it could create friction and increase turnover risk.

Final Takeaways

• Microsoft is imposing a firm timeline and an exception path with a hard deadline; employees who want to remain largely remote have a narrow window to apply.
• Managers who want the policy to succeed should treat in-office days like a product feature: clear goals, coordinated schedules, and consistent follow-through.
• As the company moves toward February 2026, the message is firm but offers some flexibility; the company is betting that three days together each week will raise “thriving” across the board.