Microsoft Foundry
Hermes Agent's provider supports Microsoft Foundry (formerly Azure AI Foundry) and Azure OpenAI. A single Foundry resource can host models with two different wi
- Section
- Guides & Tutorials
- Source
- hermesbible.com/docs/guides/azure-foundry
Hermes Agent's provider supports Microsoft Foundry (formerly Azure AI Foundry) and Azure OpenAI. A single Foundry resource can host models with two different wi
Excerpt from the official Hermes Agent documentation, quoted for reference. View sourceWhat this page covers
- Prerequisites
- Quick Start
- Microsoft Entra ID (keyless, RBAC) — recommended
- Why use Entra ID?
- One-time setup (Azure side)
- One-time setup (Hermes side)
- Configuration written to config.yaml
- Credential resolution order
- Deployment patterns
- Sovereign clouds (Government, China)
Section outline mirrored from the official Hermes Agent documentation. Follow any heading to read the complete text on the source site.
Upstream outline
- Prerequisites
- Quick Start
- Microsoft Entra ID (keyless, RBAC) — recommended
- Why use Entra ID?
- One-time setup (Azure side)
- One-time setup (Hermes side)
- Configuration written to config.yaml
- Credential resolution order
- Deployment patterns
- Sovereign clouds (Government, China)
- Health checks
- Limitations
- Configuration (written to config.yaml)
- OpenAI-style endpoints (GPT, Llama, etc.)
Section map
Prerequisites
Maps prerequisites to the Guides & Tutorials documentation path, with the source page reserved for exact commands and updates.
Quick Start
Maps quick start to the Guides & Tutorials documentation path, with the source page reserved for exact commands and updates.
Microsoft Entra ID (keyless, RBAC) — recommended
Maps microsoft entra id (keyless, rbac) — recommended to the Guides & Tutorials documentation path, with the source page reserved for exact commands and updates.
Why use Entra ID?
Maps why use entra id? to the Guides & Tutorials documentation path, with the source page reserved for exact commands and updates.
One-time setup (Azure side)
Maps one-time setup (azure side) to the Guides & Tutorials documentation path, with the source page reserved for exact commands and updates.
One-time setup (Hermes side)
Maps one-time setup (hermes side) to the Guides & Tutorials documentation path, with the source page reserved for exact commands and updates.
Configuration written to config.yaml
Maps configuration written to config.yaml to the Guides & Tutorials documentation path, with the source page reserved for exact commands and updates.
Credential resolution order
Maps credential resolution order to the Guides & Tutorials documentation path, with the source page reserved for exact commands and updates.
Implementation notes
- Use this Guides & Tutorials doc as a navigation page first: the local clone mirrors the source structure and links each heading back to the authoritative upstream section.
- Primary decision areas: Prerequisites, Quick Start, Microsoft Entra ID (keyless, RBAC) — recommended, Why use Entra ID?, One-time setup (Azure side). Read those source anchors before changing installs, credentials, automation, or runtime configuration.
- Useful search signals for this doc: microsoft, foundry, provider, supports, formerly. These are derived from the public title and summary so the clone remains lightweight.
Decision table
Use when you need orientation for microsoft foundry before applying exact upstream commands.
Open the source anchor for Prerequisites and confirm platform-specific requirements before changing configuration.
Use the upstream page as the authority for current syntax, release changes, and security-sensitive steps.
Verification checklist
- Use this page to orient yourself within Guides & Tutorials, then open the linked source page for exact current syntax.
- Start with the source section for Prerequisites; do not rely on the local summary for commands or secrets.
- Check platform, install method, provider, and credential assumptions before changing a real environment.
- Review the source section for Quick Start if the page involves setup, automation, messaging, or runtime behavior.
- After applying anything from the source, run the smallest relevant smoke test before widening scope.
Risk notes
Treat every token, OAuth grant, secret manager entry, and API key as production-sensitive. Verify least privilege and revocation before reuse.
Set provider, token, and retry limits before scaling the workflow beyond a single test run.
Check filesystem, shell, browser, repository, and server permissions before granting the agent write access.
What this page covers
- Core concept and where it fits in the Hermes Agent system.
- Setup or operating context implied by the upstream page summary.
- The source page link for full current details and updates.
Source mirror note
This page is generated from the public Hermes Bible index so the clone has the same route coverage and search surface. It stores the public title, category, summary, and source link locally; use the source page for full upstream text and updates.
Open source page