Use your own GitHub account for the exercises and your own Azure subscription for Challenges 5 and 6. No accounts, subscriptions, or preconfigured lab environments are supplied. Reading this guide needs no account.
Use your own accounts#
Sign in with your own GitHub account with active GitHub Copilot access, then fork ABBARNABIL/agentic-sdlc-workshop into your account or an organization you control. Clone or open your fork, not the upstream MicroHack monorepo. Use a feature branch for the exercises. You will configure Azure access for your own subscription when you reach the Azure challenges.
Check the remote before creating issues, pushing code, or configuring OIDC:
git remote -v
git status
git switch -c workshop/my-session
The application intentionally has missing features. Building the cart, tests, and Azure pipeline is the workshop, not an installation step.
Check prerequisites#
- GitHub Copilot: an active seat with Chat and the agent capabilities you intend to use. Ask your administrator about CLI, MCP, coding-agent, code-review, and agentic-workflow policies; availability varies by plan and organization. A real response about an open source file is the check, not just an installed extension.
- An editing environment: GitHub Codespaces, VS Code with Docker and Dev Containers, or local VS Code and the runtimes below. Codespaces compute and storage can incur charges.
- Runtime choices: Node.js 24 and npm for the frontend and default TypeScript API. For another API, use Python 3.13, .NET 10, or Java 17 with Maven. Run only one API at a time; all variants use port 3000.
- For Challenges 5 and 6 only: your own Azure subscription with a budget, a dedicated workshop resource group you create in it, Contributor on the intended scope, the extra roles your SRE Agent requires, supported region/capacity, and a GitHub-to-Azure OIDC federated identity you configure for your fork. If you cannot create federated credentials or role assignments, involve your administrator.
You can do Challenges 1–4 without Azure. Challenge 6 requires your working Challenge 5 deployment in your own Azure subscription. Do not mark skipped exercises complete.
Open the development environment#
Codespaces or Dev Containers#
In your fork, choose Code → Codespaces → Create codespace on main. There is one root configuration, Agentic SDLC; you do not need the upstream monorepo's track picker. For local VS Code, open the repository root and choose Dev Containers: Reopen in Container.
The container installs Node 24, Python 3.13, .NET 10, Java 17, Maven, make, SQLite, GitHub CLI, and Azure CLI. Creation installs and builds the default TypeScript API and frontend. If creation fails, read the creation log and resolve the reported dependency or network problem before continuing.
Run app commands from src/:
cd src
make dev
Open the forwarded 5137 frontend port. Keep it and the API port private. Vite proxies /api to port 3000 inside the environment, so you do not have to publish an unauthenticated API. The guide itself is in website/ and is a separate application.
Local setup, including Windows#
From the repository root, install and build the two packages:
npm --prefix src/api-ts ci
npm --prefix src/frontend ci
npm --prefix src/api-ts run build
npm --prefix src/frontend run build
Start the API in one terminal:
npm --prefix src/api-ts run dev
Start the frontend in a second terminal:
npm --prefix src/frontend run dev
Open http://localhost:5137. The API is at http://localhost:3000/api/products, with OpenAPI at http://localhost:3000/api-docs. The SQLite database is initialized and seeded on API startup. Do not use real customer data or payment details in this demo.
These npm commands also work in PowerShell, without make. If you prefer make, use the container, WSL, or a suitable local toolchain. better-sqlite3 may need native build tools if a prebuilt binary is unavailable.
Choose another API#
From src/, first run the matching install target (make install-cs, make install-py, or make install-java) and make install-frontend. Then use make dev-cs, make dev-py, or make dev-java. You do not need to install every language track to do the workshop locally. See the application guide and build instructions.
Confirm the baseline#
Load the product catalogue and confirm products come from the API. Stop and fix startup errors rather than asking an agent to build on a broken environment.
From the repository root:
npm --prefix src/api-ts run test -- --run
The frontend's existing tests use Playwright. In src/frontend, install its browser with npx playwright install chromium, then run npm test. The API tests cover the default track; other tracks have their own commands in src/README.md. Test additions during the workshop should use the existing app frameworks.
Review .vscode/mcp.json before enabling any MCP server. Servers may download tools, request authentication, or expose external data/actions; none is needed just to read this site or run the default app. Enable only what you intend to use.
Before you deploy to Azure#
Use your own Azure subscription and verify that you have the required permissions. Sign in with the Azure account that can access it and explicitly select the subscription before provisioning anything. Replace YOUR-SUBSCRIPTION-ID with its actual ID:
az login
az account list --output table
az account set --subscription "YOUR-SUBSCRIPTION-ID"
az account show --query "{subscription:name,id:id}" --output table
Azure Container Apps, Container Registry, Log Analytics, storage, SRE Agent, and supporting services may incur charges billed to your subscription. Set a budget and cost alerts, and plan to remove your lab resources afterward. Budgets send alerts; they do not automatically cap spending. Create a dedicated, non-production resource group in your subscription. The starter Bicep and workflow are incomplete teaching scaffolds, not production defaults.
The Azure workflow is stored as .github/workflows/deploy.yml.example, so Actions will not run it. Only the separate Pages workflow is active. Finish and review the exercise workflow in your own fork, then copy it to deploy.yml when you deliberately opt in. Use your real fork and branch/environment in the OIDC subject; never commit credentials. No Azure provisioning or credential creation is performed by this guide.
Read the finish and cleanup checklist now, before creating resources. For a shared environment, ask its owner before changing or deleting anything.
How progress and solutions work#
Check success criteria only after you have demonstrated them, then mark the challenge complete. Progress and the resume location stay in this browser on this device, using local storage; there is no account, backend, analytics, or cross-device sync. Private browsing, clearing site data, or blocked storage can erase progress. The interface reports storage failures instead of claiming it saved.
Solution pages require an explicit Reveal solution action on every visit and are excluded from search. This is a spoiler boundary, not access control: their source is public. The full learning material remains in Markdown in the repository.
Continue to Challenge 1.