Open
Description
Issue: According to Microsoft-internal telemetry, a DELETE operation for the Microsoft.Authorization/roleAssignments endpoint may also return HTTP code 204. This may returned when the same DELETE operation is triggered in a quick succession.
Currently all API versions for the Microsoft.Authorization provider list only HTTP code 200 as a valid success return code:
This causes downstream problems as AutoRest clients depend on the API spec to parse the return code and will throw an exception when facing unexpected HTTP codes such as 204 e.g. Azure/azure-libraries-for-net#1139
Expected: Either add a new REST API spec for the Microsoft.Authorization provider or edit the existing ones including HTTP 204 as a valid return code.