Allow Data Pipeline runs to return structured logical results (not only Succeeded / Failed)

[murat-to]

Body

Microsoft Fabric Data Pipelines currently expose only a binary run result (Succeeded or Failed).

This works well for execution errors, but becomes limiting when pipelines are used for logical checks or validations, such as:

• data existence checks
• rule or condition evaluation
• control or decision pipelines

In many real scenarios:

• the pipeline completes without execution errors,
• however, the evaluated logical condition is false.

Today, pipeline authors must either:

• use Fail for expected logical outcomes (making them appear as system failures), or
• always return Succeeded, losing semantic meaning.

---

Proposal

Allow a pipeline run to expose an optional structured logical result
(for example, enum / string / JSON), independent of execution failure.

This would clearly separate:

• execution failure
• logical or validation outcome

and improve observability, orchestration design, and interface clarity.

---

Design intent

This proposal does not aim to weaken or redefine execution failure semantics.

Fail should remain a clear signal for true execution errors or unrecoverable exceptions.

The intention is to allow pipeline executions to expose logical evaluation results
without overloading failure states that are currently reserved for system-level errors,
thereby reducing false failure signals in monitoring views while preserving strict execution semantics.