Expose StorageClientFactory or QueueProcessorFactory to enable triggering on client-side-encrypted queues
With WebJobs, a custom StorageClientFactory can set an EncryptionPolicy in the DefaultRequestOptions such that encrypted queue messages are transparently decrypted when triggering a WebJob.
Alternatively, the EncryptionPolicy can be set on a queue by queue basis using a custom QueueProcessorFactory.
If these, or a more general way to modify the JobHostConfiguration were provided, then we would be able to store the storage connection string in Azure KeyVault and use client side encryption with Azure Functions apps.1 vote
Marking to needs feedback per below:
Nothing planned but still curious on this one. I think the ask is that you could decrypt on trigger. I expect trigger would work today but you’d have to have decrypt in code per execution. Is hope to decrypt before execution? – Jeff
Currently, the only serverless solution for VNet integration is to upgrade to the premium consumption plan.
It seems like overkill to upgrade to a whole new (way pricier) plan, to simply use a static outbound IP with Azure functions.0 votes
Now that grpc is a full member of .net it would be great that it is also supported in azure functions and in the azure api managment0 votes
The functions Integrate blade displays a warning that the bindings are missing the required direction property. This warning seems to display for all deployed functions even if the property is included.0 votes
- Don't see your idea?