Forum Discussion
Advocate ISudden pipeline authorization issues - using credentials we have no control over
Hi HoneHealthMB ,
As you can see from your reported error message, the problem you are experiencing is an expired authentication token.
The error message indicates that the token has been revoked, probably because of a password change or reset.
So I think you can take the following steps:
1. log in again to refresh the authentication token.
2. Make sure you have not changed or reset your password recently. If you have, log in with the new password.
3. if you are using an application or service, make sure it requests a new token after the old one expires.
Best Regards
Yilong Zhou
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
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?
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.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.
