This is best Fabric, Power BI, SQL and AI community event. How do we know? The last event sold out! Save €200 with code FABCMTY200.
Register nowA new Data Days event is coming soon! This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. Don't miss out.
I am getting this error when I am executing my pipeline in fabric. "Operation on target Audit_Table_Creation failed: Failed to get User Auth access token. The error message is: Failed to get User Auth access token. The error message is: AADSTS50173: The provided grant has expired due to it being revoked, a fresh auth token is needed. The user might have changed or reset their password. The grant was issued on '2025-07-13T23:40:27.4754901Z' and the TokensValidFrom date (before which tokens are not valid) for this user is '2026-01-09T06:22:31.0000000Z'. Trace ID: d6627e27-84af-43c7-8e6d-e609e1d63100 Correlation ID: a83a8dff-f6ac-4f4e-9a60-2f445afb8040 Timestamp: 2026-02-14 23:28:06Z.."
Need clarification and assistance please.
thank you.
Solved! Go to Solution.
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.
Proud to be a Super User! | |
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.
Hi @PNG_Power_Bi , Hope you're doing okay! May we know if it worked for you, or are you still experiencing difficulties? Let us know — your feedback can really help others in the same situation.
Hi @PNG_Power_Bi , hope you are doing great. May we know if your issue is solved or if you are still experiencing difficulties. Please share the details as it will help the community, especially others with similar issues.
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.
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.
Proud to be a Super User! | |
Check out the June 2026 Fabric update to learn about new features.
Sign up to receive a private message when registration opens and key events begin.