[VSTS] Using Process Parameters in Release Definitions

Building some release pipelines for my current project, I was faced with an inconvenience. When using a lot of Azure related tasks, in my case “Azure Resource Group Deployment” tasks, each of those tasks require a connection to your Azure subscription to function. Now you could just configure the connection for each task and be done with it. But I really HATE┬ádislike repetitive work and also didn’t fancy the maintenance effort when I would need to change anything in the future. So I went looking for a better way to do this.

What I wanted to achieve: define the Azure subscription connection once per environment so that I can still have difference subscriptions for Test, Acceptance and Production; but not having to specify it for each task individually.
Read More