6-Teardown-Infrastructure.md

6. Teardown Infrastructure

!!! tip "BY THE END OF THIS MODULE YOU WILL BE ABLE TO"

- [ ] Understand the importance of resource cleanup and cost management
- [ ] Use `azd down` to deprovision infrastructure safely
- [ ] Recover soft-deleted cognitive services if needed
- [ ] **Lab 6:** Clean up Azure resources and verify removal

---

Bonus Exercises

Before we tear down the project, take a few minutes to do some open-ended exploration.

!!! info "Try These Exploration Prompts"

**Experiment with GitHub Copilot:**

1. Ask: `What other AZD templates could I try for multi-agent scenarios?`
2. Ask: `How can I customize the agent instructions for a healthcare use case?`
3. Ask: `What environment variables control cost optimization?`

**Explore the Azure Portal:**

1. Review Application Insights metrics for your deployment
2. Check the cost analysis for resources provisioned
3. Explore the Microsoft Foundry portal agent playground one more time

---

Deprovision Infra

1. Tearing down infrastructure is as easy as:

   azd down --purge

2. The --purge flag ensures that it also purges soft-deleted Cognitive Service resources, thereby releasing quota held by these resources. Once complete you will see something like this:

   ? Total resources to delete: 11, are you sure you want to continue? Yes
   Deleting your resources can take some time.
   (✓) Done: Deleted resource group rg-nitya-mshack-azd
   (✓) Done: Purging Cognitive Account: aoai-3cz3zkynhvpbc
   
   SUCCESS: Your application was removed from Azure in 11 minutes 4 seconds.

3. (Optional) If you now run azd up again, you will notice the gpt-4.1 model gets deployed since the environment variable was changed (and saved) in the local .azure folder.

   Here is the model deployments before:

   

   And here it is after: