@Gerco Verweij Managed Identities are only supported for the listed build in triggers/action and managed connectors. As of now Micorosft teams and SharePoint are not supported.
Use managed identity for logic app (Teams, SharePoint)
Hello all,
I'm recently busy with logic apps to generate word documents, based on information which is available in a SharePoint list. That is working pretty well, however, my personal account is linked to all triggers and actions (like 'Send a message to a teams channel'). If I understand well, managed identities can be used for this (in most cases). I've searched the internet about managed identities, but I still can't use a managed identity for linking to my actions. I think I miss something.
What I've done so far:
- Create a user-managed identity within my resource group
- Give the identity 'Contributor' role within the resource group (don't know if this is necessary)
Should this be enough to use the identity for an API connection, like MS Forms? If I try to use the identity, I get the following error:
For now, the following API connections are used within my logic apps in this resource:
- Microsoft Forms -> To collect new responses and adding them to a SharePoint list
- SharePoint online -> For adding and updating SharePoint lists and create items (Word documents)
- Teams -> For sending messages and adaptive cards to a teams channel
- Word online business -> For populating a word template and fill variables from SharePoint list
- Office365 -> Outlook, for sending the word document in an e-mail
I read something about adding permissions to the identity with AzureAD Powershell commandlets. Is this necessary to use a managed identity in logic apps? Or do I need to give the identity another role? If yes, which one? Because there are a lot of roles!
I hope someone can put me in the right direction.
Thanks in advance.
Gerco