Thiago Almeida

I have also run into this one @weikanglim and @kristenwomack. Deploying with the static web apps CLI works every time though.

It's part of a large sample that includes a lot of other moving parts here in this repo and branch - https://github.com/nzthiago/Durable-Task-Scheduler/tree/durable-maf-agents But it seems to happen pretty much every...

Unfortunately without having the function app name or support ticket number it's difficult for us to investigate. Were you able to disable/turn off the VNet integration before deleting the app...

Thank you for sharing - it looks like the subnet that is being used to VNet integrate the app into already has a service association. If there is another service...

Flex Consumption apps can share the same subnet. You just can't have other non-Flex apps or services in that same subnet. So you could consider creating a new, empty subnet...

But also - yes please follow the support ticket path too to see if the team can share any other thoughts on this as they should be able to take...

In [considerations for Flex Consumption](https://learn.microsoft.com/en-us/azure/azure-functions/functions-networking-options#regional-virtual-network-integration) we document that the subnet delegation required when running in a Flex Consumption plan is Microsoft.App/environments. This differs from the Elastic Premium and Dedicated (App...

@mathewc or @balag0 do you have any notes on this one? It would be good to have WEBSITE_OWNER_NAME and WEBSITE_RESOURCE_GROUP populated for Flex Consumption as documented [here](https://learn.microsoft.com/en-us/azure/app-service/reference-app-settings#app-environment).

Hi everyone - thank you for reporting this, the cancellationtoken shouldn't indeed be signaled like that. The fix to this issue is in [this PR](https://github.com/Azure/azure-webjobs-sdk-extensions/pull/917) and will roll out as...

Hi @xperiandri - sorry I missed this question. The support for the Functions task for Azure DevOps is still under way, being implemented by @FinVamp1. The current workaround would be...