Contribute a template

Getting started

The fastest path from idea to deployable demo — let the Conductor build it for you.

1. 1
   Fork the repo

   Fork MicrosoftLearning/trainer-demo-deploy to your GitHub account and clone it locally.

2. 2
   Open in VS Code and start a Chat

   Open the repo folder in VS Code, then open Copilot Chat (Ctrl+Shift+I).

3. 3
   Select the 01-conductor agent

   Pick 01-conductor from the agent dropdown and describe your demo scenario. The Conductor handles the rest.

Quick start: contribute in 4 steps

Have a great demo scenario? Adding it to the catalog is easier than you think.

1. 01

   Create your template

   Start from this repo so you get the right structure out of the box.

   git clone https://github.com/MicrosoftLearning/trainer-demo-deploy

   • Complete file structure with helpful placeholders
   • Example Bicep infrastructure patterns
   • README and demo guide templates
   • GitHub Copilot instruction files for guidance

   Customize for your scenario

   • Update azure.yaml with your template name
   • Add Azure resources to infra/main.bicep and infra/resources.bicep
   • Fill in the README, prerequisites, and demo guide
2. 02

   Test your template

   Deploy it a few times to make sure everything works.

   azd up

   Confirm that

   • Deployment completes successfully
   • Resources are tagged correctly
   • Demo steps work as documented
   • Cost is reasonable for training scenarios
   • Cleanup works: azd down
3. 03

   Publish to GitHub

   Create a public GitHub repository and push your template. The repo name should match your template name in azure.yaml (e.g., tdd-my-scenario). See publishing instructions in CONTRIBUTING.md.

4. 04

   Submit to the catalog

   Ready to share with the community? Fork this repo and add your template entry to /static/templates.json.

Catalog entry format

Fork trainer-demo-deploy and add your template entry to /static/templates.json:

{
  "title":       "Your Template Title",
  "description": "Brief description of what gets deployed and why",
  "image":       "images/your-architecture.png",
  "author":      "Your Name",
  "authorLink":  "https://github.com/yourusername",
  "repo":        "https://github.com/yourusername/tdd-your-scenario",
  "tags":        ["AZ-104", "storage", "networking"],
  "demoGuide":   "https://github.com/yourusername/tdd-your-scenario/blob/main/demoguide/demoguide.md",
  "deployTime":  "15 minutes",
  "cost":        "$8-12/day"
}

Already have an Azure template?

If you have an existing Bicep or ARM template you can adapt it. The key steps are:

1. Add an azure.yaml file with your template metadata
2. Organize infrastructure files in an infra/ folder
3. Add a README and a demo guide following our format

The this repo shows the expected structure.

Other ways to contribute

Not ready to create a template? You can still help.

We also welcome contributions to improve requested templates from the community.