Azure API Management update 4 April

On 4 April, we started a regular[ Azure API Management](https://aka.ms/apimrocks) service update. The update includes the following bug fixes, changes and new features: * You can now update the `isBuffered `property of a Logger through [the PUT Logger call](https://docs.microsoft.com/en-us/rest/api/apimanagement/2019-01-01/logger/createorupdate) or set it through ARM templates. * You can now remove the Managed Service Identity associated with a service through [the PATCH service call](https://docs.microsoft.com/en-us/rest/api/apimanagement/2019-01-01/apimanagementservice/update) with the `“identity”: { "type": "None" }` field. * You can now apply [the CORS policy](https://docs.microsoft.com/en-us/azure/api-management/api-management-cross-domain-policies#CORS) at all scopes. * The exported OpenAPI specification file will only have the `requestBody` parameter present if it is specified. Before, `requestBody` was an empty object `{}`, even for HEAD or OPTIONS requests. * We fixed a `quota` policy bug, which caused extensive CPU usage. * We fixed a configuration sync bug, which might have caused intermittent `404 Not Found` responses for existing APIs and operations. * You can now create a user with a “pending” state using [the REST API call](https://docs.microsoft.com/en-us/rest/api/apimanagement/2019-01-01/user/createorupdate). * Newly registered users no longer need to re-input their password when clicking a confirmation link from an email. * New restrictions apply when creating a revision through [the PUT API call](https://docs.microsoft.com/en-us/rest/api/apimanagement/2019-01-01/apis/createorupdate): * All revisions of the API should have the same: `Name`, `Path`, `Description`, `Protocols`, `ApiVersion`, `ApiVersionDescription` and `ApiVersionSetId` parameters. * These properties can only be changed for the current revision and the changes will be propagated to all other revisions of the API. We deploy updates gradually. It usually takes a week or more for every active service instance to receive the updates. * API Management * Features * [ API Management](https://azure.microsoft.com/en-gb/products/api-management/)