Eastern Analytics - Blog

Azure Data Factory (ADF) - Pipeline Parameters and Reuse

Written by Scott Pietroski | Jan 2, 2020 6:00:10 PM

ADF Pipeline Parameters and reusability:

Azure Data Factory (ADF) pipelines use parameters as a method of passing information from outside a pipeline into a pipeline.  Parameter values can be referenced within the pipeline’s activities as required. By using parameters a pipeline can take on the properties of a function – allowing the pipeline to serve a purpose such as starting or stopping an Azure service or sending out a communication.

 

ADF Pipeline Parameter Example: 

The pipeline in this example was created as a sort of ‘utility’ pipeline.   The pipeline’s name is “System – Send EMAIL”.  The pipeline was created for the purpose of sending emails via an Azure Power App.

 

The pipeline accepts the following parameters:

  • Subject
  • Recipients (can be comma separated list)
  • MessageBody  (message for email)
  • ErrorMessage  (error message from pipeline if error occurs)
  • Importance  (Low, Medium, High)

The pipeline accepts the above list of parameters then passes them thru to an Azure Power App service when making the call.  By using pipeline parameterization, the pipeline “System – Send EMAIL” can be included as an activity in any other pipeline – providing the ability to send emails as system notifications.

 

Image 1 – Email pipeline parameter definitions:

 

 

Image 2 –  Email pipeline’s use of parameters within an activity  The below screen shot highlights an activity referencing the parameters in a call an Azure Logic App.

 

 

Image 3 – Calling the email pipeline from another pipeline.  Now that we have created our “System – Send EMAIL” pipeline we can call it from other pipelines and just pass the parameter values.

 

 

 

 

Written by Scott Pietroski

Partner / Eastern Analytics, Inc. Solution Architect - Design thru delivery. 25+ Years of Data Warehousing, BI, Analytics, ML Specialties: MS Azure, HANA, Data Engineering, and Machine Learning experience. 
 
Scott can be reached at:  Scott.Pietroski@Eastern-Analytics.us