![\"ADF_REST_1](\"https:\/\/3cloudsolutions.com\/wp-content\/uploads\/2021\/09\/ADF_REST_1-002-1.jpg\")
<\/p>\nWe\u2019ve had conversations with customers about using either Data Factory or Logic Apps for pulling data from applications, maybe using REST API Calls. We\u2019ve discussed why you would use one over the other and we\u2019ve shared how we now favor patterns that use Data Factory and Azure Logic Apps, so it\u2019s not a choice of one or the other.<\/p>\n
But today I\u2019d like to show why I prefer to use Logic Apps in cases where we\u2019re accessing data from HTTP endpoints. The diagram below is from Azure Data Factory and shows building a connection to an HTTP service.<\/p>\n
<\/p>\n
What I want to focus on here is the authentication types. This is one of the key reasons why I gravitate to Logic Apps. In Data Factory, I have a limited list of choices as far as authentication methods including anonymous or no security \u2013 in most cases not a feasible option. In many cases we\u2019re pulling data from public facing websites, so things like Windows authentication is not a viable option.<\/p>\n
With Logic Apps I have many more options and much more flexibility as far as configuring how REST API calls are made. The diagram below is something we built for a call that we had been working with where the application was using OAuth and it required an access token string to be passed in.<\/p>\n
![\"ADF_REST_2](\"https:\/\/3cloudsolutions.com\/wp-content\/uploads\/2021\/09\/ADF_REST_2-002-1.jpg\")
<\/p>\n
With a Logic App this is relatively straightforward but is something we can\u2019t do in Azure Data Factory today. My illustration shows what that would look like. It\u2019s much simpler to parameterize your URL, so if there are query parameters that you pass into the URL, it\u2019s a bit easier to do in Logic Apps.<\/p>\n