Forum Discussion
Advocate ISudden pipeline authorization issues - using credentials we have no control over
Advocate IThat 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?
If you are wondering - we've just had an employee leaving and all his work stopped working.
Apparently you what you need to do - give access to connections you are using, that is expected. Then you have to give data pipeline, dataflows, etc. authority for some reason, because it will not work and also if it had schedule - you need to take ownership of the schedule also. Our best solution, since our number of items is around 10, is to change something in the pipeline - save it, then change the schedule and save it also. Then it is likely that it won't fail, but you never know.