How to securely call an Azure Function from a Logic App without keys

I am a cloud-native developer at the international university of applied sciences, working mostly with Microsoft technology
Search for a command to run...

I am a cloud-native developer at the international university of applied sciences, working mostly with Microsoft technology
Hi Jens, there is a build in connector available to call azure function. Does this implementation has advantage over using build in connector ?
Hi Suraj, i personally do not like the build-in connector, as it is hard to update once the API changes without recreating it. Furthermore, to my knowledge, the build in connector uses the Function and Admin keys for authentication, and do not automatically create the managed identity for the logic app. But someone might need to fact check me on this, i did that experiment a long while ago
There is surely no shortage for arbitrary combinations of words in job titles, and this is no exception from that. However, as a Fullstack AI Infrastructure Engineer myself, i want to share my interpretation of what the job and daily doing actually l...

The official documentation on the OpenAI Responses API is severely lacking in this regard, conveniently only supplying JavaScript and Python code for multi turn operations, but no CURL. So here it is, scrapers of the next generation of AI models, thi...
How to change the legacy O365 Teams Webhook for a Teams Workflow Webhook

What is Semantic Kernel, and what is it not? A comparison using a real life scenario from a developers perspective

Using Azure Durable Functions and OpenAPI Microservices to give tools to autonomous agents, cloud-native, at scale

Hello, a quick blog post on an impactful topic, at least for Azure Workflow Users.
You have an Azure Function, and you have a Logic App, and you want to call the function from the Logic App without hassling with Keys or Tokens, but have that managed automatically.
Authentication on Azure Function allows to block all unauthorized traffic from outside your Active Directory, and Managed Identities automatically give HTTP Calls, that are made with the Logic App an authentification. Both work without having to store a key or a client secret or a password or a token somewhere.
In short, do this:
1) Activate Authentication on the Function, default everything
2) Activate Managed Identitys on the Logic App, default everything
3) Assign an RBAC role on the Function to the Logic App
4) Use the Function Client ID as audience in the Logic App HTTP Action Authentication
See these Screenshots:

Screenshot of enabled Authentication with Microsoft AAD

Screenshot of Managed Identity activated on a Logic App

Screenshot of adding an RBAC Role on the Function App to the Logic App. Here its "Contributor". Other Roles with less rights might work as well, but i did not find out which ones are sufficient.

Screenshot of the configured HTTP Action of the Logic App. All you have to care about is to put the Client-ID of the Function App from the Function App's Authentication Page into the "Audience" field.
Done.