Forum Discussion
Sudden pipeline authorization issues - using credentials we have no control over
That reply makes no sense.
Let's start with a simple question.
For a given pipeline, what "token" is it referring to? I have connections to 3 different warehouses/databases in that pipeline. None of them use anything about a token. They all use service principals.
I am saying that it is absurd that a pipeline has to run as its "owner", and there is no ability to change the owner. What are you supposed to do when an employee leaves?
To add our woes to your woes... we recently had a load of pipelines fail on April 1st. Sadly not an April Fools either! Errors relating to Conditional Access failures, no clues in the logs, no useful articles to help us. Checked all authentication for connectors related to pipelines, all checked-out fine. In the end, we went into each pipeline, made an inoccuous change (like renaming an action), and re-saved. After the save, everything was fine. Had to do this 10s of times. Utter nonsense.
The more I use Fabric, the more I feel that it is not fit for Enterprise.