LogAnalytics Microsoft.OperationalInsights/LinkedStorageAccounts@2020-08-01 PUT response.properties.dataSourceType case sensitivity differs with locations

[teowa]

Description

The swagger is link

I try to PUT LinkedStorageAccounts , but the response's datatype case sensitivity differs with locations. The result doesn't change if I use customlogs or CustomLogs in request. This means sending either customlogs or CustomLogs to Central US will get CustomLogs in response, but customlogs for East US.

Below are the payloads

Request

https://management.azure.com/subscriptions/{{subscriptionId}}/resourceGroups/wt-test-app_ins/providers/Microsoft.OperationalInsights/workspaces/exampleworkspace/linkedStorageAccounts/CustomLogs?api-version=2020-08-01

{
    "properties": {
        "dataSourceType": "CustomLogs",
        "storageAccountIds": [
            "/subscriptions/{{subscriptionId}}/resourceGroups/wt-test-app_ins/providers/Microsoft.Storage/storageAccounts/wantatexamplesa"
        ]
    }
}

Response of dataSourceType is in Camel Case :

Central US

{
    "properties": {
        "dataSourceType": "CustomLogs",
        "storageAccountIds": [
            "/subscriptions/{{subscriptionId}}/resourceGroups/wt-test-app_ins/providers/Microsoft.Storage/storageAccounts/wantatexamplesa"
        ]
    },
    "location": "centralus",
    "id": "/subscriptions/{{subscriptionId}}/resourceGroups/wt-test-app_ins/providers/Microsoft.OperationalInsights/workspaces/exampleworkspace/linkedstorageaccounts/CustomLogs",
    "name": "CustomLogs",
    "type": "Microsoft.OperationalInsights/workspaces/linkedstorageaccounts"
}

x-ms-request-id: 46407c42-861e-438f-9c49-12725480ca6f
x-ms-correlation-request-id: 46407c42-861e-438f-9c49-12725480ca6f

SouthEast Asis

{
    "properties": {
        "dataSourceType": "CustomLogs",
        "storageAccountIds": [
            "/subscriptions/{{subscriptionId}}/resourceGroups/wt-test-app_ins/providers/Microsoft.Storage/storageAccounts/wantatexamplesa"
        ]
    },
    "location": "southeastasia",
    "id": "/subscriptions/{{subscriptionId}}/resourceGroups/wt-test-app_ins/providers/Microsoft.OperationalInsights/workspaces/exampleworkspace/linkedstorageaccounts/CustomLogs",
    "name": "CustomLogs",
    "type": "Microsoft.OperationalInsights/workspaces/linkedstorageaccounts"
}

x-ms-request-id: 556f0686-acf1-464d-9146-64d2c2b386ad
x-ms-correlation-request-id: 556f0686-acf1-464d-9146-64d2c2b386ad

Response of dataSourceType is all lower case:

West Europe

{
    "properties": {
        "dataSourceType": "customlogs",
        "storageAccountIds": [
            "/subscriptions/{{subscriptionId}}/resourceGroups/wt-test-app_ins/providers/Microsoft.Storage/storageAccounts/wantatexamplesa"
        ]
    },
    "id": "/subscriptions/{{subscriptionId}}/resourceGroups/wt-test-app_ins/providers/Microsoft.OperationalInsights/workspaces/exampleworkspace/linkedStorageAccounts/CustomLogs",
    "name": "customlogs",
    "type": "Microsoft.OperationalInsights/workspaces/linkedStorageAccounts"
}

x-ms-request-id: 9c9f0741-f8e8-4fee-9350-c71d39894a35
x-ms-correlation-request-id: aced01f9-926f-403e-ae0b-da6b7c48a538

East US

{
    "properties": {
        "dataSourceType": "customlogs",
        "storageAccountIds": [
            "/subscriptions/{{subscriptionId}}/resourceGroups/wt-test-app_ins/providers/Microsoft.Storage/storageAccounts/wantatexamplesa"
        ]
    },
    "id": "/subscriptions/{{subscriptionId}}/resourceGroups/wt-test-app_ins/providers/Microsoft.OperationalInsights/workspaces/exampleworkspace/linkedStorageAccounts/CustomLogs",
    "name": "customlogs",
    "type": "Microsoft.OperationalInsights/workspaces/linkedStorageAccounts"
}

x-ms-request-id: b71810b6-4b13-4af4-ae1b-268c85662105
x-ms-correlation-request-id: b09a877e-dd9e-4a47-8996-1bed7ae365eb

[teowa]

From

azure-rest-api-specs/specification/operationalinsights/resource-manager/Microsoft.OperationalInsights/stable/2020-08-01/LinkedStorageAccounts.json

Line 204 in 3817b12

"readOnly": true,

, seems the dataSourceType in request body is a read-only property.

One thing need to address is that dataSourceType is used in both request API path and body. The dataSourceType in the response body does not matches the one in request API path. But the ID keeps the same case.

[JackTn]

@dulikvor can you help to see this issue, thanks!