# Nous Research — Cookbook: run Hermes Agent as a Microsoft Foundry autonomous agent

- Company: Nous Research (nousresearch.com)
- Announced: 2026-11-20T14:00:00+00:00
- Category: not stated
- Coverage: not counted
- Announcement: no
- Group: routine
- Source: https://nousresearch.com/hermes-on-microsoft-foundry-cookbook
- Record: https://forck.live/items/39296-cookbook-run-hermes-agent-as-a-microsoft-foundry-autonomous-agent
- Subject: Hermes models

Nous Research published a cookbook for deploying its open-source Hermes Agent into a customer's own Microsoft 365 tenant as a Foundry hosted agent. The guided installer builds Hermes in the customer's Azure subscription and submits it to an administrator for approval, after which employees create instances from Microsoft Teams. Each instance runs as its own Microsoft 365 account with email, OneDrive files and scheduled routines that run with nobody signed in. The repository holds the edge, gateway and sidecar components, while Hermes itself comes from Nous's published Docker image pinned by digest. Prerequisites include a tenant enrolled in the Frontier preview program, a Microsoft 365 Copilot or Microsoft Agent 365 licence, and a free agent seat from the 25 preview seats Frontier tenants receive. Nous Research says autonomous agents are in preview through Microsoft's Frontier program and the repository is a proof of concept, so it advises using a test or pilot tenant rather than production.

## Evidence

Verbatim from https://nousresearch.com/hermes-on-microsoft-foundry-cookbook:

> Deploy Nous Research's open-source Hermes Agent into your own Microsoft 365 tenant, create it from Teams and give it its first tasks.
> 
> TL;DR. You install Hermes in your own tenant from our open-source repository, in one of two ways:
> 
> Guided install (recommended). One installer builds Hermes in your Azure subscription and submits it to your administrator for approval. Follow Steps 1 to 7.
> 
> Advanced route. Deploy step by step with the advanced guide in the repository, build the upload ZIP with the repository's package script, and upload it in the Microsoft 365 admin center. See "Advanced route: build and upload the package yourself".
> 
> Both routes end the same way: an administrator approves Hermes in the Microsoft 365 admin center, and employees create it from Teams.
> 
> What you'll build
> 
> By the end of this recipe, your company has its own Hermes autonomous agent: a Foundry hosted agent with its own Microsoft 365 account. You'll create an instance from Microsoft Teams, chat with it, have it send email and work with files in its own OneDrive, and schedule a recurring task that runs with nobody signed in.
> 
> Status.

---

Record: https://forck.live/items/39296-cookbook-run-hermes-agent-as-a-microsoft-foundry-autonomous-agent
Catalogue: https://forck.live/llms.txt
Current issue: https://forck.live/feed.md
