In Event Hub, I can add my Function App's MSI as a data reader, but in the function I cannot use trigger bindings to read from the queue without using a SecureAccess Key. We are trying to go password free wherever possible, and Azure has been promoting this course of action, so why do we need secret keys for reading from the queue? It then forces us to create and share a secret key for partner teams to read from our queue, rather than just permissioning them in Event Hub.170 votes
We don’t have an exact timeline for this, but this is something we’re eager to light up and have some preliminary work underway for. This will likely show up for Storage first, but messaging services like Event Hub would be shortly after.
would like the ability to use the new key vault reference in local.settings.json for local debugging instead of needing to have secrets in plain text. this would allow dev teams to leverage key vault as the central location for secret management.7 votes
This is something we’re looking to enable through the Core Tools.
I really want to get rid of the connection strings in my functions and I want to be able to switch to the Azure.Identity SDK for auth. I understand that this will be a breaking change, however some communication about the plan would be nice.1 vote
We’re unable to provide a specific timeline on this here, but it is certainly planned. Likely this will come in phases, with the Storage support being made available first.
- Don't see your idea?