AI tool comparison
Azure Foundry Hosted Agents vs Microsoft Harrier-OSS-v1
Which one should you ship with? Here is the side-by-side panel verdict, pricing read, reviewer split, and community vote comparison.
Developer Tools
Azure Foundry Hosted Agents
Per-session isolated agent sandboxes on Azure — scale to zero, any framework
50%
Panel ship
—
Community
Paid
Entry
Microsoft Azure's Foundry Agent Service now offers Hosted Agents in public preview — per-session isolated compute sandboxes purpose-built for running AI agents at scale. Each session gets its own container with a persistent filesystem, internet access (optional), and a Python environment pre-loaded with common agent dependencies. Sessions spin up in seconds and terminate — and stop billing — the moment the agent task completes. The design is framework-agnostic: it officially supports LangGraph, OpenAI Agents SDK, Claude Agent SDK, and Microsoft's own Agent Framework, with others planned. This removes one of the most awkward parts of deploying agents in production: figuring out where they actually run. The persistent filesystem per session means agents can read and write files across their task without external storage configuration. Pricing is $0.0994/vCPU-hour and $0.0118/GiB-hour — competitive with Lambda/Cloud Run for bursty workloads. The service is available in six Azure regions at launch. For enterprises already invested in Azure, this is a compelling "we just figured out the infra" moment. Independent developers can also use it without an enterprise agreement.
Developer Tools
Microsoft Harrier-OSS-v1
SOTA multilingual embeddings in 3 sizes — quietly MIT-licensed with zero fanfare
75%
Panel ship
—
Community
Free
Entry
Microsoft Harrier-OSS-v1 is a family of multilingual text embedding models released with almost no publicity on March 30, 2026 — no blog post, no press release, just a HuggingFace upload. Available in three sizes (270M, 0.6B, and 27B parameters), the models achieve state-of-the-art performance on Multilingual MTEB v2 across 94 languages, 32k token context windows, and use a decoder-only Transformer architecture rather than the traditional BERT-style encoder design. The 27B variant scores 74.3 on MTEB v2, outperforming all previous open-source multilingual embedding models. All three sizes are MIT-licensed — fully open, including commercial use. The decoder-only architecture mirrors modern LLMs rather than the encoder-only models (like E5, BGE, and mE5) that have dominated embedding benchmarks for years. For developers building RAG systems, semantic search, multilingual document clustering, or cross-lingual retrieval, Harrier represents a significant quality jump. The 270M and 0.6B variants are practical for production deployment; the 27B is for maximum quality where compute isn't a constraint.
Reviewer scorecard
“Framework-agnostic hosted sandboxes with scale-to-zero is exactly what I need for deploying agents without maintaining my own Kubernetes cluster. The per-session isolation eliminates a whole class of security concerns I was handling manually. The Claude Agent SDK support means I don't have to choose between Azure and my preferred model.”
“MIT license + SOTA multilingual MTEB scores + 270M/0.6B/27B size options = drop this into your RAG stack immediately. The decoder-only architecture is architecturally interesting but what matters is the benchmark numbers, and they're the best in class. Drop-in replacement for mE5-large or multilingual-e5-large.”
“Public preview means production instability risk and pricing could change significantly at GA. The cold start time for agent sessions needs to be benchmarked against real workloads before committing. And six regions is thin coverage for global deployments — wait for broader availability.”
“Benchmark scores don't always translate to real-world retrieval quality — domain-specific datasets often favor fine-tuned models over general SOTA. The lack of any documentation, paper, or announcement is a yellow flag; it's unclear what training data was used, which affects reproducibility and potential data contamination concerns.”
“The battle for agent infrastructure is the next cloud wars — and Microsoft just answered Google Cloud's agent platform launch with their own. Framework-agnostic compute that works with any model provider is a smart commoditization play: own the infrastructure layer, let the model battle play out above it.”
“The shift to decoder-only embeddings mirrors the broader architectural convergence in AI — the same foundational architecture working for both generation and retrieval. As RAG systems go multilingual and handle longer documents, models like Harrier with 32k context and 94-language coverage become load-bearing infrastructure.”
“This is squarely developer infrastructure — not directly relevant to creative workflows unless your studio runs its own agents. Worth watching for the ecosystem tools that get built on top of it.”
“For anyone building multilingual content search or recommendation systems — this is the embedding model to use. Being able to search across 94 languages with a single model rather than language-specific pipelines dramatically simplifies cross-cultural content projects.”
Weekly AI Tool Verdicts
Get the next comparison in your inbox
New AI tools ship daily. We compare them before you waste an afternoon.