Worker Pipeline Decoupling

By design the worker pipelines called by the processing framework can be anywhere;

Any tenant (see cross tenant execution).
Any subscription.
Any resource group.
Any orchestrator.

Or, simply contained within the same orchestrator instance as the framework pipelines (parent/child/infant).

The Azure Functions used to interact with the worker pipelines assume nothing about the target location and require a complete set of environment metadata provided from the database at runtime. This includes:

Tenant Id
Subscription Id
Resource Group
Orchestrator Name
Orchestrator Type
Pipeline Name
SPN Id
SPN Secret

It is this level of pipeline decoupling that allows the processing framework to be used to bootstrap any existing solution.