---
title: "Discussion on \"My Azure Journey #2: Blob Trigger Silence, a Missing Setting, and Making Managed Identity Work\" | Hashnode"
description: "Discussion on \"My Azure Journey #2: Blob Trigger Silence, a Missing Setting, and Making Managed Identity Work\". My Azure Function blob trigger never fired. Here's how I fixed a missing AzureWebJobsStorage setting, managed identity roles, and a 403 error"
url: "https://hashnode.com/posts/my-azure-journey-2-blob-trigger-silence-a-missing-setting-and-making-managed-identity-work/6ac253980b766fff93c0b811"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [My Azure Journey #2: Blob Trigger Silence, a Missing Setting, and Making Managed Identity Work](https://saseek.com/my-azure-journey-2-blob-trigger-silence-a-missing-setting-and-making-managed-identity-work?utm_source=hashnode&utm_medium=feed)

My Azure Function blob trigger never fired. Here's how I fixed a missing AzureWebJobsStorage setting, managed identity roles, and a 403 error

Oct 4 · 6 min read · saseek.com  
Read the article

-   [#azure](https://hashnode.com/tag/azure)
-   [#azure-functions](https://hashnode.com/tag/azure-functions)
-   [#azuretalks](https://hashnode.com/tag/azuretalks)
-   [#azure-devops](https://hashnode.com/tag/azure-devops)
-   [#azure-identity](https://hashnode.com/tag/azure-identity)

## Written by

[Saseek Azmi](https://hashnode.com/@saseek)

@saseek · Chennai, India

  
[View profile](https://hashnode.com/@saseek)

Senior Software Engineer @Relevantz

Senior Software Engineer @Relevantz | I write about modern JavaScript & building web apps

## Responses 2

Markdown supported · ⌘↵ to post

[UCELI Cloud](https://hashnode.com/@ucelicloud)

[Oct 4](https://hashnode.com/posts/my-azure-journey-2-blob-trigger-silence-a-missing-setting-and-making-managed-identity-work/6ac253980b766fff93c0b811/comment/6ac25f988f224414f9e66ab4)

Which Functions runtime and storage-extension/extension-bundle versions did you use for the role-removal test?

There is a distinction to capture here: Microsoft's current permissions table lists Storage Blob Data Owner + Storage Queue Data Contributor for the blob trigger, and additional Storage Queue Data Contributor + Storage Account Contributor permissions in host-required storage. This is separate from the base AzureWebJobsStorage requirement: [learn.microsoft.com/en-us/azure/azure-functions/m…](https://learn.microsoft.com/en-us/azure/azure-functions/manage-connections?pivots=functions-auth-identity#grant-permissions-to-an-identity)

Since your host and trigger share an account, including the exact versions and a fresh host start after removing the role would help readers reproduce your result. The specific denied operation in storage logs would also help explain any difference from the documented permissions.

[Saseek Azmi](https://hashnode.com/@saseek)

[Oct 4](https://hashnode.com/posts/my-azure-journey-2-blob-trigger-silence-a-missing-setting-and-making-managed-identity-work/6ac253980b766fff93c0b811/comment/6ac25f988f224414f9e66ab4#reply-6ac27be4cc422d0517317648)

Functions runtime ~4 (FUNCTIONS\_EXTENSION\_VERSION = ~4), Node worker, Consumption plan, and the extension bundle range \[4.\*, 5.0.0) in host.json (the platform-generated default). I didn't record the exact bundle or Storage extension version that actually resolved.