Microsoft shares a deployment and promotion pattern for Foundry Toolbox
Microsoft’s new deployment guide explains how shared Foundry Toolbox versions can evolve independently of individual agents.
It recommends a separate azure.yaml and deployment step for each Toolbox, with project infrastructure and connections provisioned first and environment-specific outputs supplied through GitHub Actions.
Immutable versions can be tested through version-specific endpoints before promotion to the stable consumer endpoint. Promoting a retained version supports rollback of Toolbox configuration, while downstream services remain independently changeable.
The sample promotes immediately after deployment; the article distinguishes that behavior from a production process that validates candidates before promotion.
Partner briefing
- What it is
A recommended Foundry Toolbox deployment and release-management pattern.
- What’s changing
Separates shared Toolbox version ownership and promotion from agent deployment.
- Why it matters
Supports independent testing and controlled default-version changes across consuming agents.
- Who it affects
Developers and platform teams managing shared Foundry tools.