Resource clean up

docs/deployment/azure/aca-deployment-azd-in-depth.md

@@ -403,3 +403,5 @@ azd env new
 ```
 
 This will prompt the user for subscription and resource group information again and subsequent `azd up`, `azd provision`, and `azd deploy` invocations will use this new environment by default. The `--environment` switch can be applied to these commands to switch between environments.
+
+[!INCLUDE [clean-up-resources](../../includes/clean-up-resources.md)]

docs/deployment/azure/aca-deployment-github-actions.md

@@ -153,3 +153,5 @@ The Azure Developer CLI enables you to automatically create CICD pipelines with
     :::image type="content" source="media/deployment-links.png" alt-text="A screenshot showing the deployed app links.":::
 
 Congratulations! You successfully deployed a .NET Aspire app using the Azure Developer CLI and GitHub Actions.
+
+[!INCLUDE [clean-up-resources](../../includes/clean-up-resources.md)]

docs/deployment/azure/aca-deployment.md

@@ -52,3 +52,5 @@ Click the **Application URL** link to open the front end in the browser.
 :::image type="content" source="../../media/front-end-open.png" alt-text="A screenshot of the .NET Aspire app's front end in the browser.":::
 
 When you click the "Weather" node in the navigation bar, the front end `web` container app makes a call to the `apiservice` container app to get data. The front end's output will be cached using the `redis` container app and the [.NET Aspire Redis Output Caching component](../../caching/stackexchange-redis-output-caching-component.md). As you refresh the front end a few times, you'll notice that the weather data is cached. It will update after a few seconds.
+
+[!INCLUDE [clean-up-resources](../../includes/clean-up-resources.md)]

docs/includes/clean-up-resources.md

@@ -0,0 +1,7 @@
+## Clean up resources
+
+Run the following Azure CLI command to delete the resource group when you no longer need the Azure resources you created. Deleting the resource group also deletes the resources contained inside of it.
+
+```azurecli
+az group delete --name <your-resource-group-name>
+```

docs/messaging/messaging-components.md

@@ -294,3 +294,5 @@ The sample app is now ready for testing. Verify that the data submitted to the A
 1. Switch back to the **AspireWorkerService** logs. You should see the test message printed in the output logs.
 
 Congratulations! You created and configured an ASP.NET Core API that connects to Azure Service Bus using Aspire components.
+
+[!INCLUDE [clean-up-resources](../includes/clean-up-resources.md)]

docs/storage/azure-storage-components.md

@@ -241,6 +241,6 @@ Since you choose to use Azurite, there's no need to clean up these resources whe
 :::zone-end
 :::zone pivot="azure-portal,azure-cli"
 
-Don't forget to clean up any Azure resources when you're done testing them.
+[!INCLUDE [clean-up-resources](../includes/clean-up-resources.md)]
 
 :::zone-end