Optional deployment and cleanup
Deployment is optional after the workshop. Azure Container Apps hosts the existing .NET services; the agents continue to execute in InterviewCoach.Agent.
Use an approved, access-restricted development environment with fictional data. Review development endpoints, record access, and upload retention before exposing the app.
Check the deployment entry point
Section titled “Check the deployment entry point”The root apphost.cs already runs the complete interview. Follow this setup only if you choose to deploy your learner project.
azure.yaml targets the separate project at src/InterviewCoach.AppHost/InterviewCoach.AppHost.csproj. That AppHost stays in its starter state during the core lessons. The deployment patch adds its service connections and selects handoff mode. It changes only src/InterviewCoach.AppHost/AppHost.cs and src/InterviewCoach.AppHost/appsettings.json. It keeps your agents and WorkshopHosting.cs unchanged.
Download the deployment AppHost patch into your working project’s root. From that folder, run the check below. Run the second command only when the check succeeds.
git apply --check ./deployment-apphost.patchgit apply ./deployment-apphost.patchgit apply --check ./deployment-apphost.patchgit apply ./deployment-apphost.patchIf the check fails, keep your changes and compare the named file with the 08-complete checkpoint. The standalone example already has the complete deployment AppHost and does not need this patch.
Configure the project-based AppHost’s appsettings.json for deployment. See entry-point details.
The learner checkpoint keeps Foundry reuse enabled. Supply the same four MicrosoftFoundry:Existing identifiers to the deployment entry point’s configuration; its configuration is separate from the root file-based AppHost. Review the existing model’s access for the deployed identity. See existing Foundry resources.
Provision an approved development environment
Section titled “Provision an approved development environment”Follow the deployment commands and account checks. Confirm the selected subscription, region, model access, capacity, and cleanup owner before azd up.
Check the deployed application
Section titled “Check the deployed application”Repeat the summary-agent lesson’s short interview and inspect its tool calls and saved summary. The deployment checklist covers service connectivity, identity, and failure diagnosis.
Remove only the resources you own
Section titled “Remove only the resources you own”For a running local AppHost, run this from the folder that started it:
aspire stop --apphost ./apphost.csaspire stop --apphost ./apphost.csCloud resources remain until cleanup. The example and learner share the Chapter 0 Foundry account and deployment. Keep them until both projects are finished. Review any separate azd environment too; never assume its cleanup command owns the shared model. Follow the cleanup reference to review each scope and remove only owned resources.