ClawHosters
by Daniel Samer
3 min read
On May 1, 2026, Microsoft made Agent 365 generally available. And OpenClaw is the only agent it currently detects and blocks. Not one of many. The only one.
The official Microsoft Learn documentation confirms that IT admins can now apply an Intune policy called "A365 - Block OpenClaw" to managed Windows devices. Propagation takes between 15 minutes and 8 hours depending on organizational configuration.
Why OpenClaw Specifically
The numbers tell the story. SecurityScorecard identified over 135,000 internet-exposed OpenClaw instances back in February 2026, many running from corporate IP ranges. Token Security found that 22% of monitored organizations have employees running OpenClaw without IT approval.
Employees were installing OpenClaw on company laptops with single-line commands. No approval process, no SOC visibility. Microsoft's Defender team now formally classifies OpenClaw as "untrusted code execution with persistent credentials."
That is a governance problem. And Microsoft built a governance tool for it.
The Part Nobody Is Talking About
Here is what makes this genuinely interesting. On the same day Agent 365 went GA with OpenClaw blocking, Microsoft's internal pilot "ClawPilot" (codenamed Project Lobster) jumped to over 3,000 daily users. That is 3,000 Microsoft employees running OpenClaw-based agents with full Entra ID identities, mailboxes, and Teams presence.
So Microsoft is not against OpenClaw. They are against unmanaged OpenClaw.
In June 2026, Defender Context Mapping enters public preview. This will map each detected agent to its host devices, MCP servers, identities, and cloud resources. The enforcement is getting more granular, not less.
What This Means for ClawHosters Users
Agent 365 targets local Windows device installations. That is the threat model: an OpenClaw instance running on a managed corporate laptop, binding to default port 0.0.0.0:18789, with credentials stored locally.
ClawHosters instances run on isolated cloud VPS infrastructure, not employee workstations. Your instance does not appear on corporate device scans. It does not bind to a managed Windows endpoint. The Intune policy has nothing to detect.
If your company runs ClawHosters, the architecture already satisfies what enterprise governance policies are trying to enforce. Dedicated infrastructure, controlled network access, no local credential exposure. That is exactly the difference between self-hosted and managed.
The enterprise crackdown is not about OpenClaw as technology. It is about OpenClaw as shadow IT. Managed hosting was always the answer to that problem. Microsoft just made the argument for us.
