Marcel

Closing this now, since the way to go over Event Grid has not only proven to be stable and effective, but also more cost efficient in my scenario. Since my...

Afaik yes. But there is a way if you can live with some limitations regarding scaling. You can solely rely on the managed identity of your function app to connect...

Thanks for reaching out @scale-tone ! Of course, here you go: host.json ```json { "version": "2.0", "logging": { "applicationInsights": { "samplingSettings": { "isEnabled": true, "excludedTypes": "Request" }, "enableLiveMetricsFilters": true }...

PS, looking through the DevTools I've found this, though Javascript is _not_ disabled on that site. 

Hi, thanks for your work. Apologies for the late reply. I have switched to an isolated azure function with the ASP.NET integration. It builds fine and I can run it...

Hi, I can confirm, that even if deployed in Azure, I am getting this error on pageload.. if I remove the ASP.NET integration and re-deploy, it works without the 401...

PS: Even without the ASP.NET integration I am experiencing an error. When I enter an orchestration the history cannot be displayed, due to an 401 error. The failures seem to...

Hi @scale-tone , of course, here you go. EasyAuth was not changed, and it used to work fine in the injected/in-process version of the app deployment.   This is...

I'm also having problems with OAUTH2 and the `Implicit` mode using Microsoft Entra External ID (sucessor to B2C). On trying to fetch a token, a new BCP window opens, which...

I stumbled on this while investigating why the request body received from a (deployed to azure) function app is empty. Contrary to the above, I don't see this behaviour running...