Tech Workers Challenge Military Links in Big Tech
In These Times profiles tech workers challenging military and surveillance contracts at major AI/cloud companies, including organizer Hossam Nasr and the No Azure for Apartheid campaign at Microsoft. The piece is an advocacy feature, so claims about specific military use should stay attributed to the publication, worker groups, Microsoft statements, and independent reporting rather than treated as settled by LDS. For practitioners, the operational lesson is concrete: defense-linked AI and cloud work can create hiring, retention, compliance, and reputational risks even when the underlying service is general-purpose infrastructure. Microsoft has publicly said past reviews found no evidence of Azure or AI being used to target or harm people in Gaza, while later reviews limited some services after separate surveillance reporting.
The LDS takeaway is that military-linked AI and cloud contracts create operational risk beyond the model itself. Employee activism, human-rights reviews, customer-use opacity, and public protest can all affect delivery, hiring, and vendor due diligence for teams building or buying AI infrastructure.
What happened
In These Times published a Sarah Lazare feature on tech workers organizing against military and surveillance contracts at major technology companies. The article profiles Hossam Nasr, describes No Azure for Apartheid organizing around Microsoft, and points to protests connected to Google and other large vendors. Because the article is advocacy-driven, LDS should keep the strongest claims attributed rather than present every allegation as independently settled fact.
Policy context
Microsoft said in May 2025 that reviews found no evidence to date that its Azure and AI technologies had been used to target or harm people in Gaza. In September 2025, Microsoft later said it ceased and disabled a set of services to a unit within Israel's Ministry of Defense after a continuing review. Independent reporting from AP, The Guardian, GeekWire, and others documents the broader dispute, worker firings, and activist claims around cloud and AI services.
For practitioners
Procurement and platform teams should track high-risk end uses, contract restrictions, auditability, escalation paths, and employee-relations exposure before treating defense or surveillance customers as ordinary enterprise accounts. A general-purpose model or cloud service can still carry significant downstream risk when deployed into military workflows.
What to watch
Watch for stronger human-rights due diligence requirements, employee organizing around AI infrastructure, and more public vendor statements that narrow or suspend customer access after abuse investigations.
Key Points
- 1Worker activism over military-linked contracts can create retention, compliance, and delivery risk for AI infrastructure vendors.
- 2Claims about specific battlefield or surveillance use should remain attributed because company statements and investigations can differ.
- 3Procurement teams need end-use controls and escalation paths when general-purpose AI services support sensitive government customers.
Scoring Rationale
This is a solid policy and workforce-risk story for AI infrastructure teams, especially around defense and surveillance end uses. The score stays moderate because the trigger is an advocacy feature with disputed high-stakes claims, so the strongest allegations require attribution and context.
Sources
Public references used for this report.
Practice with real Ad Tech data
90 SQL & Python problems · 15 industry datasets
250 free problems · No credit card
See all Ad Tech problems
