A small but highly visible standoff at Microsoft’s Redmond campus this week crystallized a wider crisis for the company: employees confronting management over allegations that Microsoft’s cloud and AI technologies have been used by the Israeli military to store and process mass surveillance data on Palestinians — and that those systems may have fed targeting processes used in the Gaza war. The protests, staged by employee-led groups that call themselves No Azure for Apartheid (and related coalitions), culminated in 18 arrests on Microsoft property and renewed pressure on the company to disclose what it knows, who used its systems and whether its policies were enforced.

A Flashpoint in Redmond

On two consecutive days, protesters — including current and former Microsoft employees — set up a small encampment at a central plaza on Microsoft’s East Campus, declared a symbolic “liberated zone,” and demanded the company sever ties with Israeli military entities. By Wednesday the demonstration escalated; police say protesters resisted orders to leave, blocked pedestrian ways and splashed red paint on the Microsoft sign. The Redmond Police Department arrested 18 people on charges that included trespass, malicious mischief, resisting arrest and obstruction. Microsoft described the actions as unlawful and said it will continue to uphold its human rights standards while addressing property damage and disruption.

The arrests mark the latest flashpoint in months of escalating internal activism. Earlier this year Microsoft disciplined or fired several employees who interrupted high-profile company events to protest contracts with Israel’s defense establishment. Internal groups have organized petitions, town-hall disruptions and public demonstrations seeking transparency, redress and policy changes. The protest rhetoric has hardened at times — including online calls that used terms invoking Palestinian resistance — which has exacerbated tensions inside the company over free expression, corporate security and public perception. The message from the protesters is clear: they believe Microsoft’s technology is enabling grave human rights abuses, and they are willing to risk their jobs and freedom to force the company’s hand.

The Guardian Investigation: Microsoft’s Deepening Military Ties

The protests did not emerge in a vacuum. Over the last twelve months investigative reporting has exposed a multilayered relationship between major U.S. cloud and AI providers and the Israeli Ministry of Defense. A Guardian-led investigation — based on leaked documents and interviews with sources from across Israel’s defense and intelligence establishment — revealed that the Israeli military’s reliance on Microsoft’s cloud technology and AI systems surged during the most intensive phase of its bombardment of Gaza. The files offer an inside view of how Microsoft deepened its relationship with Israel’s defense establishment after 7 October 2023, supplying the military with greater computing and storage services and striking at least $10m in deals to provide thousands of hours of technical support.

According to the leaked commercial records and Microsoft subsidiary files, Azure was used by multiple military intelligence units, including the elite surveillance division Unit 8200 and the secretive technology unit Unit 81. A system Israeli security forces use to manage the population registry and movement of Palestinians in the West Bank and Gaza, known as “Rolling Stone,” was maintained using Microsoft technology. Perhaps most critically, Microsoft’s suite of communications and messaging systems were used by Ofek, an air force unit responsible for managing large databases of potential targets — “target banks” — that feed lethal strikes. During the Gaza offensive, Microsoft engineers provided round-the-clock support to intelligence units, both remotely and on military bases. The defense ministry agreed to buy 19,000 hours of engineering support and consultancy services from Microsoft between October 2023 and June 2024.

The documents also reveal a staggering leap in AI consumption. The Israeli military’s average monthly consumption of Azure cloud storage in the first six months of the war was 60% higher than in the four months leading up to it. By March 2024, the military’s monthly consumption of Azure’s machine learning tools was 64 times higher than in September 2023. The IDF drew on AI-powered translation and speech-to-text conversion tools, and a significant portion of these AI services were used on “air-gapped” systems disconnected from the internet, suggesting highly sensitive applications. The military’s use of OpenAI’s GPT-4 engine — made accessible through Azure after OpenAI quietly deleted its restrictions against military use in early 2024 — also rose sharply. At one stage, OpenAI’s tools accounted for a quarter of the military’s machine learning consumption on Azure.

Microsoft declined to comment on the specifics of the Guardian investigation. Its public posture has been to stress its human rights commitments and terms of service, while insisting that it has seen no evidence that Azure or its AI tools were used to target or harm civilians. The company has pointed to an earlier internal review and — after the latest reporting — announced a second, external review to be conducted by law firm Covington & Burling with technical assistance from an independent consulting firm. Microsoft’s public statements emphasize that use of its services is governed by its Acceptable Use Policy and AI Code of Conduct.

