Nous Research is embedding its open-source Hermes agent inside Teams, the Microsoft Store and Azure, with skills that teammates can share and improve.
- Nous Research brings Hermes Agent to Microsoft Teams, the Microsoft Store, and Azure Container Apps sandboxes.
- Collective Wisdom turns individual workflows into reviewable skills shared across the whole team.
- Hermes Enterprise can run entirely inside a customer's own Azure tenant for data residency.
- Hermes processes nearly 2 trillion tokens daily, ranked top open agent on OpenRouter.
- Backed by Microsoft's M12 venture fund; Nous recently raised $90M at a $1.5B valuation.
- Architecture details presented at Microsoft Ignite session BRK448 on secure agent sandboxes.
Nous Research is bringing its open-source Hermes Agent to Microsoft Teams, Windows, and Azure. The company announced its Microsoft partnership alongside Hermes Enterprise, which customers can deploy inside their own Azure tenant. An agent in this context can plan multistep work, call connected tools, and execute code on a user’s behalf.
Microsoft’s venture fund, M12, has invested in Nous, so the companies already have a financial relationship. The new integration gives Hermes three entry points into Microsoft’s business software:
- Hermes Desktop for Windows: A desktop client distributed through the Microsoft Store.
- Microsoft Teams: A chat interface where employees can delegate financial analysis, document drafting, inbox triage, and other work, then review the output in the same thread.
- Azure Container Apps Sandboxes: Isolated microVMs that run agent-generated code, start in under a second, according to Nous, and release compute capacity when idle.
Workflows become reviewable skills #
Hermes’s Collective Wisdom feature converts successful recurring workflows into reusable skills. Each skill combines written instructions with executable code, allowing stable steps to run consistently while reducing repeated model inference.
Employees can ask Hermes to identify useful personal skills, submit them for review, and publish approved versions to a team. Colleagues can then reuse the established workflow instead of reconstructing it for each task. Nous says these skills remain within the organization and are excluded from vendor model training.
Tenant control for regulated workloads #
Nous plans to offer two commercial versions of Hermes:
| Product | Hosting | Primary use |
|---|---|---|
| Hermes Business | Hosted by Nous | A managed software-as-a-service deployment |
| Hermes Enterprise | Deployed in the customer’s Azure tenant | Workloads requiring tighter control over data, identity, and infrastructure |
Hermes Enterprise runs as Azure AI Foundry hosted agents within the customer’s tenant. That deployment model is designed to keep sensitive workloads inside the customer’s Azure boundary, which can simplify security reviews for banks, healthcare providers, government agencies, and other regulated organizations.
The Teams architecture uses familiar Microsoft services and development patterns:
- Identity: Microsoft Entra ID authenticates users and services.
- Microsoft 365 data: Microsoft Graph can retrieve resources such as meeting transcripts.
- Action approval: Adaptive Cards present commands for user review before execution.
- Keyless authentication: The
DefaultAzureCredentialchain supports service principals, managed identities, and Azure CLI credentials. - Bot registration: The
@microsoft/teams.clitooling automates registration steps that would otherwise require manual Azure portal configuration.
Funding turns into distribution #
Nous Research raised a $90 million Series B at a reported $1.5 billion valuation. Robot Ventures led the round, with reported participation from Nvidia, Microsoft’s M12, Samsung, Union Square Ventures, and other investors. Nous’s fundraising materials identified Teams and Slack integrations as routes into enterprise accounts, and the Microsoft release delivers part of that plan.
Nous says Hermes ranks first among public open agents on OpenRouter and processes nearly 2 trillion tokens per day. OpenRouter provides a common API and routing layer for accessing AI models. The reported volume gives Nous evidence of substantial developer usage, although enterprise buyers will also evaluate reliability, governance, support, and security controls.
The build-versus-buy calculation #
- Bot setup requires less manual configuration. The Teams CLI automates bot registration, reducing the number of portal steps needed to establish the integration. Tenant permissions, identity policies, and deployment controls still require configuration.
- Generated code runs in isolated environments. Ephemeral microVMs narrow the blast radius of compromised code. Secure deployments still need prompt-injection defenses, restricted network egress, scoped credentials, and audit logging.
- Skills can be inspected and reviewed. A skill’s instructions and code can pass through a review process similar to a pull request, with versioning and approval controls applied before publication.
- The core agent framework remains open. Its MIT license allows teams to inspect the agent loop, modify the implementation, and connect their preferred models. Microsoft distribution and Nous-hosted services may carry separate commercial terms.
- Enterprise data can remain tenant-bound. Self-hosting gives security teams greater control over identity, network policy, logs, and data handling than a vendor-hosted agent typically provides.
Microsoft expands its agent portfolio #
Microsoft will distribute Hermes while continuing to sell its own Copilot products. The overlap gives customers another agent option within Teams and Azure. It also benefits Microsoft when organizations choose Azure infrastructure without standardizing on Copilot.
For Nous, placement in the Microsoft Store and Teams app catalog reduces discovery and deployment friction. The partnership also puts Hermes in front of organizations that already use Entra ID, Microsoft Graph, Teams, and Azure procurement agreements.
Security details to verify #
- Data flow: Confirm where prompts, tool outputs, model inference, telemetry, and logs are processed for each deployment option.
- Graph permissions: Review the Microsoft Graph scopes requested by Hermes and apply least-privilege access.
- Sandbox controls: Assess outbound network access, secret handling, image provenance, patching, retention, and forensic logging.
- Skill governance: Define ownership, review, versioning, rollback, and deletion procedures for shared skills.
- Commercial coverage: Verify pricing, support response times, uptime commitments, data-processing terms, and relevant compliance attestations.
Nous CTO Jeffrey Quesnelle is scheduled to present the sandbox architecture at Microsoft Ignite in session BRK448, “Run secure agent loops in production with isolated sandboxes at scale.” The session focuses on production isolation, scaling, and agent-loop execution.
The announcement leaves pricing, service-level commitments, compliance certifications, and detailed rollout dates unspecified. Those terms will determine whether Hermes Enterprise can replace a custom internal agent stack or serve as another component within one.