Forum Discussion
Error causing pipeline failure
Hi
Would anyone recognise this error at all? I try to start a notebook spark, and it just immediately stops and says the following error: "Your compute session was disconnected, Run or reopen the notebook...."
When i look at my nightly run of the notebook, i get the following error:
Failed to get User Auth access token. The error message is: Failed to get User Auth access token. The error message is: _____________: 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 '2026-04-20T16:11:39.4655530Z' and the TokensValidFrom date (before which tokens are not valid) for this user is '2026-05-14T12:44:27.0000000Z'. Trace ID_________
I cant figure out how to refresh this auth token. It started on the 15th May, which is around the time i tried to change some tenant settings to allow external sharing. Im not really sure what to do, I have revoked access, resigned in etc, nothing seems to trigger the refresh token.
Thanks
Hello chriswyl91,
This is what you see when a refresh token gets revoked. The May 14th time frame suggests a tenant switch that probably broke existing sessions.
“The provided grant has expired due to it being revoked”
Try signing out of Fabric, signing back in, then reopening the notebook and running it again. That usually clears it.
If it still doesn’t work, check Workspace Settings → Connections and re-authenticate anything tied to your account. Old connections can keep reusing the revoked token even after a fresh login.
This often shows up after things like Conditional Access, MFA changes, or updates to external sharing settings.
For scheduled runs, user auth is where this tends to break.
Service principal or workspace identity is more stable.
Docs:
Refresh tokens in the Microsoft identity platformHi chriswyl91 ,
Thank you for reaching out to the Microsoft Community Forum. In addition to Olufemi7 response, i have added some points.
It is a token invalidation / credential revocation issue. Your auth token was issued on April 20, 2026 and your tenant/user forced token invalidation on May 14, 2026. So all tokens issued before May 14 are now invalid. This usually happens when password reset or security change, Admin revoked sessions, Tenant/security policy change and Conditional Access / external sharing updates.
Please try below workarounds.
1. Reauthenticate linked services, If your notebook uses Azure Data Lake, SQL DB, APIs and Fabric Lakehouses.
Go to Linked Services / Connections --> Click Edit --> Re-authenticate or Reconnect and Save again.
2. After Re-authenticate, Restart Spark pool / compute and Reopen notebook (don’t reuse the disconnected one).
3. Ask your admin to verify Conditional Access policies, external sharing policies, Token lifetime / session rules, “Sign-in frequency” policies and check whether “Revoke sessions” was triggered for users.
I hope this information helps. Please do let us know if you have any further queries.
Regards,
Dinesh
4 Replies
Hello chriswyl91,
This is what you see when a refresh token gets revoked. The May 14th time frame suggests a tenant switch that probably broke existing sessions.
“The provided grant has expired due to it being revoked”
Try signing out of Fabric, signing back in, then reopening the notebook and running it again. That usually clears it.
If it still doesn’t work, check Workspace Settings → Connections and re-authenticate anything tied to your account. Old connections can keep reusing the revoked token even after a fresh login.
This often shows up after things like Conditional Access, MFA changes, or updates to external sharing settings.
For scheduled runs, user auth is where this tends to break.
Service principal or workspace identity is more stable.
Docs:
Refresh tokens in the Microsoft identity platformHi chriswyl91 ,
Thank you for reaching out to the Microsoft Community Forum. In addition to Olufemi7 response, i have added some points.
It is a token invalidation / credential revocation issue. Your auth token was issued on April 20, 2026 and your tenant/user forced token invalidation on May 14, 2026. So all tokens issued before May 14 are now invalid. This usually happens when password reset or security change, Admin revoked sessions, Tenant/security policy change and Conditional Access / external sharing updates.
Please try below workarounds.
1. Reauthenticate linked services, If your notebook uses Azure Data Lake, SQL DB, APIs and Fabric Lakehouses.
Go to Linked Services / Connections --> Click Edit --> Re-authenticate or Reconnect and Save again.
2. After Re-authenticate, Restart Spark pool / compute and Reopen notebook (don’t reuse the disconnected one).
3. Ask your admin to verify Conditional Access policies, external sharing policies, Token lifetime / session rules, “Sign-in frequency” policies and check whether “Revoke sessions” was triggered for users.
I hope this information helps. Please do let us know if you have any further queries.
Regards,
Dinesh
Hi chriswyl91 ,
We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. And, if you have any further query do let us know.
Regards,
Dinesh
Hi @chriswyl91 ,
We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. And, if you have any further query do let us know.
Regards,
Dinesh