Introduction In previous post - Securing Function App with Azure Active Directory authentication we saw how function app can be secured with Azure active directory and how to make call to it. And it was done by creating an AD App which acted as Audience and and was responsible for validating the access token.  And as Azure Function App supports AD authentication, the Audience app can be assigned/linked to it. So the first thought would be that same can be done with Logic App, why this post? - Ideally it should be but it is not because not all Azure services support Azure AD authentication and Logic App is one of them. Microsoft has a plan for adding/integrating support for all All Azure services, but it will take some time.    So how do we use Azure Active Directory to secure Logic App? It can be done with the help of Azure APIM, where we ask it to do the task of validating the token and rest all remains same. i.e. whoever has to access the logic ap...

Introduction By default Function Apps are public in nature i.e. you can access it over internet without any restriction  (anonymous access) . However that is not the only thing, you can restrict the access by enabling access with function level authorization(Host keys). So the caller/client  has to have the key and sent it along with request, thus adding security to function App. Second option which is available is securing Function App using Azure Active Directory(Oauth standard). This is what we will explore with an example . I have tried to cover basic understanding around  AD authentication in following post-  Understanding Azure Active Directory Authentication and Authorization using Oauth There is one more way to add security to function app - by using Azure APIM Adding function App in ASE also makes it secure. Azure Active Directory Application When we say securing Function App with Azure AD it means whoever has to access the functi...