Clarification Needed on Personal Access Token Expiration Notification

Nalini Bhavaraju 210 Reputation points
2026-06-15T15:12:02.53+00:00

Hi Team,

We received an email as below -

One or more of your personal access tokens are expiring

One or more of your personal access tokens in the Workspace xx-xx-azdatabricksws-resource, id: xx will expire in the next 7 days. Please renew your token(s) before expiration to avoid any disruption.

Token ID: xxxx

Comment:

Expiration: June 9, 2026

Last accessed: July 8, 2025

Owner name: xxxxx

Manage Your Tokens >

When we follow the link provided in the email and when we check manually from the Azure Databricks UI to review the PAT in the workspace mentioned, we do not see the Token ID given int he email.

There are only 2 Tokens and None are expiring in 2026. One of them is expiring in July 8, 2027.

Can you please clarify -

Whether the token still shows as expired?

Is this email generated for any other old Token ID that might be deleted sometime in the past ?

We just wanted to make sure None of the process using the PAT are effected.

Thanks,

Nalini.

Azure Databricks
Azure Databricks

An Apache Spark-based analytics platform optimized for Azure.

0 comments No comments

Answer accepted by question author
Vinodh247-1375 44,801 Reputation points Volunteer Moderator
2026-06-15T15:55:23.49+00:00

Hi ,

Thanks for reaching out to Microsoft Q&A.

This usually happens when the email is referring to a previous or already revoked PAT, not an active one visible in the UI. In Databricks, once a token is deleted or expired, it will no longer appear in the UI, but backend notification jobs can still trigger emails based on historical records. Given the “last accessed: July 2025” and no matching Token ID in your workspace, it is very likely this token is already expired or deleted, and the email is just a delayed or stale notif.

overall, if you do not see the TokenID in the workspace and your current tokens have valid future expirations, there is no impact to running processes. Only action needed is to doublecheck any legacy jobs or integrations, but in most cases, this can be safely ignored.

Please 'Upvote'(Thumbs-up) and 'Accept' as answer if the reply was helpful. This will be benefitting other community members who face the same issue.

Was this answer helpful?

1 person found this answer helpful.
0 comments No comments

0 additional answers

Sort by: Oldest

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.