Skip to content

Commit 541d4a1

Browse files
simonjjv-jaswel
andauthored
Update articles/container-apps/troubleshooting.md
Co-authored-by: Jason Wells <[email protected]>
1 parent 70824e5 commit 541d4a1

File tree

1 file changed

+7
-5
lines changed

1 file changed

+7
-5
lines changed

articles/container-apps/troubleshooting.md

Lines changed: 7 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -218,11 +218,13 @@ az extension add --name containerapp --upgrade --allow-preview true
218218

219219
If you receive the message **provisioningState: ScheduledForDelete**, but your environment fails to actually delete, make sure to delete your associated VNet manually.
220220

221-
1. Identify the VNet being used by the environment you're trying to delete:
222-
```azurecli
223-
az containerapp env show --resource-group $RG --name $ACA_ENV
224-
```
225-
In the output shown above look for the `infrastructureSubnetId` and note down the VNet name.
221+
1. Identify the VNet being used by the environment you're trying to delete. Replace the \<PLACEHOLDERS\> with your values.
222+
223+
```azurecli
224+
az containerapp env show --resource-group <RESOURCE_GROUP> --name <ENVIRONMENT>
225+
```
226+
227+
In the output, look for `infrastructureSubnetId` and note down the VNet ID. An example VNet ID is `vNet::myVNet.id`.
226228
227229
2. Delete the VNet manually:
228230
```azurecli

0 commit comments

Comments
 (0)