Pipeline not running

Hi PNG_Power_Bi, 

It looks like an auth token expired. Can you double check all the connections used and re-authenciate them? I see this frequently when connections use the devleoper's microsoft account using oauth and that developer changes their password. 

Hi PNG_Power_Bi , Thank you for reaching out to the Microsoft Community Forum.

tayloramy  is correct, the failure is caused by an expired authentication token and that the connections used in the pipeline should be checked and re-authenticated. Errors with code AADSTS50173 commonly occur when a connection is using a user’s OAuth credentials and that user changes their password, is forced to sign out or their session is revoked by policy.

The token was explicitly revoked, as shown by the TokensValidFrom timestamp, so the pipeline will continue to fail until the exact Fabric connection or linked service using that user identity is edited and signed in again. For long-term stability, if the pipeline is operational, the better approach is to move the connection to a service principal or managed identity, so future password or security changes do not interrupt pipeline execution.