Running Playwright e2e tests on Azure Functions - always spawn error

Question

So, I tried it on Linux - https://stackoverflow.com/q/65067095/2896495.
Then I tried it on Windows - https://github.com/microsoft/playwright-sharp/issues/1076.

Believe me, I tried all the things that come up to my mind. It's always the same result:

spawn UNKNOWN =========================== logs =========================== <launching> C:\home\site\wwwroot\browsers\chromium-833159\chrome-win\chrome.exe --disable-background-networking --enable-features=NetworkService,NetworkServiceInProcess --disable-background-timer-throttling --disable-backgrounding-occluded-windows --disable-breakpad --disable-client-side-phishing-detection --disable-component-extensions-with-background-pages --disable-default-apps --disable-dev-shm-usage --disable-extensions --disable-features=TranslateUI,BlinkGenPropertyTrees,ImprovedCookieControls,SameSiteByDefaultCookies,LazyFrameLoading --disable-hang-monitor --disable-ipc-flooding-protection --disable-popup-blocking --disable-prompt-on-repost --disable-renderer-backgrounding --disable-sync --force-color-profile=srgb --metrics-recording-only --no-first-run --enable-automation --password-store=basic --use-mock-keychain --user-data-dir=C:\local\Temp\playwright_chromiumdev_profile-9V2G59 --remote-debugging-pipe --headless --hide-scrollbars --mute-audio --blink-settings=primaryHoverType=2,availableHoverTypes=2,primaryPointerType=4,availablePointerTypes=4 --no-sandbox --no-startup-window ============================================================ Note: pass debug: "pw:api" to LaunchAsync to capture Playwright logs.

it's slightly different on Linux but the meaning it the same. I tried to deploy with Azure DevOps pipelines and manually from VS2019. It doesn't matter, obviously.

I understand it's probably a security measure but maybe there is any other way?

Can anyone tell me if this even possible? Or maybe any other way of doing this? Docker container will not work for me.