Apokalypt

This fix is present in many of resources due to previous Azure API behaviour. I think that the problem occurs in function_app_\*, web_app_\*, logic_app, ...

Do not merge this change! If you do that you will have other problems 😅 Here is a simple POC of the problem: ```Javascript require('dotenv').config(); const { Client, GatewayIntentBits, ButtonBuilder,...

Apparently, the Azure API has been updated and the error is now clearer (409 instead of 500) :

> @Apokalypt @websolut I'm confused... in response to both of your comments, I am already passing in an `app_service_id` (which in turn lives in an app service plan) and a...

> Thanks @Apokalypt for the PR, can we please hold adding the serverFarmId in the request as I'm trying to confirm with the app service team to see if it's...

@xiaxyi Have you had any news on this subject?

> @Apokalypt telemetry processors should have the request object and also correlation context available for you to consume, more info [here](https://github.com/microsoft/ApplicationInsights-node.js#preprocess-data-with-telemetry-processors). I'm not sure to understand how to proceed. We've...

> Well depends on when do you need the information, we should also be adding headers with correlation context information, have you tried reading the response headers? To be more...

> @Apokalypt It looks like what you're trying to do here could be achieved with the OpenTelemetry [Context](https://opentelemetry.io/docs/specs/otel/context/). If you want to work with the OpenTelemetry based distro that version...

@dschnare Did you find any solutions ? I'm facing the same issue regarding the delay visible in the timestamps EDIT: I just found a solution when looking on the [code](https://github.com/googleapis/nodejs-logging-winston/blob/d43c27d953f80553cb4433afe7a3f1a235a3c922/src/common.ts#L252C1-L258C6)...