When employees organize a workplace demonstration around a political or social cause, employers often face the same threshold question: does it matter that the protest touches, even loosely, on some workplace issue? A newly released National Labor Relations Board (“NLRB”) Advice Memorandum says “no”, at least on these particular facts. The Division of Advice concluded Microsoft lawfully fired two employees for organizing an unauthorized, non-workplace protest over the company’s ties to Israel because the protest was not aimed at improving employees’ own working conditions. But the reasoning is narrower than employers may assume, and it arrives while the Board’s own precedent on mixed-motive protests is under active challenge.
Background
Microsoft terminated two employees who organized an unauthorized on-campus demonstration at the company’s Redmond, Washington headquarters after they disregarded repeated instructions from company security to move the event off corporate property.
The demonstration did not arise in a vacuum. Months earlier, in May 2024, the advocacy group “No Tech for Apartheid” and a coalition of Microsoft employees launched a petition demanding, among other things, that Microsoft terminate its Azure cloud-computing contracts with the Israeli government and take steps to protect pro-Palestinian speech and fundraising on internal company platforms. Notably, Microsoft took no action against the employees over that petition, demonstrating a measured approach to employee advocacy.
The later event—timed to coincide with an international day of action—was billed as a walkout, vigil, speaker series, and fundraiser opposing the tech industry’s support for what organizers termed Israel’s actions in Gaza. The invitation linked to the earlier campaign’s materials, which in turn linked back to the May petition. But the invitation did not otherwise identify workplace concerns as an objective. The event was also publicized to non-employees on social media.
Microsoft security informed the organizers that the event could not proceed on campus because it was open to non-employees, was not authorized by the company, and was sponsored by an outside organization. Security repeatedly asked the organizers to relocate to nearby public property—offering a reasonable alternative rather than shutting down the activity entirely. When the organizers proceeded anyway, Microsoft terminated them for violating company policy and disregarding security directives.
The Division of Advice’s Analysis
The NLRB’s Division of Advice (the “Division”) concluded the terminations did not violate Section 8(a)(1) of the National Labor Relations Act (the “Act”) because the protest was not activity for employees’ “mutual aid or protection”—the threshold requirement for Section 7 protection.
The touchstone for that inquiry, rooted in the Supreme Court’s decision in Eastex, Inc. v. NLRB, 437 U.S. 556 (1978), is whether employees are seeking to improve their own terms and conditions of employment—or otherwise improve their lot as employees. The Division acknowledged that Board precedent, including Home Depot, USA, Inc., 373 NLRB No. 25 (2024), allows concerted activity to remain protected even when other, non-workplace objectives predominate—so long as improving working conditions is at least an objective of the activity.
Here, the Division found the demonstration’s objectives did not satisfy that standard. The protest’s stated objectives were to pressure Microsoft to cut ties with the Israeli government, raise awareness of conditions in Gaza, and raise funds for humanitarian relief. The invitation’s indirect link to the months-old petition—which itself contained only one demand tethered to a workplace concern (protecting employee speech on internal platforms)—was not enough to establish that improving employees’ lot was an objective of the May 2024 protest. As the Division put it, employees cannot extend Section 7’s protections by “wrapping an unprotected goal in a protected one.” Ampersand Publ’g, LLC v. NLRB, 702 F.3d 51, 58 (D.C. Cir. 2012).
The Division also rejected the argument that the protest qualified for protection because Microsoft’s relationship with Israel could affect the company’s public perception and financial performance—and therefore indirectly affect employee compensation and benefits. That chain of reasoning, the Division found, was too attenuated. This is consistent with precedent holding that efforts to influence a company’s overall business direction fall outside the mutual-aid-or-protection clause even where those efforts might have some ancillary financial effect. Critically, the Division found no evidence that Microsoft’s stated reasons for the terminations—the policy violation and disregard of security directives—were pretextual, reinforcing that the company acted on legitimate, consistently applied business grounds.
A Word of Caution: Home Depot Is Not Settled Law
Employers should not read this memo as a wholesale retreat from Home Depot. The Division distinguished Microsoft’s facts from Home Depot rather than rejecting its framework. Accordingly, the “an objective” standard—i.e., that improving working conditions must be an objective of the activity—remains the operative test. At least for now.
More importantly, the memo itself flags that this area of law is unsettled. General Counsel Crystal Carey noted her own disagreement with the Board’s decision in Home Depot and stated she “will urge the Board to overturn it in an appropriate case.” Employers should treat the current framework as provisional and watch closely for a case that squarely tests—and potentially narrows or eliminates—the Home Depot “logical outgrowth” and “an objective” analysis.
Practical Takeaways for Employers
- Enforce facility and event policies neutrally and consistently. Microsoft’s handling of this situation is instructive: its relocation demand rested on neutral criteria—outside sponsorship, no authorization, publicity to non-employees—not the protest’s message. Apply access and event-approval rules the same way regardless of subject matter.
- Consider giving employees a real chance to comply. Microsoft’s approach here was measured: it asked the organizers more than once to relocate before taking action, and disciplined them for the rule violation and refusal to comply—not for the content of their message.
- A thin workplace hook may not be enough. Before assuming a demonstration is protected simply because it references a prior employee complaint, examine whether the demonstration itself identifies a clear workplace objective—or merely borrows momentum from an earlier, arguably protected campaign. An indirect reference to past workplace advocacy will not necessarily convert a political protest into protected concerted activity.
- Document the real reason for discipline. The absence of any showing of pretext was central to the outcome, and Microsoft’s contemporaneous documentation of the policy violation helped establish that its decision was made on legitimate grounds. Ensure that discipline decisions are documented contemporaneously and tied to specific, articulable policy violations—not to the content or viewpoint of the activity.
- Do not treat this as a green light. General Counsel Carey has signaled an intent to seek reversal of Home Depot. Employers should continue to evaluate employee protests and demonstrations carefully—and consult counsel before disciplining participants—rather than relying on this memo as a categorical safe harbor.
We will continue to monitor developments in this area, including any case in which the Board is asked to revisit Home Depot, and will provide updates as further guidance emerges.
The content of this article is intended to provide a general guide to the subject matter. Specialist advice should be sought about your specific circumstances.
[View Source]
