How do I trigger a blob in a separate storage account using Managed ID?

Hi @Niyam Bhat

Thank you for posting your query. I understand you would like to know how to trigger a blob in a separate storage account using Managed Identity, and you are also seeking to view logs for the Blob Trigger initiated on inventorxdata. Is that correct?

To better understand and diagnose the issue, could you please provide more details about your exact requirements or the specific problem you're encountering? Any screenshots or error messages you can share would be greatly appreciated.

Any additional information you can provide will be extremely helpful in troubleshooting and resolving the issue. Thank you!

Sure,
I am getting following error for now.
The 'DigestBlob' function is in error: Microsoft.Azure.WebJobs.Host: Error indexing method 'Functions.DigestBlob'. Microsoft.Extensions.Azure: Unable to find matching constructor while trying to create an instance of QueueServiceClient.

Expected one of the follow sets of configuration parameters:

1. connectionString
2. serviceUri
3. serviceUri, credential:accountName, credential:accountKey
4. serviceUri, credential:signature
5. serviceUri

Found the following configuration keys: credential, clientId, blobServiceUri.

The 'DigestBlob' function is in error: Microsoft.Azure.WebJobs.Host: Error indexing method 'Functions.DigestBlob'. Microsoft.Extensions.Azure: Unable to find matching constructor while trying to create an instance of QueueServiceClient.

Expected one of the follow sets of configuration parameters:

1. connectionString
2. serviceUri
3. serviceUri, credential:accountName, credential:accountKey
4. serviceUri, credential:signature
5. serviceUri

Found the following configuration keys: credential, clientId, blobServiceUri.

Hi @Niyam Bhat

Apologies for delay in response. Welcome to the Microsoft Q&A Forum and thanks for posting you query here!

In order to fix the issue, please follow the steps to trigger a blob in different storage account using Managed Identity, you need to make sure that Azure function is properly set up to access that storage account.

Make sure that the Managed Identity is enabled for Azure Function app. Login to Portal>>Function App>>Identity>>Enable Managed Identity.

Also, please assign the role Storage Blob Data Contributor at storage account level and assign access to the Managed Identity for the storage account you want.

When we are using Managed Identity, you don't need to provide a connection string. Instead, configure your function to authenticate against the storage account using the Managed Identity.

In your Azure Function code, make sure you're using the correct client configuration. You might need to utilize the BlobServiceClient with a DefaultAzureCredential to authenticate with Managed Identity. eg: var blobServiceClient = new BlobServiceClient(new Uri(blobServiceUri), new DefaultAzureCredential());

As said that if you are not seeing any logs, make sure logging is enabled for your Azure Function. You can view real-time logs by checking the Log Stream in the Azure portal.

As per the given error message given above, the error message might be because the function is trying to create a QueueServiceClient without the required parameters. Make sure you're not trying to create unnecessary services for your blob trigger.

Please follow the below link, if this might be helpful in resolving your issue.

Hope this helps in resolving your issue, if the still persists. Please feel free to contact, for any further assistance. We will be glad to assist you closely.

Please do consider clicking on "Accept Answer" and "Up-vote" on the post that helps you, as it can be beneficial to other community members.

Hi @Niyam Bhat

Just following up to see if the below answer helped. Please do consider clicking 'Up-Vote'/Accept Answer as accepted answers help community as well. Also, please click on Yes for the survey 'Was the answer helpful'. Thanks!