Microsoft.Automanage @2022-05-04 API returns 400 Bad request with no response body.

Currently, when I try to deploy a configurationProfiles version using the API provided on [azure-rest-api-specs/automanage.json at main · Azure/azure-rest-api-specs (github.com)](https://github.com/Azure/azure-rest-api-specs/blob/main/specification/automanage/resource-manager/Microsoft.Automanage/stable/2022-05-04/automanage.json), an unexpected 400 code is returned. Here are the details.

API link and body in json format:
PUT https://management.azure.com/subscriptions/(sid)/resourceGroups/yunliutest66/providers/Microsoft.Automanage/configurationProfiles/testprofile/versions/profileversion?api-version=2022-05-04
{
"id": "/subscriptions/(sid)/resourceGroups/yunliutest66/providers/Microsoft.Automanage/configurationProfiles/testprofile/versions/profileversion",
"name": "profileversion",
"type": "Microsoft.Automanage/configurationProfiles/versions",
"location": "westeurope",
"properties": {
"configuration": {
"Antimalware/Enable": false,
"AzureSecurityCenter/Enable": false,
"Backup/Enable": false,
"BootDiagnostics/Enable": true,
"ChangeTrackingAndInventory/Enable": true,
"GuestConfiguration/Enable": true,
"LogAnalytics/Enable": true,
"UpdateManagement/Enable": true,
"VMInsights/Enable": true
}
}
}

Start with specification/automanage/resource-manager/Microsoft.Automanage/stable/2022-05-04/automanage.json and reproduce the shown PUT request for the configuration profile version. Compare the request body with the specification and the returned 400 behavior; done means identifying the cause and updating the API specification or documenting the required request correction.

Written by the indexing model from the issue text.