Users reported receiving a different log format for Azure Functions.

Depending on the hosting plan, Azure Functions logs may contain invalid JSON documents like the following:

{
    "category": "FunctionAppLogs",
    "location": "useast",
    "properties": {
        'appName': 'myapp'
    }
}

However, on some deployments, it seems that Azure Functions now sends invalid JSON wrapped in a string:

{
    "category": "FunctionAppLogs",
    "location": "useast",
    "properties": "{'appName': 'myapp'}"
}

This makes the JSON document formally valid. However, the sanitizer won't change the single quote inside the JSON string.

When Azure wraps the invalid JSON in a string, the platformlogs pipeline fails with the following error:

expecting token of type [START_OBJECT] but found [VALUE_STRING]