Update TroubleshootingSteps.md file with latest errors 1

Author: NirajC-Microsoft

docs/TroubleShootingSteps.md

@@ -158,7 +158,7 @@ Use these as quick reference guides to unblock your deployments.
 | **FlagMustBeSetForRestore/<br>NameUnavailable/<br>CustomDomainInUse** | Soft-deleted resource requires restore flag or purge | This error occurs when you try to deploy a Cognitive Services resource that was **soft-deleted** earlier. Azure requires you to explicitly set the **`restore` flag** to `true` if you want to recover the soft-deleted resource. If you don't want to restore the resource, you must **purge the deleted resource** first before redeploying.<br><br>**Example causes:**<br><ul><li>Trying to redeploy a Cognitive Services account with the same name as a previously deleted one</li><li>The deleted resource still exists in a **soft-delete retention state**</li></ul><br>**How to fix:**<br><ul><li>If you want to restore → add `"restore": true` in your template properties</li><li>If you want a fresh deployment → purge the resource using:<br>`az cognitiveservices account purge --name <resource-name> --resource-group <resource-group> --location <location>`</li><li>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)</li></ul> |
 | **ContainerAppOperationError** | Container image build or deployment issue | <ul><li>The error is likely due to an improperly built container image. For resolution steps, refer to the [Azure Container Registry (ACR) – Build & Push Guide](./ACRBuildPushGuide.md)</li></ul> |
 | **LinkedAuthorizationFailed** | Service principal lacks permission to use a linked resource required for deployment | This error occurs when a service principal doesn't have permission to perform an action on a linked resource that is required for the operation (e.g., cluster creation).<br><br>**Common causes:**<br><ul><li>The service principal has permission on the primary resource but lacks permission on the linked scope</li><li>Missing role assignment for operations like `Microsoft.Network/ddosProtectionPlans/join/action`</li></ul><br>**Resolution:**<br><ul><li>Identify the **service principal**, **resource**, and **operation** from the error message</li><li>Grant the service principal the required permissions on the linked resource</li><li>Use [Assign Azure roles using the Azure portal](https://learn.microsoft.com/en-us/azure/role-based-access-control/role-assignments-portal) to add the role assignment</li><li>For more details, refer to [LinkedAuthorizationFailed error](https://learn.microsoft.com/en-us/troubleshoot/azure/azure-kubernetes/error-codes/linkedauthorizationfailed-error)</li></ul> |
-| **ContainerOperationFailure** | Container image or storage resource does not exist | This error occurs when an operation fails because the **specified container resource does not exist**. This can happen with Azure Container Registry images or Azure Storage blob containers.<br><br>**Example error message:**<br>`ContainerOperationFailure: The specified resource does not exist. RequestId:xxxxx Time:xxxxx`<br><br>**Common causes:**<br><ul><li>**Invalid container image tag:** The specified image tag does not exist in the container registry</li><li>**Non-existent container registry:** The container registry endpoint is incorrect or inaccessible</li><li>**Missing blob container:** The storage blob container referenced by the application does not exist</li><li>**Incorrect storage account URL:** The storage account endpoint is misconfigured</li><li>**Permission issues:** The managed identity lacks permissions to access the container registry or storage account</li></ul><br>**Resolution:**<br><ul><li>**Verify container image exists:**<br>`az acr repository show-tags --name <registry-name> --repository <image-name>`</li><li>**Check image tag in deployment:** Ensure the `imageTag` parameter matches an existing tag in the registry</li><li>**Verify storage containers exist:**<br>`az storage container list --account-name <storage-account-name> --auth-mode login`</li><li>**Check role assignments:** Ensure the Container App's managed identity has `AcrPull` role on the container registry and `Storage Blob Data Contributor` role on the storage account</li><li>**Rebuild and push container images:** If images are missing, follow the [ACR Build & Push Guide](./ACRBuildAndPushGuide.md)</li><li>**Verify storage account URL:** Ensure `APP_STORAGE_BLOB_URL` and `APP_STORAGE_QUEUE_URL` in App Configuration point to the correct storage account</li></ul><br>**Reference:**<br><ul><li>[Azure Container Registry troubleshooting](https://learn.microsoft.com/en-us/azure/container-registry/container-registry-troubleshoot-login)</li><li>[Azure Storage troubleshooting](https://learn.microsoft.com/en-us/azure/storage/common/storage-troubleshoot-common-errors)</li></ul> |
+| **ContainerOperationFailure** | Container image or storage resource does not exist | This error occurs when an operation fails because the **specified container resource does not exist**. This can happen with Azure Container Registry images or Azure Storage blob containers.<br><br>**Example error message:**<br>`ContainerOperationFailure: The specified resource does not exist. RequestId:xxxxx Time:xxxxx`<br><br>**Common causes:**<br><ul><li>**Invalid container image tag:** The specified image tag does not exist in the container registry</li><li>**Non-existent container registry:** The container registry endpoint is incorrect or inaccessible</li><li>**Missing blob container:** The storage blob container referenced by the application does not exist</li><li>**Incorrect storage account URL:** The storage account endpoint is misconfigured</li><li>**Permission issues:** The managed identity lacks permissions to access the container registry or storage account</li></ul><br>**Resolution:**<br><ul><li>**Verify container image exists:**<br>`az acr repository show-tags --name <registry-name> --repository <image-name>`</li><li>**Check image tag in deployment:** Ensure the `imageTag` parameter matches an existing tag in the registry</li><li>**Verify storage containers exist:**<br>`az storage container list --account-name <storage-account-name> --auth-mode login`</li><li>**Check role assignments:** Ensure the Container App's managed identity has `AcrPull` role on the container registry and `Storage Blob Data Contributor` role on the storage account</li><li>**Rebuild and push container images:** If images are missing, follow the [ACR Build & Push Guide](./ACRBuildPushGuide.md)</li><li>**Verify storage account URL:** Ensure `APP_STORAGE_BLOB_URL` and `APP_STORAGE_QUEUE_URL` in App Configuration point to the correct storage account</li></ul><br>**Reference:**<br><ul><li>[Azure Container Registry troubleshooting](https://learn.microsoft.com/en-us/azure/container-registry/container-registry-troubleshoot-login)</li><li>[Azure Storage troubleshooting](https://learn.microsoft.com/en-us/azure/storage/common/storage-troubleshoot-common-errors)</li></ul> |
 ---------------------------------
 
 💡 Note: If you encounter any other issues, you can refer to the [Common Deployment Errors](https://learn.microsoft.com/en-us/azure/azure-resource-manager/troubleshooting/common-deployment-errors) documentation.