`Microsoft.Automation/automationAccounts@2021-06-22` - `ROUNDTRIP_INCONSISTENT_PROPERTY`

I made PUT request according to its example: https://github.com/Azure/azure-rest-api-specs/blob/main/specification\automation\resource-manager\Microsoft.Automation\stable\2021-06-22\examples\createOrUpdateAutomationAccount.json
And found the properties in GET response body is inconsistent with the properties in PUT request body.

Summary
```
{
"location": "westeurope",
"properties": {
"sku": {
"name": Got "Basic" in response, expect "Free"
}
}
}
```

PUT request:
```
{
"location": "westeurope",
"properties": {
"sku": {
"name": "Free"
}
},
"tags": {}
}
```

GET request:
```
{
"name": "acctest2194",
"systemData": {
"createdAt": "2022-01-20T08:56:26.307+00:00",
"lastModifiedAt": "2022-01-20T08:56:26.307+00:00"
},
"id": "/subscriptions/67a9759d-d099-4aa8-8675-e6cfd669c3f4/resourceGroups/acctest2625/providers/Microsoft.Automation/automationAccounts/acctest2194",
"type": "Microsoft.Automation/AutomationAccounts",
"location": "westeurope",
"tags": {},
"etag": null,
"properties": {
"disableLocalAuth": false,
"sku": {
"name": "Basic",
"family": null,
"capacity": null
},
"state": "Ok",
"RegistrationUrl": "https://4a0f853c-8111-42b0-9df8-16f972a122b9.agentsvc.we.azure-automation.net/accounts/4a0f853c-8111-42b0-9df8-16f972a122b9",
"encryption": {
"keySource": "Microsoft.Automation",
"identity": {
"userAssignedIdentity": null
}
},
"privateEndpointConnections": [],
"automationHybridServiceUrl": "https://4a0f853c-8111-42b0-9df8-16f972a122b9.jrds.we.azure-automation.net/automationAccounts/4a0f853c-8111-42b0-9df8-16f972a122b9",
"RuntimeConfiguration": {
"powershell": {
"builtinModules": {
"Az": "6.5.0"
}
},
"powershell7": {
"builtinModules": {
"Az": "6.5.0"
}
}
},
"creationTime": "2022-01-20T08:56:26.307+00:00",
"lastModifiedBy": null,
"lastModifiedTime": "2022-01-20T08:56:26.307+00:00"
}
}
```

Start with the referenced createOrUpdateAutomationAccount.json example under specification/automation/resource-manager/Microsoft.Automation/stable/2021-06-22 and compare its PUT schema with the reported GET response. Determine whether the inconsistency belongs in the API specification or the service behavior; done means the expected SKU behavior and any required specification change are agreed and validated.

Written by the indexing model from the issue text.