You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-The deployment values either include values that aren't recognized, or required values are missing. Confirm the values for your resource type.
97
-
- You can refer [Invalid Request Content error](https://learn.microsoft.com/en-us/azure/azure-resource-manager/troubleshooting/common-deployment-errors#:~:text=InvalidRequestContent,Template%20reference) documentation.
98
-
99
-
</details>
100
-
101
-
<details><summary><b>Conflict - Cannot use the SKU Basic with File Change Audit for site.</b></summary>
102
-
103
-
- This error happens because File Change Audit logs aren’t supported on Basic SKU App Service Plans.
104
-
105
-
- Upgrading to Premium/Isolated SKU (supports File Change Audit), or
106
-
107
-
- Disabling File Change Audit in Diagnostic Settings if you must stay on Basic.
108
-
- Always cross-check the [supported log types](https://aka.ms/supported-log-types)
109
-
before adding diagnostic logs to your Bicep templates.
- The property **`isHnsEnabled`** (Hierarchical Namespace for Data Lake Gen2) is **read-only** and can only be set during **storage account creation**.
118
-
- Once a storage account is created, this property **cannot be updated**.
119
-
- Trying to update it via ARM template, Bicep, CLI, or Portal will fail.
120
-
121
-
-**Resolution**
122
-
- Create a **new storage account** with `isHnsEnabled=true` if you require hierarchical namespace.
123
-
- Migration may be needed if you already have data.
124
-
- Refer to [Storage Account Update Restrictions](https://aka.ms/storageaccountupdate) for more details.
125
-
126
-
</details>
127
-
93
+
| Issue/Error Code | Description | Steps to Resolve |
|**InvalidRequestContent**|| - The deployment values either include values that aren't recognized, or required values are missing. Confirm the values for your resource type<br>- You can refer [Invalid Request Content error](https://learn.microsoft.com/en-us/azure/azure-resource-manager/troubleshooting/common-deployment-errors#:~:text=InvalidRequestContent,Template%20reference) documentation |
96
+
|**Conflict - Cannot use the SKU Basic with File Change Audit for site**|| - This error happens because File Change Audit logs aren't supported on Basic SKU App Service Plans<br>- Upgrading to Premium/Isolated SKU (supports File Change Audit), or<br>- Disabling File Change Audit in Diagnostic Settings if you must stay on Basic<br>- Always cross-check the [supported log types](https://aka.ms/supported-log-types) before adding diagnostic logs to your Bicep templates |
97
+
|**AccountPropertyCannotBeUpdated**|| - The property **`isHnsEnabled`** (Hierarchical Namespace for Data Lake Gen2) is **read-only** and can only be set during **storage account creation**<br>- Once a storage account is created, this property **cannot be updated**<br>- Trying to update it via ARM template, Bicep, CLI, or Portal will fail<br>**Resolution:**<br>- Create a **new storage account** with `isHnsEnabled=true` if you require hierarchical namespace<br>- Migration may be needed if you already have data<br>- Refer to [Storage Account Update Restrictions](https://aka.ms/storageaccountupdate) for more details |
- The AccountProvisioningStateInvalid error occurs when you try to use resources while they are still in the Accepted provisioning state.
138
-
- This means the deployment has not yet fully completed.
139
-
- To avoid this error, wait until the provisioning state changes to Succeeded.
140
-
- Only use the resources once the deployment is fully completed.
141
-
</details>
142
-
143
-
<details><summary><b>BadRequest - DatabaseAccount is in a failed provisioning state because the previous attempt to create it was not successful</b></summary>
144
-
145
-
- This error occurs when a user attempts to redeploy a resource that previously failed to provision.
146
-
147
-
- To resolve the issue, delete the failed deployment first, then start a new deployment.
148
-
149
-
- For guidance on deleting a resource from a Resource Group, refer to the following link: [Delete an Azure Cosmos DB account](https://learn.microsoft.com/en-us/azure/cosmos-db/nosql/manage-with-powershell#delete-account:~:text=%3A%24enableMultiMaster-,Delete%20an%20Azure%20Cosmos%20DB%20account,-This%20command%20deletes)
150
-
151
-
</details>
104
+
| Issue/Error Code | Description | Steps to Resolve |
|**AccountProvisioningStateInvalid**|| - The AccountProvisioningStateInvalid error occurs when you try to use resources while they are still in the Accepted provisioning state<br>- This means the deployment has not yet fully completed<br>- To avoid this error, wait until the provisioning state changes to Succeeded<br>- Only use the resources once the deployment is fully completed |
107
+
|**BadRequest - DatabaseAccount is in a failed provisioning state because the previous attempt to create it was not successful**|| - This error occurs when a user attempts to redeploy a resource that previously failed to provision<br>- To resolve the issue, delete the failed deployment first, then start a new deployment<br>- For guidance on deleting a resource from a Resource Group, refer to the following link: [Delete an Azure Cosmos DB account](https://learn.microsoft.com/en-us/azure/cosmos-db/nosql/manage-with-powershell#delete-account:~:text=%3A%24enableMultiMaster-,Delete%20an%20Azure%20Cosmos%20DB%20account,-This%20command%20deletes)|
- The updated model may not be supported in the selected region. Please verify its availability in the [Azure AI Foundry models](https://learn.microsoft.com/en-us/azure/ai-foundry/openai/concepts/models?tabs=global-standard%2Cstandard-chat-completions) document.
162
-
163
-
</details>
113
+
| Issue/Error Code | Description | Steps to Resolve |
|**DeploymentModelNotSupported/ServiceModelDeprecated/InvalidResourceProperties**|| - The updated model may not be supported in the selected region. Please verify its availability in the [Azure AI Foundry models](https://learn.microsoft.com/en-us/azure/ai-foundry/openai/concepts/models?tabs=global-standard%2Cstandard-chat-completions) document |
- Trying to redeploy a Cognitive Services account with the same name as a previously deleted one.
173
125
- The deleted resource still exists in a **soft-delete retention state**.
174
126
**How to fix:**
175
-
1. If you want to restore → add `"restore": true` in your template properties.
176
-
2. If you want a fresh deployment → purge the resource using:
177
-
```bash
178
-
az cognitiveservices account purge \
179
-
--name <resource-name> \
180
-
--resource-group <resource-group> \
181
-
--location <location>
182
-
```
183
-
For more details, refer to [Soft delete and resource restore](https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/delete-resource-group?tabs=azure-powershell).
- The error is likely due to an improperly built container image. For resolution steps, refer to the [Azure Container Registry (ACR) – Build & Push Guide](./ACRBuildAndPushGuide.md)
190
-
191
-
</details>
127
+
1. If you want to restore → add `"restore": true` in your template properties<br>2. If you want a fresh deployment → purge the resource using:<br>`az cognitiveservices account purge --name <resource-name> --resource-group <resource-group> --location <location>`<br>- For more details, refer to [Soft delete and resource restore](https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/delete-resource-group?tabs=azure-powershell) |
128
+
|**ContainerAppOperationError**|| - The error is likely due to an improperly built container image. For resolution steps, refer to the [Azure Container Registry (ACR) – Build & Push Guide](./ACRBuildAndPushGuide.md)|
0 commit comments