@Dixan Thomas Welcome to Microsoft Q&A Forum, Thank you for posting your query here!
I understand that you want to use Managed Identity to interact with queue storage from FuntionApp instead of using Connection String.
You need to first leverage v5.0 version of Microsoft.Azure.WebJobs.Extensions.Storage.Queues
. This version introduces the ability to connect using an identity instead of a secret. For a tutorial on configuring your function apps with managed identities, see the creating a function app with identity-based connections tutorial.
dotnet add package Microsoft.Azure.WebJobs.Extensions.Storage.Queues --version 5.0.0
Once the above steps are followed, Your application may require additional permissions based on the code you write. You need to have the below RBAC permissions on Azure Storage for your Function APP.
Trigger | Storage Queue Data Reader, Storage Queue Data Message Processor |
Output binding | Storage Queue Data Contributor, Storage Queue Data Message Sender |
Below settings are also needed in your json:
"AzureWebJobsStorage__queueServiceUri": "https://mystorage.queue.core.windows.net/",
"AzureWebJobsStorage__credential": "managedidentity"
More Info about the above settings are below:
AzureWebJobsStorage__credential | Defines how a token should be obtained for the connection. This setting should be set to "managedidentity" if your deployed Azure Function intends to use managed identity authentication. This value is only valid when a managed identity is available in the hosting environment. |
---|
AzureWebJobsStorage__queueServiceUri | The data plane URI of the queue service of the storage account, using the HTTPS scheme. | https://<storage_account_name>.queue.core.windows.net |
---|
Also refer : Azure Functions - use queue trigger with managed identity
** Please do not forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.