adding provisionState:Scheduled for deletion workaround

Author: Simon Jakesch

articles/container-apps/troubleshooting.md

@@ -29,6 +29,7 @@ The following table lists issues you might encounter while using Azure Container
 | Responses not as expected | The container app endpoint responds to requests, but the responses aren't as expected. | [Verify traffic is routed to the correct revision](#verify-traffic-is-routed-to-the-correct-revision)<br><br>[Verify you're using unique tags when deploying images to the container registry](/azure/container-registry/container-registry-image-tag-version) |
 | Missing parameters error | You receive error messages about missing parameters when you run `az containerapp` commands in the Azure CLI, or run cmdlets from the `Az.App` module in Azure PowerShell. | [Verify latest version of Azure Container Apps extension is installed](#verify-latest-version-of-azure-container-apps-extension-is-installed) |
 | Preview features not available | [Preview features](./whats-new.md) are not available when you run `az containerapp` commands in the Azure CLI. | [Verify Azure Container Apps extension allows preview features](#verify-azure-container-apps-extension-allows-preview-features) |
+| Deleting your app or environment doesn't work | This issue is often accompanied by a message such as **provisioningState: ScheduledForDelete**.  | [Manually delete the VNet being used](#manually-delete-the-vnet-being-used-by-the-azure-container-apps-environment) |
 
 ## View logs
 
@@ -212,6 +213,27 @@ If [preview features](./whats-new.md) are not available when you run `az contain
 az extension add --name containerapp --upgrade --allow-preview true
 ```
 
+
+## Manually delete the VNet being used by the Azure Container Apps environment
+
+If you receive the message **provisioningState: ScheduledForDelete**, but your environment fails to actually delete, make sure to delete your associated VNet manually.
+
+1. Identify the VNet being used by the environment you're trying to delete:
+```azurecli
+az containerapp env show --resource-group $RG --name $ACA_ENV
+```
+In the output shown above look for the `infrastructureSubnetId` and note down the VNet name.
+
+2. Delete the VNet manually:
+```azurecli
+az network vnet delete --resource-group $RG --name $VNET_NAME
+```
+
+3. Delete the Azure Container Apps environment:
+```azurecli
+az containerapp env delete --resource-group $RG --name $ACA_ENV --yes
+```
+
 ## Next steps
 
 > [!div class="nextstepaction"]