Technical Underpinnings: How Cloud AI Feeds Surveillance

To understand the gravity of the allegations, one must grasp the technical capabilities at play. Commercial cloud platforms like Azure offer a suite of services that can be seamlessly integrated into intelligence workflows: managed storage, speech-to-text, translation, natural-language processing, and model hosting. A government customer can ingest raw signals intelligence into Azure data lakes, run transcription and entity extraction, cross-reference outputs with other datasets, and feed the results into decision-support systems — all using off-the-shelf tools. These capabilities are commercially available and widely used in legitimate contexts such as emergency response or humanitarian analysis. But in the wrong hands, they become instruments of mass surveillance.

However, cloud providers do not automatically have deep visibility into how their tools are used. Microsoft, like others, maintains service-level telemetry — API calls, compute consumption, billing records — but it does not capture the semantic content of customer data by default. Customers can also create “air-gapped” or dedicated networks that limit provider visibility entirely. Proving that a specific transcript stored on Azure was used to recommend a particular lethal strike requires access to both cloud logs and the customer’s internal operational systems, which are often classified. This technical opacity is at the heart of the accountability challenge.

Microsoft’s Response and the Limits of External Review

Microsoft’s announcement of an external review by Covington & Burling is a significant step, but its credibility hinges on scope and access. A law-firm-led review can examine contractual arrangements, policy enforcement, and internal compliance processes. It can interview employees and review service logs where available. But key forensic questions — such as whether specific audio files fed into targeting systems — require access to customer-side operational logs that may be locked behind national security barriers. The company itself has repeatedly highlighted its limited visibility into how customers use on-premises or air-gapped systems. Without extraordinary cooperation from Israeli authorities, the review may be unable to independently validate the most serious downstream operational claims made by intelligence insiders or media sources. Any review that fails to attempt forensic verification of data flows or relies exclusively on company management interviews will be treated skeptically by observers and employees alike.

The stakes for Microsoft are immense. Its Acceptable Use Policy and AI Code of Conduct prohibit uses that cause harm or violate human rights. If investigations substantiate that its services enabled mass civilian surveillance or were used in ways that contravene those policies, Microsoft could face contractual breaches, reputational damage, and regulatory scrutiny. Large-scale employee activism adds a new vector of corporate risk: protests at Redmond are not merely symbolic; they threaten operations, attract regulatory attention, and test executive credibility. For customers, investors, and policymakers, the perception that Microsoft’s tools contributed to humanitarian harm — even indirectly — erodes trust.

Beyond Microsoft, the controversy signals a broader reckoning for the tech industry. Commercial AI and cloud providers have become strategic infrastructure, blurring the line between civilian and military applications. As governments integrate public-cloud tooling into national security operations, new norms for responsible provisioning and oversight are urgently needed. Transparency regimes must be realistic about national security limits while compelling vetted external audits and redaction-limited disclosures. Independent technical audit capacity is in critically short supply; investing in such frameworks is a public good. Employee activism will likely accelerate corporate governance changes, as workers play a more prominent role in forcing transparency on ethically fraught contracts.

What a Credible Investigation Must Do

To rise above a public-relations exercise, the Covington review must go beyond high-level policy recitations. It should secure independent technical forensics that can examine logs, configuration snapshots, and data flows where legally permissible. It must interview current and former Microsoft employees with direct knowledge of relevant project work and procurement chains. It should obtain and analyze contracts, statements of work, and invoicing records related to Israel’s defense and intelligence units. And it must publish a public summary that differentiates verified facts, corroborated allegations, and unresolved claims, providing as much redacted supporting material as national security allows. Without these elements, the review will fail to quiet the uproar inside and outside the company.

Conclusion: Accountability at a Crossroads

The Redmond arrests and the revelations from leaked documents represent an inflection point for Microsoft and the broader cloud-AI industry. The company’s next steps — the depth and openness of the Covington & Burling review, the technical access it secures, and any policy or operational changes it enacts — will determine whether Microsoft manages this crisis through credible accountability or further erodes trust among employees, customers, and regulators. For now, the allegations deserve thorough, transparent investigation; the protests show employees are prepared to hold the company publicly accountable; and the industry must grapple with the fact that advanced cloud and AI services are no longer neutral utilities — they are instruments with profound ethical and geopolitical consequences. The coming weeks should reveal whether Microsoft can translate its stated principles on responsible AI and human rights into verifiable action and meaningful change.