Skip to content

Commit 857f1bb

Browse files
Update Troubleshoot doc - 5
1 parent e0fe951 commit 857f1bb

File tree

1 file changed

+5
-20
lines changed

1 file changed

+5
-20
lines changed

docs/TroubleShootingSteps.md

Lines changed: 5 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -79,27 +79,12 @@ Use these as quick reference guides to unblock your deployments.
7979

8080
---------------------------------
8181

82-
### Network & Infrastructure Configuration
83-
84-
<details>
85-
<summary><b>NetcfgSubnetRangeOutsideVnet</b></summary>
86-
87-
- Ensure the subnet’s IP address range falls within the virtual network’s address space.
88-
- Always validate that the subnet CIDR block is a subset of the VNet range.
89-
- For Azure Bastion, the AzureBastionSubnet must be at least /27.
90-
- Confirm that the AzureBastionSubnet is deployed inside the VNet.
91-
</details>
92-
93-
<details>
94-
<summary><b>DisableExport_PublicNetworkAccessMustBeDisabled</b></summary>
95-
96-
- <b>Check container source:</b> Confirm whether the deployment is using a Docker image or Azure Container Registry (ACR).
97-
- <b>Verify ACR configuration:</b> If ACR is included, review its settings to ensure they comply with Azure requirements.
98-
- <b>Check export settings:</b> If export is disabled in ACR, make sure public network access is also disabled.
99-
- <b>Dedeploy after fix:</b> Correct the configuration and redeploy. This will prevent the Conflict error during deployment.
100-
- For more information refer [ACR Data Loss Prevention](https://learn.microsoft.com/en-us/azure/container-registry/data-loss-prevention) document.
101-
</details>
82+
### Network & Infrastructure Configuration
10283

84+
| Issue/Error Code | Description | Steps to Resolve |
85+
|-----------------|-------------|------------------|
86+
| **NetcfgSubnetRangeOutsideVnet** | | - Ensure the subnet's IP address range falls within the virtual network's address space<br>- Always validate that the subnet CIDR block is a subset of the VNet range<br>- For Azure Bastion, the AzureBastionSubnet must be at least /27<br>- Confirm that the AzureBastionSubnet is deployed inside the VNet |
87+
| **DisableExport_PublicNetworkAccessMustBeDisabled** | | - **Check container source:** Confirm whether the deployment is using a Docker image or Azure Container Registry (ACR)<br>- **Verify ACR configuration:** If ACR is included, review its settings to ensure they comply with Azure requirements<br>- **Check export settings:** If export is disabled in ACR, make sure public network access is also disabled<br>- **Redeploy after fix:** Correct the configuration and redeploy. This will prevent the Conflict error during deployment<br>- For more information refer [ACR Data Loss Prevention](https://learn.microsoft.com/en-us/azure/container-registry/data-loss-prevention) document |
10388

10489
---------------------------------
10590

0 commit comments

Comments
 (0)