User-assigned managed identity not working with the in-app Blob connector in Logic Apps

Mandal, Sukdev 0 Reputation points
2025-04-09T15:25:45.11+00:00

The in-app Azure Blob connector is throwing below authorization error when using a user-assigned managed identity for authentication. However, while trying with managed Blob connector its successfully creating connection with the same user-assigned managed identity without any issues. is this a limitation with in-app blob connector ?

User's image

Azure Logic Apps
Azure Logic Apps
An Azure service that automates the access and use of data across clouds without writing code.
3,470 questions
0 comments No comments
{count} vote

2 answers

Sort by: Most helpful
  1. Praveen Kumar Gudipudi 170 Reputation points Microsoft External Staff
    2025-04-09T22:18:05.9466667+00:00

    Hello Mandal, Sukdev,

    This is expected behavior from logic app blob built in connector. It has been mentioned in the built-in connector's documentation that some built-in connectors only support a single way of authentication. Please refer to the below statement from the document and quote it in your response

    Some built-in connectors support only a single way to authenticate a connection to the underlying service. Other built-in connectors can offer a choice, such as using a connection string, Microsoft Entra ID, or a managed identity. 

    There is no list of connectors provided in the documentation to provide more details on which connectors support single authentication. Based on the behavior we see I take Blob built-in connector does not support User assigned managed identity.

    If you found the response helpful, please click Accept Answer and Yes for the provided answer. This will help other community members with similar issues find the solution more easily.


  2. Rob Fox 0 Reputation points
    2025-05-04T07:55:18.16+00:00

    I also have a problem using the user assigned managed identity. Busy for over an hour, always throwing the error "Failed to get oauth token for managed identity". I ended up switching to the system-assigned managed identity that worked in a jiffy. Something's broken there for sure.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.