This upgrades the extension to use the beta version of the v5.x extension. In order to use the new Storage extension, I need to add the new extension to my project. I start by creating an Azure Storage queue-triggered function. Once I deploy to Azure, I want the function to use the identity of the function app. Since I’m starting locally, I want to use my local identity (on my dev laptop). My primary objective is to establish the connection, using an Azure AD identity, to an Azure Storage queue so that the queue trigger executes.
![azure storage emulator access denied azure storage emulator access denied](https://i.stack.imgur.com/WNTWP.png)
My first function using managed identityĪs previously mentioned, my first function to use an identity-based connection is an Azure Storage queue-triggered function. The Live Metrics and Logs are incredibly helpful in figuring out what may be going wrong. I like Application Insights available with my Azure Functions. While creating the Azure Function app, I’m also going to create an Application Insights instance. Since the function will connect to Azure Storage using an identity-based connection, the Azure Function will need to be set up with a managed identity. At the time I’m writing this, Azure Function Consumption plans are not yet supported for use with identity-based connections. Thus, I’ll create a new Azure Functions Premium plan (an App Service plan should also work, but I haven’t tried yet). I know I’m going to eventually deploy this function to Azure. I’ll also use this storage account when provisioning my function app in Azure.
![azure storage emulator access denied azure storage emulator access denied](https://static.wixstatic.com/media/e67998_23c8774e767b4270b4386ec9971792e1~mv2.png)
This storage account will host the queue from which the function will receive messages. I first need to create an Azure Storage account.
![azure storage emulator access denied azure storage emulator access denied](https://docs.microsoft.com/en-us/azure/storage/common/media/storage-monitoring-diagnosing-troubleshooting/overview.png)
#AZURE STORAGE EMULATOR ACCESS DENIED CODE#
Later, I’ll discuss how I was able to apply these learnings to work with Event Hubs.Įager to get to it? Skip to the code samples in my GitHub repo. I’m going to start by describing how I was able to get a very simple Azure Storage queue-triggered function to use an identity-based connection. It’s still early, and thus I expect a few bumps in along the way. This intent of this blog post is to share my initial experiences with the extensions. I’m a fan of having fewer secrets to manage. The new extensions use the new Azure SDK, and as a result, include support for using Azure AD to authenticate to specific Azure resources (a.k.a., managed identities). I recently started experimenting with the beta versions of the new Azure Storage and Event Hub extensions for Azure Functions.