Azure Functions with Event Grid Not Triggering on Blob Create Events - No Logs or Errors
I'm maintaining legacy code that I'm currently working with an scenario where my Azure Function, set to trigger on Event Grid events for Blob creation, is not firing as expected. I've configured the Event Grid to send notifications when a new blob is created in my storage account, but despite the configuration appearing correct, the function does not log any events or errors. Here's a snippet of my function's code for reference: ```csharp using System; using Microsoft.Azure.WebJobs; using Microsoft.Extensions.Logging; public static class BlobCreatedHandler { [FunctionName("BlobCreatedHandler")] public static void Run([EventGridTrigger] EventGridEvent eventGridEvent, ILogger log) { log.LogInformation($"Event received: {eventGridEvent.EventType}"); // Further processing logic... } } ``` I've set up the Event Grid subscription through the Azure portal, linking it to my Azure Function. Here are a few details: - The storage account is located in the same region as the function. - The Event Grid subscription is set to deliver events of type `Microsoft.Storage.BlobCreated`. - I’ve verified that the storage account has a blob created event by manually uploading a blob and checking the Event Grid metrics, which show that the events are being generated. In the Azure portal, the function is not showing any invocations for these events. I tried enabling diagnostic logging for both the Event Grid and the Function App, but I still see no indication of what's going wrong. Also, I made sure that the function is set to use the correct connection string for the Event Grid. Can anyone provide guidance on what might be going wrong or what additional debugging steps I should take? I'm using .NET Core 3.1 for the function and the latest Azure Storage packages. Any help would be greatly appreciated! I'm coming from a different tech stack and learning C#. Could this be a known issue? Has anyone else encountered this? I'm working in a Linux environment. Could this be a known issue?