Description
There are a couple minor issues with the DeviceUpdate "Accounts_Update" operation that should be corrected before this API becomes stable.
-
The request body of this operation defines a "location" property, but the ARM RPC states that patch should not allow "location" to be updated. The "location" property should be removed from the "AccountUpdate" schema and the service should reject an attempt to update it.
-
This operation defines a 201 response, and the service does actually return this for a successful patch, but 201 should only be returned when a resource is created -- not when an existing resource is updated. Since the Account_Update operation cannot create a new account, the 201 response should be removed from the API definition and the service should be changed to return a 200 response for a successful update.
cc: @darkoa-msft