Jeff Hollan

Is still an issue. It is documented here https://docs.microsoft.com/en-us/azure/azure-functions/functions-bindings-cosmosdb-v2?tabs=csharp#http-trigger-look-up-id-from-route-data-using-sqlquery and does even link to this issue.

It's a valid feature and potentially just a few lines of code, but not yet at the top of the backlog. Keep letting us know (via 👍 or whatever) that...

The path forward to adding new trigger support for Azure Functions is having the service integrate with Azure Event Grid. We have made this request to the Azure Storage team...

@denniceritchie can you potentially open another issue with details on what you are seeing in Premium / App Service Plan that isn't working? I'm not aware of any issues that...

At this moment you shouldn’t need to wait for the VNet routes to establish when adding a service endpoint / private link service to call from your function. However, you...

Still coming - best ETA would be end of this year. We hit an issue with the deployment for the earlier ETA so doing a bit phased rollout later this...

Heads up preview just went live for West Europe - let us know if you have any issues with this and hope to push it out globally in the coming...

Just updating - this is now GLOBAL, and generally available.

I think one challenge I have is that I don't think I would recommend ever using the ConnectionString to store my connection strings unless I'm using a library that requires...

Or put differently - is there any reason we should just have people put these all in "values" and then they don't have to worry about know what prefix to...