AzureRM REST API bug - HTTP response code for DELETE method of /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.CognitiveServices/accounts/{accountName}/projects/{projectName}

[shigeyf]

Technical Feedback

AzureRM REST API Spec for Azure AI Services (CognitiveServices) seems to have an inconsistency against the real implementation.

The "DELETE" method for AI Foundry Project resources (Microsoft.CognitiveServices/accounts/{accountName}/projects/{projectName}) actually returns HTTP status code 200 as response.

But the spec says, "Returns HTTP status code 202 or 204". Please see the spec doc as below:
https://github.com/Azure/azure-rest-api-specs/blob/main/specification/cognitiveservices/resource-manager/Microsoft.CognitiveServices/stable/2025-06-01/cognitiveservices.json#L3865

Desired Outcome

The REST API Spec files should be consistent with the AzureRM REST API implementation.

This is because the REST API Spec files are used for many implementation of 1P/3P Azure SDKs.
The inconsistency of response codes causes the problem.

Current Workaround

No workaround without the suggested fix above.

[leestott]

@shigeyf would this be a good Potential Workaround Suggestions

1. Client-Side Tolerance

   • Modify SDK or client logic to accept 200 as a valid success response for DELETE.
   • Example in TypeScript:

     if ([200, 202, 204].includes(response.status)) {
       // Proceed with success logic
     } else {
       throw new Error(`Unexpected status code: ${response.status}`);
     }

2. Custom OpenAPI Patch

   • Locally patch the spec file to include 200 in the response schema before regenerating SDKs.
   • This is especially useful for internal tooling or CI/CD pipelines.

3. Suppress Validation Errors

   • If using tools like AutoRest or Swagger Codegen, configure them to suppress strict response code validation for DELETE operations.

4. Raise a PR or GitHub Issue

   • Submit a pull request or open an issue on the [Azure REST API Specs repo](https://github.com/Azure/azure-rest-api-specs/issues) to formally request the update.
   • Include your observed behavior and justification (SDK impact, LRO misalignment, etc.).